Hi,
atm,
I agree it can be done with the actual representation, I even used to do it using the boolops lpe, with the "identity B" operation (!) (althought I had troubles with transforms).
But this is somewhat strange, since the "clone" lpe would be applied to... no path. It sounds like a hack. Does the node tool agree working with empty paths? Should a default meaningless path be provided??...
Moreover, I feel we will meet the "transform" issue again. I did already insist too much on that so I won't take it again, but I'm still not convinced we handle transforms correctly. It's another issue anyway (talso concerning the xml representation however...).
Cheers, jfb.
2009/8/3 bulia byak
<buliabyak@...1857...00...>
This is absolutely doable with the current representation. We just
need to add a trivial "copy" LPE which will link to some path and
create a copy of it, just like the pattern-along-path now links to the
pattern path. Once you get such a copy, you can stack other LPEs on
it, and the copy will be live just like with clones (or like with
linked offset, which also must be migrated to a LPE). We already have
link LPE parameter and some UI for it, so it just needs to be coded.
No need to change anything in XML representation for it.