I've seen several people mention Shockwave-style animation, with something like the Score. I wonder if people know about this spec yet, which layers such a model atop SMIL: http://www.w3.org/TR/timesheets/
This would be a way to go, if such a thing is desired. It's always best to avoid adding new and incompatible namespaces.
By the way, while trying to implement SVG-DOM in /src/dom and binding/scripting int /src/bind, I am finding a lot of questions that are not, as far as I can find, in the specs.
For example, the interfaces here, except for SVGElement, do not inherit from Element, thus do not have attributes: http://www.w3.org/TR/SVG/types.html#BasicDOMInterfaces ...yet they all must map their semantic values onto attributes when getting/setting. Is there a reason for that? It would seem to be more efficient to inherit this, along with their semantics.
Would anyone know why? Just curious. This seems to demand an interface/implementation split, rather than merely suggest it.
bob
Chris Lilley wrote:
On Wednesday, May 7, 2008, 6:48:59 AM, Jonathan-David wrote:
JDS> I don't know svg much, but one way further to animate object JDS> properties, instead of using the builtin tweening svg JDS> capabilities, is to have script drivers (like python drivers for JDS> Blender IPOS (keyframes)) : expressions that are shorter than a JDS> piece of code, and return some value to use. For example, assign JDS> to the alpha of some object the java script expression : JDS> sin(2*3.14*10*_current_frame_number) where _current_frame_number JDS> is the official frame number is a variable representing the JDS> actual frame being played in the running svg animation/application.
SVG isn't frame based (perhaps you are more familiar with SWF?) but a relative time-based expression would be one way to do this.