On Fri, 2007-10-05 at 07:41 -0700, Redefined Horizons wrote:

You wrote: "You should look through the INX files in Inkscape..."

I really did look at some of the INX files. I opened at least 3 or 4 of them, but couldn't find what I was looking for. I think the dummy INX file that you attached will get me going in the correct direction.

I find it useful to grep for things I'm looking for in that directory. So something like this would give me the list of all INX files that have enums in them:

grep enum *.inx

Maybe you could help me with a couple questions in this regard. I was trying to add the PyGTK modules to my Inx file. But I wasn't sure if they should be labeled as "executable". Is there a more appropriate term, like "library", or do all Python modules used in my script need to be labeled "executable" in my INX file?

You don't need to specify the modules in your INX file. The dependency checking that Inkscape has isn't very smart, it is only the basically looking to see if a file exists in the path or in the extensions directory. It doesn't know about how to load Python modules or anything like that.

Also, what version of the Python interpreter is used by Inkscape? Is it the Python interpreter I have installed on my system, or is it an embedded interpreter? I need to make sure that my PyGTK and Python versions are matching up.

On Linux, Inkscape will use the python interpreter from your system first. You can overwrite that in your settings if you like. On Windows, it will use the version of Python that is packaged with Inkscape, which I believe is 2.5.

Thanks for all the support guys. This is really great and unexpected!

No problem Scott. In the Inkscape project we believe that success is determined by the number and quality of contributions. We want everyone to be able to contribute what they can.

--Ted