On Tue, 2008-02-26 at 09:15 +0100, J.B.C.Engelen@...1578... wrote:
To be honest, I find the 'extensions only' very limiting, so I like this compromise. Maybe incorrect, but I read the 'extensions only' as: python scripts only. I understand that new developers need time to get used to Inkscape's codebase, but devs like me can (and, personally, want to) go much much deeper.
I don't think that this means things have to be python. There are many non-python extensions. Some good examples would be the wmf importer, pdf (in and out) and all the bitmap tools.
In any case, my GSoC'08 ideas for my own application could be: -1- LPE plugins (note the word LPE in front. I really first want plugins only for LPE, not tools, not other things, just LPE. It's because I have no experience with any plugin system coding, and I already have a good idea of what API must be available for LPE plugins. So, although it sounds exciting to have pluginable code, don't expect too much !)
I would rather rephrase this: "integrate LPE into the current extensions system".
This should involve making a subclass of Inkscape::Extension::Extension for live path effects and adding the appropriate functions into the prototype of Inkscape::Extension::Implementation::Implementation so that implementations can be built. Also, porting the current LPEs to be subclasses of Implementation. Oh, and making the parameters do the local stuff.
--Ted