Accessing Inkscape API in external scripts
Hi,
From the thread about the Script Window i start to think how
to access the Inkscape API in external scripts.
I don't know if you already write something about this, but, if you don't may it help...
My idea is to say in the XPI "this script uses the Inkscape DOM" and the inkscape will talk with the script all the time, allowing this to use the inkscape like the user does...
The Inkscape must listen the commands from the script output and write an feedback in a pipefile for the script know what happens.
A sample bash script to fill in red an rectangle with id rect2:
#!/bin/bash pipe=$1 echo 'selectElementById rect2' testError "$( cat $pipe )" echo 'setAttribute fill="red"' testError "$( cat $pipe )"
I write 2 scripts to see if it's possible. inkSimulator.sh will do what the Inkscape must to do and externalDOM.sh will test it. See the simulation output: ___________________________________________________
$ ./inkSimulator.sh
The user has cliqued on the "External DOM Test" efect. The interface is disabled for the user interaction...
All the readed DOM commands gets an error response <error num>|<error text> No error returns something like this: 0|Ok
Trying to set the attribute fill...
Outch! I recived the error 2: Ups... no element selected
Trying to get the rect4...
Outch! I recived the error 1: The id rect4 do not existis
Trying to get the rect2...
Yeah! I recived the error 0: Ok, element rect2 selected
Trying to set the attribute fill again...
Yeah! I recived the error 0: Ok, attribute fill="red" seted in rect2
Nice! The "External DOM Test" ends. ___________________________________________________
I'm sending this scripts attached in the ink-dom-external-proposal.tar.gz to you see the code, if i was not clear. (English is not my language :-) )
It is a good idea? I think it can be easy to write scripts...
Thanks, Aurium
On Fri, 2007-02-16 at 23:13 -0300, Aurélio A. Heckert wrote:
My idea is to say in the XPI "this script uses the Inkscape DOM" and the inkscape will talk with the script all the time, allowing this to use the inkscape like the user does...
The Inkscape must listen the commands from the script output and write an feedback in a pipefile for the script know what happens.
I think that would be interesting. The problem here, mostly, is that we don't have the DOM completed. Otherwise I think it could be feasible. The trickiest part will just be handling all the scheduling. Currently Inkscape hands over execution to the script, so it is blocking. We'd have to have some sort of threading to make sure that Inkscape could respond to the DOM commands sent through the pipe.
--Ted
On Feb 16, 2007, at 11:18 PM, Ted Gould wrote:
I think that would be interesting. The problem here, mostly, is that we don't have the DOM completed. Otherwise I think it could be feasible. The trickiest part will just be handling all the scheduling. Currently Inkscape hands over execution to the script, so it is blocking. We'd have to have some sort of threading to make sure that Inkscape could respond to the DOM commands sent through the pipe.
SWIG
DOM Events.
:-D
On Feb 16, 2007, at 6:13 PM, Aurélio A. Heckert wrote:
I don't know if you already write something about this, but, if you don't may it help...
My idea is to say in the XPI "this script uses the Inkscape DOM" and the inkscape will talk with the script all the time, allowing this to use the inkscape like the user does...
The Inkscape must listen the commands from the script output and write an feedback in a pipefile for the script know what happens.
Hi,
My general expectation for this was that we would expose a live DOM via SWIG and then allow interaction that way. My personal preference would be to have one DOM that's the actual document itself and another for the UI (or at least a subset of it).
And then 2-way communication could be achieved via standard DOM events.
http://en.wikipedia.org/wiki/DOM_Events http://www.w3.org/TR/DOM-Level-2-Events/ http://xformsinstitute.com/essentials/browse/ch07.php#ch07-2-fm2xml
Then if you combine DOM, XML Events and a few other standard technologies, you get into XForms http://xformsinstitute.com/essentials/
participants (3)
-
Aurélio A. Heckert -
Jon A. Cruz -
Ted Gould