Re: [Inkscape-devel] Scripting

Hi, all... fretfind@...540... wrote: The with-perl and with-python sections of configure.ac have always been clunky and could use some improvement. Even when you use --with-perl and --with-python, they need to be found by the script. Unlike a lot of other libs that we use, those tools do not use libtool or pkg-config to report their CFLAGS and LDFLAGS information. Both Python and Perl have their own mechanism to report their embedding information. In both cases I think they are a bit clumsy also. Someone might want to look at that part of the script to see if they have any ideas. However, all you will get from the scripts right now are two stubs in both Perl and Python whose only purpose is to prove that scripting is plugged in. There is a hello() that does a "Hello, world." and an about() that shows the About dialog. That's it. I have spent the past few days working hard to get something working in DOM. Yesterday I got the XPath grammar started, and am now working on a new lexical scanner for it. Once the dom/xpath stuff is plugged in, we should be able to begin scripting Inkscape pieces like this: inkscape::eval("/inkscape/dialogManager/dialog[strokeAndFill].setVisible(true)"); So, Perl and Python should be able to affect Inkscape (and the document, too) when requested. And -finally- the JS lib that we have been carrying for so long will be usable, and will always be available. However, in the meantime, there should be nothing preventing anyone from scripting anything -outside- of Inkscape with Perl or Python. Bob