Sending this again because I never saw it come through on the list.
ted@...11... wrote:
On Tue, 12 Apr 2005 aaron@...749... wrote:
Ok. I spent a little more time on this. In script.inx file, this works on Linux:
<command reldir="extensions">script.py</command>
And this works on Windows:
<command reldir="path">python "C:\Path\To\Script\script.py"</command>
What is the proper syntax for a write once run anywhere *.inx file?
Well, I think that the problem is that we don't have one. I'm open to suggestions. Does that mean that Windows won't execute the #! at the top of files?
Windows uses an association between file extension and applications that is stored in the registry.
I have a bunch of random thoughts/questions: -with option one can Inkscape be taught to call the script in such a way that windows can choose the interpreter properly (and function with pipes)? -what other platforms will have special nuances that need to be delt with? -with option two could the inkscape extensions directories be added to a search path environment variable (like java classpath) that is used by the interpreter to avoid absolute paths? -Could inkscape be given a more flexible way to construct the command line? eg. <interpreter reldir="path">python</interpreter> <scriptfile reldir="extensions">script.py</scriptfile> would yeild 'python "path to script/script.py" params...' -Could scripts run on the embedded interpreter?
Aaron Spike