On Sat, 2004-11-06 at 13:21, bulia byak wrote:
On the other hand, it occurred to me that we may want to use arbitrary objects as guides (as some other vector editors do). Such objects would have to be SVG objects but, as guides, only visible in Inkscape. How to handle them?
One idea is this: store such objects in <defs> with an inkscape: attribute telling Inkscape that they are guide objects and must be displayed correspondingly. Other renderers will naturally just ignore then and yet we will be able to store arbitrary SVG for our purposes.
I think the best thing to do would be keep them in a <defs> as you suggest, but instead of a special attribute reference them at their place of use with an inkscape-namespaced element that behaves like <use>, but creates guides rather than normal rendered/editable instances.
Directly rendering objects in <defs> is probably not a good idea.
-mental