Quoting "Jon A. Cruz" <jon@...18...>:
Except that it's not a live view of the same tree. Not exactly anyway.
Instead it's an alternate rendering that comes through an entirely different code path.
Right, we need to unify the codepaths.
When Inkscape loads it's SVG icons, it goes through a strange separate codepath that renders things differently. The icon view is not really a view on the same document, but a different rendering of it. Of course, at one level that could be considered the same thing, but on another it's different.
We have too many sections of the code that are "the same, only different" already. :P
Factor out and unify the "same" parts.
Same goes for animation. It's not going to be a separate View on the same live tree Model, but a View based on a slave Model that is sporadically updated.
Shouldn't the master and slave models still present the same interface, though?
You can't get a useful animation preview without cloning the entire document down to the XML::Node level anyway, at least if we're talking about DOM-based animation.
Declarative animation, yes, we should be able to manage that from the SPObject level.
-mental