Hi,
First sorry for my very bad english, i'm french (please excuse me!)
Then I would like to introduce you a concept that could be very interesting in Inkscape.
I'm used to Inkscape to draw a lot of interfaces going directly later in softwares we develop.
Just imagine a simple example : we use in interfaces some buttons or other kind of objects . So very often we are importing or cut/paste some objects from a master document (containing a lot of very often used objects) to a target document (a new interface for instance). Very often, also, we have to change a little thing in our interfaces we produce this way. Let's says we want to change the design of the buttons we imported. Today, what we have to do, is to open each interface document and to correct the little thing that changed (i.e. to reimport the design of buttons we saved in the master document). And that is using a lot of time, and very repeated operations.
So what we would like is that Inkscape gives the hability to many documents (and objects inside) not only to be imported (that is to say copied in without any link to the source document or object) in an another one but really to be linked together.
The structure could be like that :
Document Level 1 (ID D1) (Master) contains :-
- object1 (ID 11) ,
- object 2 (ID 12)
- and object 3 (ID 13)
Document Level 2 (ID D2) contains :
- object1 (ID 21),
- object 2 (ID 22),
- object 3 (ID 23)
- and object 4 (ID 24) itself containing object 2 from Document Level 1 and object 3 from Document Level 1
Document Level 3 (ID D3) (interface) contains :
- object1 (ID 31) itself containing object 4 from Document Level 2 and object 1 from Document Level 1
- object 2 (ID 32) itself containing object 1 from Document Level 2
How is produced D3 ? When opening D3, Inkscape could systematically import via a link encapsulated the objects coming from other documents :
D3 :
+ ID 31 :
---------> local (inside D3) objects
---------> ID 24 :
--------->---------> local (inside D2) objects
--------->---------> ID 12 :
--------->--------->---------> local (inside D1) objects
--------->---------> ID 31 :
--------->--------->---------> local (inside D1) objects
---------> ID 11 :
--------->---------> local (inside D1) objects
+ ID 32 :
---------> local (inside D3) objects
---------> ID 21 :
--------->---------> local (inside D2) objects
Now if i change the design of ID 12, ID 31 in D1, I would like that when opening D3, all updates of design are made in D3 dynamically.
This will be really useful not only for us, because when building (with this hability) documents depending from each other and able to store only link adresses (and not copies of objects!), this is a huge gain of time.
Imagine you want to round a square button, just do it in the master document, and automatically all documents will traduce the change when they are open (in fact nothing change in svg code because only the link adresse is inside)
What is strange is that this hability exist for a bitmap image because a link is effectively saved inside the svg code, but not a svg object or document. Why ??????????
If you do have answers or think it's a good idea to integrate to Inkscape code, let's say it here !
Thanks a lot in advance.
Regards.
Patrick.
Hierarchical (arborescent) structure of a SVG document
-
- Posts: 1
- Joined: Tue Feb 16, 2010 9:34 pm