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