Ted Gould wrote:
The basic module architecture right now is derived from the Adobe Illustrator plug-in model. There are some optimizations and changes, but that's where most of the ideas come from. I had looked at others, but the Adobe one seemed the most mature (surprise), flexible and reasonable. I think the basic ideas of 'load, unload, prefs, execute' will work for just about anything in the future. But, there are lots of things that Adobe and others have done, that we'll need. The future is bright, and I'm wearing shades :)
One thing to remember about the Adobe model is that they don't want other people poking around in their code, whereas we are/should be quite happy with people adding anything they like. For example, Peter and I have been working on a new improved grids and guides system, currently written in python. We'd like to just plonk this into inkscape and see how it works before commiting to spending a few weeks petrifying it into C(++). There's no way we can do this currently using the modules code, because we need to do things like add new tools and catch all edit operations.
njh