
bulia byak wrote:
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.
And I have implemented it that way, and I see now that this is a very small very easily reworked piece of the code. (I forgot the "inkscape:" in my example, sorry.)
Unfortunately this is taking much longer than I expected.
Hey!
<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
Will the parser really be that covoluted?
which is rather a lot of work for the idea which is still untested in real life.
Um, I'm not saying we should drop everything and get this implemented immediately. I just want to discuss it and talk about proposed solutions to the problem before the time comes so we don't get stalled another few months with the discussion.
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).
Who said you get to have all the fun coding this? ;-)
Aaron Spike