Inkscape Wiki - User contributions [en]

SVG Test Suite Compliance

2006-01-23T14:57:49Z

Jacktanner: Spam.

This table summarises the results of testing Inkscape against the [http://www.w3.org/Graphics/SVG/Test/ [[W3C]] SVG Test Suite].

Last complete test was performed on Windows with release version Inkscape-0.42-1.win32.exe. See also
* [[SVG Test Suite Compliance V0.41]]
* [[SVG Test Suite Compliance-0.42-1]]

== Key ==
; '''pass''' : the test passed fully (69 occurences)
; '''partial''' : the test partially failed but it may be easy to make it pass (24 occurences)
; '''fail''' : the test failed (88 occurences)
; '''crash''' : the test failed and Inkscape crashed (0 occurences)

----
== Results ==
=== Animation (not yet supported) ===
; animate-elem-02-t.svg : '''fail'''
; animate-elem-03-t.svg : '''fail'''
; animate-elem-04-t.svg : '''fail'''
; animate-elem-05-t.svg : '''fail'''
; animate-elem-06-t.svg : '''fail'''
; animate-elem-07-t.svg : '''fail'''
; animate-elem-08-t.svg : '''fail'''
; animate-elem-09-t.svg : '''fail'''
; animate-elem-10-t.svg : '''fail'''
; animate-elem-11-t.svg : '''fail'''
; animate-elem-12-t.svg : '''fail'''
; animate-elem-13-t.svg : '''fail'''
; animate-elem-14-t.svg : '''fail'''
; animate-elem-15-t.svg : '''fail'''
; animate-elem-16-t.svg : '''fail'''
; animate-elem-17-t.svg : '''fail'''
; animate-elem-18-t.svg : '''fail'''
; animate-elem-19-t.svg : '''fail'''
; animate-elem-20-t.svg : '''fail'''
; animate-elem-21-t.svg : '''fail'''
; animate-elem-22-b.svg : '''fail'''
; animate-elem-23-t.svg : '''fail'''
; animate-elem-24-t.svg : '''fail'''
; animate-elem-25-t.svg : '''fail'''
; animate-elem-26-t.svg : '''fail'''
; animate-elem-27-t.svg : '''fail'''
; animate-elem-28-t.svg : '''fail'''
; animate-elem-29-b.svg : '''fail'''

=== Colors ===
; color-prof-01-f.svg : '''fail'''
: <i>Tests color profile support. Hopefully the Little CMS work should address this: see [[InkscapeColor]].</i>
; color-prop-01-b.svg : '''fail'''
: <i>there are bugs for variations of this test: see comment in sp_object_get_style_property.</i>
; color-prop-02-f.svg : '''pass'''
; color-prop-03-t.svg : '''pass'''

=== Coordinates ===
; coords-trans-01-b.svg : '''pass'''
; coords-trans-02-t.svg : '''pass'''
; coords-trans-03-t.svg : '''pass'''
; coords-trans-04-t.svg : '''pass'''
; coords-trans-05-t.svg : '''pass'''
; coords-trans-06-t.svg : '''pass'''
; coords-units-01-b.svg : '''partial''' - incorrect clipping
; coords-units-02-b.svg : '''partial'''
; coords-units-03-b.svg : '''partial''' - the red background is not clipped correctly
; coords-viewattr-01-b.svg : '''fail'''
; coords-viewattr-02-b.svg : '''partial''' - viewport boxes not styled correctly
; extend-namespace-01-f.svg : '''fail'''

=== Filters (not yet supported) ===
; filters-blend-01-b.svg : '''fail'''
; filters-color-01-b.svg : '''fail'''
; filters-composite-02-b.svg : '''fail'''
; filters-comptran-01-b.svg : '''fail'''
; filters-conv-01-f.svg : '''fail'''
; filters-diffuse-01-f.svg : '''fail'''
; filters-displace-01-f.svg : '''fail'''
; filters-example-01-b.svg : '''fail'''
; filters-gauss-01-b.svg : '''fail'''
; filters-image-01-b.svg : '''fail'''
; filters-light-01-f.svg : '''fail'''
; filters-morph-01-f.svg : '''fail'''
; filters-offset-01-b.svg : '''fail'''
; filters-specular-01-f.svg : '''fail'''
; filters-tile-01-b.svg : '''fail'''
; filters-turb-01-f.svg : '''fail'''

=== Fonts ===
; fonts-elem-01-t.svg : '''fail'''
; fonts-elem-02-t.svg : '''fail'''
; fonts-elem-03-b.svg : '''fail'''
; fonts-elem-04-b.svg : '''fail'''

=== Interaction (not supported) ===
These tests are only relevant to Inkview; Inkscape interaction is inevitably oriented to support editing. These tests are done against Inkscape however, hence the failures.
; interact-cursor-01-f.svg : '''fail'''
; interact-dom-01-b.svg : '''fail'''
; interact-events-01-b.svg : '''fail'''
; interact-order-01-b.svg : '''fail'''
; interact-order-02-b.svg : '''fail'''
; interact-order-03-b.svg : '''fail'''
; interact-zoom-01-t.svg : '''fail'''

=== Linking ===
These tests are only relevant to Inkview; Inkscape linking is inevitably oriented to support editing. These tests are done against Inkscape however, hence the failures.
; linking-a-01-b.svg : '''fail'''
; linking-a-02-b.svg : '''fail'''
; linking-a-03-b.svg : '''fail'''
; linking-a-04-t.svg : '''fail'''
; linking-uri-01-b.svg : '''fail'''
; linking-uri-02-b.svg : '''fail'''
; linking-uri-03-t.svg : '''fail'''

=== Masking ===
; masking-mask-01-b.svg : '''partial''' - the string is incorrectly rendered (see Fonts above)
; masking-opacity-01-b.svg : '''pass'''
; masking-path-01-b.svg : '''pass'''
; masking-path-02-b.svg : '''partial''' - clip[[PathUnits]]=object[[BoundingBox]] fails
; masking-path-03-b.svg : '''fail'''
; masking-path-04-b.svg : '''pass'''
; masking-path-05-f.svg : '''partial''' - clip-rule=evenodd not functioning

=== Metadata ===
; metadata-example-01-b.svg : '''pass'''

=== Painting ===
; painting-fill-01-t.svg : '''pass'''
; painting-fill-02-t.svg : '''pass'''
; painting-fill-03-t.svg : '''pass'''
; painting-fill-04-t.svg : '''pass'''
; painting-marker-01-f.svg : '''pass'''
; painting-marker-02-f.svg : '''partial''' - mishandling of marker strokes
; painting-render-01-b.svg : '''pass'''
; painting-stroke-01-t.svg : '''pass'''
; painting-stroke-02-t.svg : '''pass'''
; painting-stroke-03-t.svg : '''pass'''
; painting-stroke-04-t.svg : '''pass'''

=== Paths ===
; paths-data-01-t.svg : '''pass'''
; paths-data-02-t.svg : '''pass'''
; paths-data-03-f.svg : '''pass'''
; paths-data-04-t.svg : '''pass'''
; paths-data-05-t.svg : '''pass'''
; paths-data-06-t.svg : '''pass'''
; paths-data-07-t.svg : '''pass'''

=== Color Gradients ===
; pservers-grad-01-b.svg : '''pass'''
; pservers-grad-02-b.svg : '''pass'''
; pservers-grad-03-b.svg : '''pass'''
; pservers-grad-04-b.svg : '''pass'''
; pservers-grad-05-b.svg : '''pass'''
; pservers-grad-06-b.svg : '''pass'''
; pservers-grad-07-b.svg : '''pass'''
; pservers-grad-08-b.svg : '''partial''' - gradient is ok; font is incorrect (see Fonts above)
; pservers-grad-09-b.svg : '''pass'''
; pservers-grad-10-b.svg : '''pass'''
; pservers-grad-11-b.svg : '''pass'''
; pservers-grad-12-b.svg : '''pass'''
; pservers-pattern-01-b.svg : '''pass'''

=== Rendering ===
; render-elems-01-t.svg : '''pass'''
; render-elems-02-t.svg : '''pass'''
; render-elems-03-t.svg : '''fail''' - not rendered
; render-elems-06-t.svg : '''partial''' - rendering is ok; font is incorrect (see Fonts above)
; render-elems-07-t.svg : '''partial''' - rendering is ok; font is incorrect
; render-elems-08-t.svg : '''partial''' - rendering is ok; font is incorrect
; render-groups-01-b.svg : '''partial''' - rendering is ok; font is incorrect
; render-groups-03-t.svg : '''partial''' - rendering is ok; font is incorrect

=== Scripting (not supported) ===
; script-handle-01-b.svg : '''fail'''
; script-handle-02-b.svg : '''fail'''
; script-handle-03-b.svg : '''fail'''
; script-handle-04-b.svg : '''fail'''

=== Shapes ===
; shapes-circle-01-t.svg : '''pass'''
; shapes-ellipse-01-t.svg : '''pass'''
; shapes-line-01-t.svg : '''pass'''
; shapes-polygon-01-t.svg : '''pass'''
; shapes-polyline-01-t.svg : '''partial''' - the pentagon ends are incorrect
; shapes-rect-01-t.svg : '''pass'''

=== Structure ===
; struct-cond-01-t.svg : '''fail'''
; struct-cond-02-t.svg : '''fail'''
; struct-defs-01-t.svg : '''pass'''
; struct-dom-01-b.svg : '''fail'''
; struct-dom-02-b.svg : '''fail'''
; struct-dom-03-b.svg : '''fail'''
; struct-dom-04-b.svg : '''fail'''
; struct-dom-05-b.svg : '''fail'''
; struct-dom-06-b.svg : '''fail'''
; struct-frag-01-t.svg : '''pass'''
; struct-group-01-t.svg : '''pass'''
; struct-group-02-b.svg : '''pass'''
; struct-image-01-t.svg : '''pass'''
; struct-image-02-b.svg : '''partial''' - problem with use element
; struct-image-03-t.svg : '''fail''' - Gamma correction
; struct-image-04-t.svg : '''pass'''
; struct-image-05-b.svg : '''fail''' - Prints the message: error loading pixbuf at close
; struct-symbol-01-b.svg : '''partial''' - the topleft image is not resized correctly

=== CSS ===
; styling-css-01-b.svg : '''pass'''
; styling-css-02-b.svg : '''pass'''
; styling-css-03-b.svg : '''pass'''
; styling-inherit-01-b.svg : '''pass'''
; styling-pres-01-t.svg : '''pass'''

=== Text ===
; text-align-01-b.svg : '''pass'''
; text-align-02-b.svg : '''fail''' - baseline-shift not functioning
; text-align-03-b.svg : '''fail'''
; text-align-04-b.svg : '''partial''' - tref not supported
; text-align-05-b.svg : '''pass'''
; text-align-06-b.svg : '''fail'''
; text-altglyph-01-b.svg : '''fail'''
; text-deco-01-b.svg : '''partial''' - underline and strikethrough not functioning; whitespace problem
; text-fonts-01-t.svg : '''partial''' - monospaced font is incorrect
; text-fonts-02-t.svg : '''partial''' - font-weight="lighter" not functioning
; text-intro-01-t.svg : '''pass'''
; text-intro-02-b.svg : '''partial''' - right-to-left text now functioning but mis-aligned
; text-intro-03-b.svg : '''partial''' - text is vertical but oriented incorrectly
; text-intro-04-t.svg : '''pass'''
; text-path-01-b.svg : '''pass'''
; text-spacing-01-b.svg : '''pass'''
; text-text-01-b.svg : '''fail''' - 'textLength' and 'lengthAdjust' not functioning
; text-text-03-b.svg : '''partial''' - underline and strikethrough not functioning
; text-tref-01-b.svg : '''fail''' - tref not functioning
; text-tselect-01-b.svg : '''pass'''
; text-tspan-01-b.svg : '''pass'''
; text-ws-01-t.svg : '''pass'''
; text-ws-02-t.svg : '''pass'''
----

Animation-(Timeline)

2006-01-23T14:55:39Z

Jacktanner: Spam.

[[Animation|Back to main page for animation]]

=== User interface for timeline-based animation ===

==== Existing animation programs (Free & non-Free) ====

* [[MacromediaFlash]] is a good non-Free example.
* Macromedia Director prior to version MX had a different interface (http://www.rice.edu/fondren/erc/howto/director.html) which I prefer(ed) over Flash
* QFlash is a FUNCTIONAL free-software mock-up of the Flash 4 interface, which can import SVG files but not edit them. (http://qflash.sourceforge.net)
* F4l is a non-functional free-software mock-up of the Flash 4 interface.(http://f4l.sf.net/)
* [[Moho]] as a gratis-but-non-free example. (Written in Java.)
* [[LimSee2]] (http://wam.inrialpes.fr/software/limsee2/) is an excellent almost-free basis. (The web site incorrectly claims open source, but it means only that the source code is visible: the actual license says in capital letters no commercial use or distribution.)
* Spalah Flash (http://spalah.sourceforge.net/?p=10) (not to be confused with Spalah CMS) "is a GTK2[[/GNOME2]] based application for generating Macromedia SWF and [[W3C]] SVG animations." The GUI is today minimalist but the author is trying to integrate it with inkscape. See http://spalah.sourceforge.net/?p=19
* SMIL 2.1 player (GPL): http://www.cwi.nl/projects/Ambulant/distPlayer.html
* Bob Sabiston's proprietary animation software http://www.flatblackfilms.com
* Synfig (http://www.synfig.com/) is a free-software film-quolity 2D vectore animation software.

==== Fantavision example ====
Back in the '80's there was a program on Apple IIE (Amiga and MS-DOS too) called "Fantavision". It allowed one to create vector artwork (although I didn't understand at the time that that was what it was called) and animations. It allowed one to create frames of animation where you manually repositioned, recolored, scaled, rotated etc. the objects from one frame to the next. However, it then automatically interpolated frames between the 2 frames (the number of interpolated frames was configurable) such that it create a smooth transition of the object moving from one frame to the other. The effect was very similiar to the "Morphing" effect for raster graphics (popularized in a Michael Jackson video, I believe). That is, the system calculated the trajectory of "Key Points" of the objects from one frame to the next. This process is often called "Tweening" (a term used by Macromedia Flash). [[Sketch|Skencil]] (formerly known as [[Sketch]]) supports this functionality and describes it as "Blending".

I guess what I'm saying is that I think a nice interface to create animations would be similiar. So to animate you would do the following:

* Draw the initial SVG Image

* Increment Frame (from say 1 to 20)

* Reposition the elements in frame 20 (including scaling, color changes, adding removing objects, etc, etc, etc)

* System would then calculate a trajectory for each key point from frame 1 to frame 20. Trajectories would be calculated for things like:
** Each "node" of an object
** Color
** Transformation Matrix
** etc

* You could display/manipulate the trajectories (using the trajectory editor shown above by the original creator of this topic)

* The system would then store the animations using SVG trajectories and the "Key Points" would be the frames you manually created

:So, to create say a 100 frame animation, one might only need to manually create/modify 10 frames and the system would interpolate the additional frames as necessary.

* Also, once the system interpolated frames it would allow you to manually modify the interpolated frames creating further "Key Points" and allow further refinement and interpolation.

NOTE: 3D apps such as blender also use a technique like this, which I think is most widely known as "keyframe animation" or simply "keyframing". However, many such systems tie the keys too closely to actual animation frames, and this creates problems when the frames-per-second rate changes. Particularly in the case of vector apps which are not so low-level as bitmaps and animation frames, I would suggest that frames should be as abstract as possible.

Having key positions in simple percentages of the total animation time might be a better solution. This would also need to be a global/local system, of course: animated objects would have their own animation time specified when inserted into a larger document. A character's walkcycle would end at 100%, but in the larger animation, it would perhaps only be 5% of the total time, yet repeating as the object moves across the screen.

One issue with this abstraction of frames might be that important animation effects do not occur exactly within frames: small things could be mistimed, or simply missed altogether. If you set the frame rate too low, this would be an obvious side effect, so it's not necessarily a problem
that Inkscape should try to fix. On the other hand, a few things could be done to ease this. For instance, "snapping" animation events to frames when exporting (thereby slightly altering the timing), or perhaps just warning that certain animation events are not visible at such a low frame rate.

Of course, on the web, with SVG and DHTML, where most Inkscape animations will hopefully be used one day, frames are not an issue at all, and we just worry about keys in time :)

==== Bob Sabiston Example ====
Bob Sabiston's animation software is an amazing vector-based package that stores line width within the points that make up a line -- derived from a tablet pen. usually in a simple stroke there could be a hundred data points storing width information. Then in the next keyframe, a line from a previous key is selected and re-drawn restricted to the same number of points. The software allow sthe points to be "repositioned" as you watch their previous locations be re-positioned. When you run out, the line ends automatically. This information is interpolated in tweening frames to change shape, width, position, but retains the same number of data-points. See the film "Waking Life" for the making-of video for a demonstration. Also visit his website for examples of it's capabilities converted to flash. http://www.flatblackfilms.com

==== Other thoughts ====

Suggestion from someone else: working like [[CinePaint]] (compared with Gimp), with each frame independently from each svg document (working like this or providing this feature) - providing vectorial edition quality we can't get on apps like Macromedia Flash or any other (maybe [[ToonBoom]] or Moho) - allowing us to make our work fast publish without further lack of quality.
(One more suggestion about it: being able to convert .swf to .svg sequence (or animated .sgv) and vice versa.)

It is suggested that there be basically two modes: Local (Object) mode and Global mode. Below is a picture showing a very rough design of the local mode:

http://www.inkscape.org/wiki_uploads/anim_gui1.png

In local modes, all properties of the object editing will be shown on a timeline, and one can create and edit frame within the timeline. Then one may assign different value of that properties on different timeline, or make it change linearly, or nonlinearly :)

==== Onion Skinning ====
As an animator, one of the features I find most useful is the ability to view a series of frames layered on top of each other (called "onion skinning"). They don't need to be key frames, or even tied to a particular frame rate, just be representative of the state at regular time intervals. It's much more intuitive than looking at a graph of position vs. time or whatever you are animating. After all this is a tool to be creative with, and graphs are more suited to thinking like an engineer.