Hi, Alexander- Thanks for your comment. It's always interesting to hear from viewer implementors.
You comment about native time functions made me think that a viewer having its own timer functionality will help with consistent timeline control, as described in: 13.5 Time Manipulation http://www.w3.org/TR/SVG12/animation.html#timemanipulation The new 'speed' attribute can be used "to speed up or slow down the effective rate of play relative to the parent time container" or to "cause the element to play backwards." Do you think that this is true, or am I misinterpreting what you're saying? Regards- -Doug Alexander Adam wrote: | | Ronan, | | > Good point about performance. | > | > But dont you think that asking each browser implementer to do this | is a bit of | > overkill? Granted, it takes the technical requirements out of the | developers | > and puts them in the hands of the infrastructure (viewer) people. | But man, at | > what cost?? This seems to me to only be adding | YetAnotherHurdleToSVG1.2. | | Well I can just talk about what we're experiencing due the svg | viewer development process. Timers and other - more or less - "low" | level routines / classes are easy to be implemented by the viewer | vendor. A time is a sample of that. It takes the vendor a few lines | to provide a new object to the engine accessing the underlying | system api's. It'd be another case of SVG would require to implement | any high-complex thing (like UI Controls etc.) because they would be | much harder to implement and less "low"-level. Also note that SVG is | an animating, time based format and by that, it really makes a lot | of sense to add a SVG-Only API for a Timer implementation. | | > About performance, i have been hearing that scripting performance | is mostly | > affected by the rendering side on asv, and not by the script | complexity. | | Well, what we're experiencing (We're the first _not_ using the Mozzi | Scripting Engine) is that scripting perfomance really slows down | when you have routines that are needed to do time-critical stuff as | the scripting engine can not and does not have to guarantee to | execute something at a specific time, it executes it when there's | power left for it, know what I mean? Whereas this may not be that | important for 'standard' web apps, its a big issue when trying to | develop time critical applications. A timer API implemented by the | viewer itself could be Thread based and by that, allow a | real 'multitasking' SVG Application. | | Alexander Adam | EvolGrafiX - http://www.evolgrafix.com ------------------------ Yahoo! Groups Sponsor --------------------~--> $9.95 domain names from Yahoo!. Register anything. http://us.click.yahoo.com/J8kdrA/y20IAA/yQLSAA/1U_rlB/TM --------------------------------------------------------------------~-> ----- To unsubscribe send a message to: [EMAIL PROTECTED] -or- visit http://groups.yahoo.com/group/svg-developers and click "edit my membership" ---- Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/svg-developers/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
