bulia byak wrote:
On 4/17/07, Bob Jamison <rwjj@...127...> wrote:
One thing we should start addressing again is the launching of extensions from an embedded interpreter rather than shelling out. Embedding Python has improved a lot recently, so I suggest that we try to run extensions with that first. We can expose Inkscape internals rather cleanly now.
That would be cool. Do you already have some proof-of-concept script accessing internals? Will it run from the Scripts window? If yes, can we finally edit the message in that window to remove the "this window has no functionality" part?
Thanks!
That message is only displayed if neither --WITH-PYTHON nor --WITH_PERL are set. I would suggest that people only use --WITH-PYTHON for the time being, since we should probably get that one working well instead of trying both at once.
All the script does currently is show the About screen as a proof of concept. Python's stdout and stderr are redirected to the output textboxes.
Look at InkscapePython. You can see that I only have Inkscape, Document, Desktop, and DialogManager stubbed.
What we could use is two things:
1) Some help on launching python scripts internally as an alternative to shelling out.
2) 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.
Script the Tracer? Script one or more of the drawing tools?
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. :-)
bob