use, xlink:href, and external svg
I have a group of SVG documents which have a lot of objects in common; what I'd like to do is have a 'library' document which contains defs of those objects and then reference them in the other documents instead of repeating them umpteen times.
I thought that I could achieve that by putting objects in the <defs> part of my library document, e.g.,
<defs> <rect id="somerect" ... /> </defs>
and then referencing the objects elsewhere like this:
<use xlink:href="lib.svg#somerect" ... />
This seems not to work with Inkscape. (It does seem to work with Batik, but not if the href URL is relative.) Am I doing this incorrectly or is it unsupported?
On 9/8/06, Joel Uckelman <uckelman@...2004...> wrote:
This seems not to work with Inkscape. (It does seem to work with Batik, but not if the href URL is relative.) Am I doing this incorrectly or is it unsupported?
Yes, external hrefs are not supported yet. Only within the same document.
Thus spake "bulia byak":
On 9/8/06, Joel Uckelman <uckelman@...2004...> wrote:
This seems not to work with Inkscape. (It does seem to work with Batik, but not if the href URL is relative.) Am I doing this incorrectly or is it unsupported?
Yes, external hrefs are not supported yet. Only within the same document.
Is this something for which support is planned?
On 9/8/06, Joel Uckelman <uckelman@...2004...> wrote:
Is this something for which support is planned?
Since this is part of SVG, eventually yes. But right now it's not being worked on.
Thus spake "bulia byak":
On 9/8/06, Joel Uckelman <uckelman@...2004...> wrote:
Is this something for which support is planned?
Since this is part of SVG, eventually yes. But right now it's not being worked on.
How hard would this be to add if I'm not familiar with the Inkscape codebase?
On 9/8/06, Joel Uckelman <uckelman@...2004...> wrote:
How hard would this be to add if I'm not familiar with the Inkscape codebase?
That largely depends on how good you are at programming in C/C++ :)
I think it's somewhat cumbersome. At the very least you'll need to complelely parse and load the external documents. I think Mental could comment further on what is involved in enabling cross-document references. Mental, could you please outline?
Thus spake "bulia byak":
On 9/8/06, Joel Uckelman <uckelman@...2004...> wrote:
How hard would this be to add if I'm not familiar with the Inkscape codebase?
That largely depends on how good you are at programming in C/C++ :)
Good enough, so long as external xlink support isn't an enormous job.
I think it's somewhat cumbersome. At the very least you'll need to complelely parse and load the external documents. I think Mental could comment further on what is involved in enabling cross-document references. Mental, could you please outline?
That would be great. Then I could get some idea of whether I want to dive in to do this...
On Fri, 2006-09-08 at 18:39 -0300, bulia byak wrote:
I think it's somewhat cumbersome. At the very least you'll need to complelely parse and load the external documents. I think Mental could comment further on what is involved in enabling cross-document references. Mental, could you please outline?
I'm less worried about parsing and loading the external document (most of _that_ code is taken care of by what we already have) than I am about coping with having SPObjects in the same object tree which belong to different documents. That's going to require some serious architectural work, I think.
I've got part of that work planned out already (namely, forcing all element creation to go through an XML::Session, so we can have multiple documents [fragments?] in the same transaction), but there's still quite a lot which would need to be done beyond that, particularly at the SPObject and SPDocument levels.
-mental
Thus spake MenTaLguY:
On Fri, 2006-09-08 at 18:39 -0300, bulia byak wrote:
I think it's somewhat cumbersome. At the very least you'll need to complelely parse and load the external documents. I think Mental could comment further on what is involved in enabling cross-document references. Mental, could you please outline?
I'm less worried about parsing and loading the external document (most of _that_ code is taken care of by what we already have) than I am about coping with having SPObjects in the same object tree which belong to different documents. That's going to require some serious architectural work, I think.
I've got part of that work planned out already (namely, forcing all element creation to go through an XML::Session, so we can have multiple documents [fragments?] in the same transaction), but there's still quite a lot which would need to be done beyond that, particularly at the SPObject and SPDocument levels.
-mental
Thanks for the explanation. It sounds like it won't be a small job like I'd thought, so I probably won't dive in and tackle it. Still, it's a feature I'd like to see eventually.
participants (3)
-
bulia byak -
Joel Uckelman -
MenTaLguY