W3C home > Mailing lists > Public > public-fx@w3.org > October to December 2010

Re: CSS SVG Discussion on Thursday

From: Dr. Olaf Hoffmann <Dr.O.Hoffmann@gmx.de>
Date: Wed, 3 Nov 2010 10:36:00 +0100
To: public-fx@w3.org
Message-Id: <201011031036.00977.Dr.O.Hoffmann@gmx.de>
Dean Jackson:
...
>Some of the complaints against SMIL/SVG animation is that it mixes the 
>animation with the content, but that doesn't need to be so. It would be 
>fairly simply to define behaviour of an "animation sheet", referenced by a 
><link> element, that is an external file containing the animations. I'd 
>suggest adding a selector attribute to the animation elements to replace 
>xlink:href.

Basically this happened already with the timesheet draft of the SYMM WG:
http://www.w3.org/TR/timesheets/
Taking into account this and some more elegant notation to reference the
timesheet, there would be in general no need anymore for CSS-animations
(something like the CSS-transitions however can be a nice improvement for
declarative animation with SMIL as well as to apply animations to classes, not
only to single elements).
This basically has the advantage, that authors can concentrate on one 
simple method of notation (XML/SMIL) and no new CSS notation variant.

Even in SVG it is no problem to get a relative good separation putting
all animation stuff into the top defs element...
And because in most cases the animation in SVG is not only decorative 
as those intended for CSS-animations, within the same document is 
typically the right place for it - and a notation within the animated element
can have advantages, if one wants to provide alternative text content
for the animation itself, not only the whole document. I think, CSS-animations
have no own accessibility feature at all (?)


Olaf
Received on Wednesday, 3 November 2010 09:36:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 3 November 2010 09:36:37 GMT