Hey Aaron,
Thanks a lot for the links to the mail discussion. Very very helpful! I think you won't mind me throwing this on the devel maillist?
From what I gather from the discussion, no consensus was reached on the
SVG representation. Perhaps it is best, like Bulia said, to first make it working the 'ugly' simple way,
<path original-d= ... d = ... path-effect="sample" path-effect-param1="0.0" path-effect-param2="0.0" path-effect-param3="0.0" path-effect-param4="0.0" />
Then we can see what needs to be improved, what UI needs there are etc. Does that make sense? Once I have this working, we can discuss how to make a more versatile SVG representation.
I want to make skeletal strokes first, because it also probes for on-canvas UI needs (on-canvas parameter editing).
<path original-d="..." (input curve) d = "..." (result curve) path-effect="skeletal_strokes" (how are we going to name the effects?) path-effect-param1="..." (input curve) />
Cheers, Johan
On Sun, 2007-04-15 at 22:13 -0500, Aaron Spike wrote:
I'm already sick of typing Live Path Effects over and over so I'm abbreviating. :-)
I believe we can harvest a diff of my changes on the branch with a command like:
svn diff --new=https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/branches/live...... --old=https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk@...1725...
Now this takes a long time to execute and I haven't stuck it out all the way yet. I'll try to remember to leave it running when I go to work tomorrow. The idea is to diff the current head of the branch with the last revision merged in from trunk. I think reading this diff will give you a pretty good idea of what has been done so far.
Aaron Spike