On Tue, 2007-04-17 at 14:49 -0500, Bob Jamison wrote:
Look at InkscapePython. You can see that I only have Inkscape, Document, Desktop, and DialogManager stubbed.
I'm honestly not to thrilled about this. Any API that we choose here than has to be supported forever. I don't think we want to support the interfaces on those objects for that long.
DOM, we'll need to support that at the various levels also, but I'd really prefer to not have much of a custom API. Perhaps something generic like call effect? Pretty much anything can become an effect.
- Some help on launching python scripts internally as an alternative
to shelling out.
I'm for this, but I think that we don't need any internal APIs for that.
- Some fun ideas on what easily-bound things we would like to
add initally. I have a difficult time having creative ideas, but this is a very creative crowd here. I know that we need to script both Repr and DOM, but those are a lot more work and will take a bit longer.
I don't think we need to expose Repr at all. DOM should be sufficient for that.
This is separate from the much larger DOM-JS binding stuff. But PyCxx is a good example of how to efficiently do the binding, which I will try to learn (steal) as much as I can. :-)
I'm still a touch concerned about loosing SWIG, it means that we loose out on several of the languages that SWIG supports. I would hate to see us have to implement the same interface code to lots of different language interfaces. I don't think we should implement that functionality ourselves.
--Ted