2008/9/3 Maximilian Albert <Anhalter42@...173...>
bulia byak schrieb:

 > I think we will need to store widths not per node, but as a list of
 > length along path/width pairs, with length measured in percentages
 > of the total length of subpath

That's an excellent idea. Since I had something like Pajarico's other
suggestion in mind (see different email), I was thinking about how to
store per-node information. But separating the width info from nodes and
storing it in the described way will make the LPE very powerful and
flexible.
 
Its an excellent idea until you make any change that substantially alters the path length, at which point all your widths 'slide' along the path when you didnt want them to...

> And finally, for the actual profile shape I think we should use a
> Spiro path for extra smoothness and natural flow. However, if we want
> to eventually support sharp width changes, we will need to store for
> each point its type - whether it is a smooth Spiro point or a cusp
> point.

I'm not sure if I understand you correctly here (in particular: what do
you mean by "profile shape"?), but why not apply the LPE to any path
whatsoever? The 2geom routines are flexible enough to make this
possible. If you want it to be on top of a spiro path, just use LPE
stacking.

Max

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel