![](https://secure.gravatar.com/avatar/bb65b6b3a109d97cf9f8d6c014ede042.jpg?s=120&d=mm&r=g)
On Wed, Sep 3, 2008 at 3:15 PM, Maximilian Albert <Anhalter42@...173...> wrote:
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"?),
It's the pattern path stretched along the skeleton path. It is generated automatically from the list of length/width pairs. I was just saying that the best way to do this generation is to let a Spiro go through the points, each point corresponding to one length/width pair.
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.
Of course. For arbitrary profile paths, we have the regular Pattern on Path LPE. But this one is just a specialization of that, it stores a list of length/width pairs, not the profile path itself, and regenerates the profile path when this data changes.