Note that the Timeline is used for editing all animations in the SVG. It may be possible with this design to allow separate times for each row, letting the animator compare the states of different layers/objects at separate times.The Layers/Timeline dialogue would have to be able to dock to the bottom of the window, as the width (even when at its smallest size, not shown here) would be prohibitive to have on the right.
rotation) would be un-applied in isolation mode. For animations nested in other animations, the animated effects applied by the one higher up (e.g. Selecting any keytime block would put it in 'isolation mode,' similar to what's available in Flash™ and Illustrator™.There is a drop-down menu used for selecting the viewable frames per second, used as a grid.An interpolation curve editor is also readily available, similar to the note editor in GarageBand™.However, the two are similar enough to allow an easy move from Flash™ to Inkscape. This is necessary as SVG animations are based on keytimes instead of frames and keyframes. Instead of being based on the Flash™ timeline, which is frame-based, this one is based more on GarageBand™, which as a music editor is time-based.Each layer and group can 'open' to display the individual objects contained in it. In this concept, the Timeline is an extension of the Layers dialogue.This will make it a lot easier for current Flash artists to move to SVG.Īn example of the third interface would be: Finally, the most professional interface would abstract away as much of the SVG specific parts of the problem as possible and provide an interface that conforms to the more popular Flash animation packages.
At the same time, someone needs to develop some visual cues that will appear in the editor window that will indicate that animations are present. This will take some time, but it isn't a particularly difficult task, since much of the code can be modeled on existing interface panels.
Summary Rationale Design Document Handling User Interface
0 kommentar(er)
