I plan to remove these two extension effects, please speak up if you disagree:
svg_dropshadow: writtern in Perl for which we have no support infrastructure on Windows; is really primitive, more a proof of concept than a useful effect. I suggest that if anyone wants to have such an effect, it's easier to rewrite it in Python using inkex, with gaussian blur and clones (but better wait until we have more SVG filters supported, which will allow us to have black shadows regardless of the color of the object).
Export groups as PNGs: seems to be redundant with the recent improvements in Export ("Batch export all selected objects") that do the same but in a more integrated and controllable fashion.
svg_dropshadow
Yes - voted to go.
Export groups as PNGs: seems to be redundant with the recent improvements in Export ("Batch export all selected objects") that do the same but in a more integrated and controllable fashion.
Cannot find that 'batch export' thing anywhere in 0.45.1
Can you leave the code for both in the extensions directory (whatever it is) because they could serve as tutorials in themselves? Perhaps make a new directory called "samples" and put defunct (and others) scripts in there.
/d
I have a general question about this: Do we want to support Perl in the future, or rather say that Python is the scripting language that Inkscape wants to support?
I don't use the scripting framework, so I don't really have an opinion. But I do know that it can be better to stick with one thing and do it well.
Speaking of Python, a reminder: Has anyone decided what to do concerning the demise of PyXML? It's dangerous for our complete script module to depend on a dead package. I looked, and Python now has its own XML API. Is there a reason that Python's own is not being used?
bob
On 4/1/07, Donn <donn.ingle@...400...> wrote:
Cannot find that 'batch export' thing anywhere in 0.45.1
It's in SVN (as are lots of other improvements)
Can you leave the code for both in the extensions directory (whatever it is) because they could serve as tutorials in themselves? Perhaps make a new directory called "samples" and put defunct (and others) scripts in there.
Non-working code is a bad teacher - it can't teach you how to make working code :) Any removed and unsupported code will bitrot over time and become dysfunctional. If you need samples, use the current working extensions.
participants (4)
-
Andy Fitzsimon -
Bob Jamison -
bulia byak -
Donn