Btw, the requirements we've identified so far (but probably incomplete) for our Extension system is itemized here:
http://www.inkscape.org/cgi-bin/wiki.pl?PlugIns
Bryce
On Fri, 20 Feb 2004, Bryce Harrington wrote:
On Sat, 21 Feb 2004, Charles Goodwin wrote:
On Sat, 2004-02-21 at 03:21, Bryce Harrington wrote:
- Write an extensions/plugin enhancement proposal(s) and post to mailing list for review
[snip]
The extensions proposal is necessary for this release because implementing a solution will be the focus for next release. Multiple proposals is fine, but we need at least one, and we'll need concensus on which to use by the time we finish cutting this release.
Please consider liasing with Jody Goldbery who is doing a lot of work on libgoffice. Part of libgoffice is a plugin/extension framework.
Yup, we're aware of libgoffice. I'm hoping someone will submit a solid proposal for it, that will explain how using it would be better from other options we're considering.
Note that we won't be adopting any solution blindly. I think we are best served to lay out all the possible options and weigh all the pros and cons, and select the approach that is the all-around best.
I've asked a couple Inkscape developers to look into libgoffice, but initial feedback suggests the choice is not totally clearcut, so we're going to need to go through a process to examine options. I would love to see a sales pitch made by someone more familiar with libgoffice's capabilities, particularly as it relates to Inkscape's needs.
I'd love to see libgoffice give us a perfect solution, as it'd save us a ton of time. We'd be able to focus on making extensions (or making inkscape itself pluggable into other things), but it's critical that the extension system we select will meet our requirements, as we plan to make heavy use of it. A good extension system will help us scale our developer base beyond what can be achieved otherwise.
Bryce