In my understandign there are two different cases: 1. mask/clippath object is leaved in the document 2. clipping object is moved into defs, but removed from document (no longer visible)

For the first case, I guess the simple approach would be to have something like: <defs> <clipPath id="clipPath123"> <use href="url to the clipping object(s)> </clipPath> </defs> <g clip-path="#clipPath123"> ... the clipping object(s) ... ... the clipped objects ... </g>

This leaves clippath in defs and allows edditing of a mask directly by editing a clipping object. This can also be implemented without a group and it should still work

But for second scenario (object is removed) editing is more complicated, but we can still have this grouping and on entering (dbl-clicking) a group, clipping objects can be copied to a group, so they can be edited, after leaving a group copied object properties goes to a clipPath element and copied object is restored. Or a new manu item "Edit clip path" can be added, which will do basicly the same, but group will not be required, so this can also be used for masks created outside of Inkscape.

Andrius

On 3/18/06, bulia byak <buliabyak@...400...> wrote:

On 3/17/06, MenTaLguY <mental@...3...> wrote:

...

If the clipPath and the clipped objects share a parent group, then you get "compensation" for free.

Not entirely for free, and in any case no more free than when they are elsewhere. Here's the scoop: The spec says that any transform= on clipped object affects the clippath as well, and we implement this. Therefore, for objects that always get transform= such as groups or ellipses, you get transforming the clippath truly for free, and this does not depend on where is the clippath - in defs or in group. It works the same both ways. However for objects that completely or partially embed the transformation, we will need to either (a) disable that and write transform= if there's a clippath or mask, or (b) add transform= to the clippath/mask corresponding to the embedded portion of the transform. Both approaches are relatively easy to do. Your approach (always putting clippend object(s) in group with clippath there too) is just another way of doing the (a) - you just disable embedding transforms into the object by virtue of its always being the group. However for that you have to pay the price of an unavoidable extra level of <g> and the dangers associated with resources-not-in-defs which our legacy code is known to mishandle often.

...

Unlike gradients, I don't see a strong case for re-using clipPaths either (another usual motivation for putting things in <defs>).

Sure, I don't want them to be shared either. It's not about sharing or not sharing.

...

Keeping the clipPath with the clipped objects seems to be the simplest approach...

I don't think so, see above. Besides, if you rely on your clippaths always inside groups and thus do not implement (a) or (b) above, you will damage your ability to gracefully handle non-Inkscape SVGs.

-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

---

This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmdlnk&kid%110944&bid$1720&dat%1... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel