bulia byak wrote:
First comments:
- I enabled the Effects menu in preferences.xml and copied the inx and
py files from Aaron's tarball into ~/.inkscape/extensions. The new commands are in the menu but don't work. Is this supposed to work? If not why it picks them up for the menu?
- Then I copied them to /usr/local/share/inkscape/extensions/. Now the
commands in the menu work, i.e. at least say something in the console.
I believe Ted is currently working on this problem. The implementation of the user directories (./inkscape/extensions) is not yet finished. After that is complete there may still be a problem on Windows until the interpreter attribute is added to the inx files.
At first I got: File "/usr/local/share/inkscape/extensions/inkex.py", line 23, in ? import xml.dom.ext ImportError: No module named ext
I installed PyXML. Now I get instead:
File "/usr/local/share/inkscape/extensions/inkex.py", line 25, in ? import xml.xpath ImportError: No module named xpath
What do I need to install now? I see nothing appropriate in the Mandrake repository.
It will be difficult for me to weed out the appropriate packages since I have everything installed already.
In debian xpath comes from the python-xml package the files are found here for python 2.3: /usr/lib/python2.3/site-packages/_xmlplus/xpath You might look for the package which provides "pyxpath.py"
On Windows things should be a bit more simple. I believe I only needed to install the python package from python.org and PyXML. Though I did have pygame and numeric installed also, I don't think they helped much.
I haven't yet tested on Windows but I still think we must ship Python and all needed Python libs with the Windows package. (Or maybe make two packages, one with extensions and the other without.) This will save a LOT of trouble both to the users and developers. We have a tradition of shipping with "everything included" and it worked out extremely well, so let's stick to that. I think the python interpreter with the minimum of libs can be made quite small.
I agree with the "batteries included" approach. Things will be best for all parties if it "just works." Then again stripping it down to the bare essentials might limit what industrius new extension author are able to accomplish. I think someone should see how difficult it is to get them working on windows with a virgin install of python. If it only requires two packages,(as I think it does) it will be pretty simple to do anyway. I would probably consider that easier, since I don't know what is required to package python.
Aaron Spike