
On 4/26/06, Aaron Spike <aaron@...749...> wrote:
<path path-effect="sample" path-effect-param1="0.0" path-effect-param2="0.0" path-effect-param3="0.0" path-effect-param4="0.0" />
Sure, I never claimed this is the best layout. But it's fastest to implement. I proposed it as a quick way to get it up and running, to get at least a couple real effects working to test them in real life. Unfortunately this is taking much longer than I expected.
<path path-effect="sample1(param1:0.0;param2:loopy;) sample2(paramA:45;)" />
Looks good to me. But this will require writing a rather convoluted parser for the grammar, which is rather a lot of work for the idea which is still untested in real life.
So I propose to organize it like this: I think at this time you should concentrate on SPCurve distortion functions, port one or two real effects from Python, so we could test how effected objects behave in different situations, how easy it is to make them behave sanely, and if there are any gotchas in that (there may well be). After we're sure it's gonna work, I will code the parameter parser and the corresponding infrastructure in SPShape (this will require a PathEffect class storing its own params and a linked list of PathEffect instances). I think this is the best approach, with both of us doing what we can do best :)
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org