Ted Gould wrote:
- Add user extensions. Being able to correctly use
~/.inkscape/extensions to put extensions in.
- Fix the double window, make effects work like all the other entries in
the menu. I think this is what we meant when we started with "first class extensions"
- Grouping. There needs to be some way to organize the effects so that
they start to collect in submenus, in an orderly fashion. This functionality should also be extended to input/output extensions to make the open/close/import dialogs a little more orderly.
- Fix undo/redo. Currently effects don't work with undo/redo. The
effect subsystem should protect these from any extension -- they're very important to end users trying out functionality. If they loose work, they'll forever be scared of the Effects menu.
That's the order that I plan on tackling these in (though undo/redo may end up being second as I start playing with XML). Anyone who'd like to work ahead is welcome :)
Ted or anyone else who is willing-
I would like to make a plea that you rearrange these priorities just slightly. I think the number one priority at the moment should be making interpreted extensions run similarly on Windows and Linux using a single *.inx file.
Adding a property for interpreter and calling scripts by their full path should accomplish this.
In my mind this would make extensions distributable and ready for inclusion in CVS.
Aaron Spike