On Thu, 4 Dec 2003, Nathan Hurst wrote:
Jonathan Phillips wrote:
Maybe his foundation could fund the development of the python scripting feature for Inkscape we've discussed implementing?
It's funny, I was thinking about how to implement scripting this morning before I'd heard of the bounty...
I'll leave it to someone else now, as they have incentive to do it! :)
I'd also love to see someone take this challenge on and implement it for Inkscape and/or Sodipodi. If anyone's interested, speak up, I think the rest of us would love to see the feature come to be.
Now, if no one wants to take it on individually, do we want to consider organizing an effort ourselves? E.g., we would create a requirements spec for the system defining our acceptance criteria and expectations, recruit a small team (2-3) developers to write the proposal, design spec, and do the implementation. They'd split the bounty and hold the responsibility for completing it, themselves.
Also, I notice that they did not specifically say they'd fund adding Python support to Sodipodi "and etc." but rather to write a spec for a universal scripting approach across multiple apps. So it might be hard at this point to make a strong enough proposal for this for Inkscape. This might be work-aroundable if the patch is submitted to both Inkscape and Sodipodi.
Another approach I've been kicking around is if we "stole" the plugin architecture/design from another project - Karbon14 has a plugin system, for example. Gaining the savings in design time would be the primary motivation, but conceivably the plugins could then be shareable or at least portable between the apps. No idea of the feasibility, though.
Bryce