I was thinking of adding a python scripting interface to dia. From what I
can see, it should be possible to make it into a shared library, just like
the object libraries. One question though is where to put it in the dia
source tree? Its interface with the rest of dia would be closest to that
of the libraries in objects/*, but it won't add any extra objects for dia
to use. Would it be more appropriate to create a new toplevel directory
for things like this?
It would also be necessary to add a few more APIs to dia/lib.
Specifically a way to add extra menu items. At a minimum to the right
click diagram menu, and maybe also the toolbox's menu as well. It would
be nice if this allowed adding a pixmap to the menu item if gnome support
has been enabled, but this is not necessary.
For any of these support features, I don't want to make them python
specific -- I am sure people might want perl, tcl or guile bindings as
well.
I aim to make the bindings capable of fully manipulating a diagram, and
also accessing any properties of objects (this was one of the motives for
wanting standard set/get property functions for objects :). The idea
being that they be powerful enough to write filters to import/export UXF
or XMI files to dia UML diagrams, or export a SPICE network from a circuit
diagram.
I also have a bit of code that would also give an interactive console
(written using pygtk) to alow you to programatically modify the diagram.
What do people think of this?
James.
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
