On Tue, 2014-02-25 at 19:17 +0100, Krzysztof Kosiński wrote:
As a backup option, I'm considering changing my MSc project to implementing a Python scripting console for Inkscape. If I were to pick that instead, the GSoC project could involve a variety of refactoring tasks intended to simplify writing the Python bindings used by the console.
Wouldn't it be better to complete the DBus bindings for inkscape? Python has a very good dbus implantation that could be effectively wrapped for such a thing allowing process separation between python code operating on drawings and inkscape codebase.
Then it's just a matter of launching extensions with the dbus drawing id and let the wrapper take care of interacting with inkscape. you could have a python shell, live drawing extensions... lots of things really.
The tricky point is getting dbus working on windows. http://www.freedesktop.org/wiki/Software/dbus/#index6h1 It should be possible to depend on the in-tree windows port from fdo's development branch if it works. Since it's windows we don't need to care too much if something is packaged or stable beyond stable enough for inkscape.
Martin,