Re: <timesheets>separating svg data from presentation

Robert,

SMIL/SVG Cascading Animation Sheets could look like this:

In one SVG file containing all sitewide animations
"sitewide_animations.svg" :
(and maybe all other sitewide data: SVG fonts, symbols, headers,
footers, metadata, filters, etc; everything that gets used more than
once, or/and is handy to have in one central place)
...
  <animate xlink:href="svg[@id = 'mainLogo']/ellipse)" ... />
...

(note the use of XPath to address multiple targets)

in the SVG files:
...
  <?xml-animationsheet href="sitewide_animations.svg"
type="image/svg+xml"?>
...

= flexible, no redundancy, easy to maintain, remote control.

The actual syntax for all this has not been developed.
The concept is one of my wishes for SVG2.

Tobi


> 
> I think that Tobi's trem maybe be better......animationsheet.....I like it ....I can even dance to it.
> 
> but...what is the idea......someone...give a definition....
> 
> ####################################################
> I guess there are different concepts being developed and discussed.
> 
> What I would like to use are animationsheets:
> place all animations (or all animations that apply to more than one SVG)
> in one file (just like CSS), and have centralized remote control over
> the animations on a collection of SVGs, for example a whole site.
> In combination with XPath and XPointer for addressing multiple targets,
> a lot of otherwise redundant code could be saved, and global changes
> could be realized more effectively.
> 
> http://www.pinkjuice.com/SVG/spec-prop.xhtml#animation
> 
> tobi
> #####################################################

-- 
Tobias Reif
http://www.pinkjuice.com/myDigitalProfile.htm

Received on Friday, 11 May 2001 18:03:47 UTC