- From: Dr. Olaf Hoffmann <Dr.O.Hoffmann@gmx.de>
- Date: Thu, 25 Jan 2007 14:17:49 +0100
- To: www-svg@w3.org
- Cc: Simon.Flannery@wrsa.com.au
Hello, some ideas about this (maybe there are much more possibilities): 1. The program calculates the position of the offset in the same coordinate system as the polyline or path and the offset is realised with a transform attribute. Of course, the information about the fraction of 50/234 of the pathLength is lost. The transform attribute can be used in general to get some relative offset, often it will be useful to group elements with the g element to translate them together. 2. A path itself can be structured with stroke-dasharray in arbitrary fractions. Of course this is limited to the possibilities of stroke-dasharray, but is enough to mark a fraction or 50/234 of the pathLength. 3. With animateMotion, maybe using pathLength, keyPoints, keyTimes, keySplines and so on it is possible to position any object at any fraction of an arbitrary path time dependent or constant in time. Calculating correct timing will be necessary to avoid any visible motion in the last case. This method is limited to paths expressed in a path element (no polyline or polygon element) or alternatively a list of values (like a polyline or polygon). Here only some information about the meaning of the path is lost and the viewer needs to support animation, even if the timing is chosen in such a way, that nothing really moves within the display time. An information about the meaning of the path can be added again using elements like title and desc or the class attribute. This seems to me the most comfortable solution of the problem with a minimum of information loss, but requires simple calculation and the understanding of the animateMotion element of course.
Received on Thursday, 25 January 2007 13:23:21 UTC