
Hi!
I just do not get, why we cant *reference* separate .svg files from a main one. So it looks like, we have all icons in a single svg document (so easy for the designers), but in reality it does not contains all the icons but references them. So when editing it edites the referenced .svg file.
With this setup we could have each icon in a separate .svg file, and we could also have a main .svg document which displays all of them.
I do not know what is the most standard compliant way to implementing it, maybe the <image> element?: http://www.w3.org/TR/SVG/struct.html#ImageElement
It would be useful for many usecases, like drawing a schematic, where each symbols located in different files. (Im using inkscape for drawing power electricity, but for now I copy the symbols, the safest way.)
Best regards, Khiraly
On Wed, Feb 11, 2009 at 5:49 AM, Jon A. Cruz <jon@...18...> wrote: et the system
use it's file-based approach. That has many problems.
It also has one big advantage, namely you don't have to dig in the source code to discover which icon names you need to provide in your theme. The monolithic icons.svg file is also fairly unobvious to theme designers.
There are many other ways to approach this. One would be a simple XSLT run on the icons.svg to generate a list of icons. Other things could be done, but that one might be the simplest and most web-developer friendly. And for a generic theme designer out there, Inkscape will happily go with any icons they've added in a standard themeing way. The single file is more for the Inkscape internal/built-in icons.