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
On Tue, 2005-04-12 at 18:04 -0500, aaron@...749... wrote:
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)?
I'm not sure of a way, and I'm scared of the registry -- if there was an easy way, I see no problem with doing that.
-what other platforms will have special nuances that need to be delt with?
All of them :)
-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?
I don't see any big problem with this, but it seems that using environment variables is out of style. I think that they can get a little bit crazy, and they are hard for most users to modify. I think we'd be better off with a preference.
-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...'
Yeah, I'm thinking this:
<command reldir="extensions" interpreter-type="python">script.py</command>
Then we can have one for perl/ruby/etc. without exposing the details to the inx file -- it could be a build time option if need be. So, basically that would expand to:
python /usr/share/inkscape/extensions/script.py
-Could scripts run on the embedded interpreter?
Well, we're not including the interpreters yet, and I don't that we want to include every possible interpreter that people might want.
--Ted
aaron@...749... wrote:
Sending this again because I never saw it come through on the list. ted@...11... wrote:
On Tue, 12 Apr 2005 aaron@...749... wrote:
<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.
It's possible to make use of this btw, so you CAN "execute" a python script directly. When using the command-line this can be accomplished by using "start script.py" and I believe the relevant API function is ShellExecute. Problems with this approach are that InkScape doesn't know for sure that the user hasn't meddled with his file associations to change this (the Python installer does set it up like this, but it can easily be changed) and it would only fix Windows, no other platforms would benifit from it.
Jasper van de Gronde wrote:
Windows uses an association between file extension and applications that is stored in the registry.
It's possible to make use of this btw, so you CAN "execute" a python script directly. When using the command-line this can be accomplished by using "start script.py" and I believe the relevant API function is ShellExecute. Problems with this approach are that InkScape doesn't know for sure that the user hasn't meddled with his file associations to change this (the Python installer does set it up like this, but it can easily be changed) and it would only fix Windows, no other platforms would benifit from it.
"start script.py" may not work properly with pipes.
Aaron Spike
participants (3)
-
unknown＠example.com -
Jasper van de Gronde -
Ted Gould