Fail to install with Inkscape 0.46

[GoogleCodeExporter]

As there is no 'effects' menu entry anymore, the export to tikz entry does
not show up.
Changing the .inx files accordingly also does not work. I can't seem to get
the 'export to tikz' feature to appear anywhere in under the extensions menu.
Any quick'n'dirty fixes?

Original issue reported on code.google.com by maurits....@gmail.com on 1 Sep 2009 at 2:18

[GoogleCodeExporter]

Could you give some details about your operating system? I have used the script 
with
Inkscape 0.46 before, so it should work if Inkscape finds the extensions. Have 
you
tried 'Save as TikZ' instead?

Original comment by kjel...@gmail.com on 1 Sep 2009 at 5:36

• Added labels: Type-Other
• Removed labels: Type-Defect

[GoogleCodeExporter]

I'm running inkscape 0.46 beta on Ubuntu 8.04. Yes, I tried saving is as TikZ, 
there
is no option there either. I've had to change a few lines in the .idx files for 
some
other extensions to work in 0.46, mainly the textext extension. Can't seem to 
get
inkscape find the extensions in this case.
If you had it running under 0.46, could you send me your .idx and .py files and 
I can
have a look.

Original comment by maurits....@gmail.com on 2 Sep 2009 at 12:17

[GoogleCodeExporter]

I have used the idx and py files found on the project home page.  Have you 
remembered
to copy every dependency to the same directory as the tikz_export.py file? 
(inkex.py,
simplestyle.py simplepath.py should all be in the  home/.inkscape/extensions 
directory) 

I did a sudo apt-get install inkscape and followed the above instructions. The 
script
showed up in the extensions menu. There seems to be some issues with clipboard
support though. I will investigate that later. 

Original comment by kjel...@gmail.com on 2 Sep 2009 at 6:44

[GoogleCodeExporter]

Hmm. I'm a bit puzzled. Yes, I copied all the files into 
$HOME/.inkscape/extensions,
including inkex.py etc. Nothing shows up.
I am using the jaunty inkscape beta version from
http://ppa.launchpad.net/inkscape.testers/ppa/ubuntu, which is called 
0.46-devel and
shows up as 0.47 in aptitude (I should have made that clearer right from the 
start) .
So maybe that's the problem? Mind you, the new inkscape version has a few 
changes in
their extensions format, I believe. 
However, as I explained, for at least one other extension (textext) it was just 
a
matter of changing a few lines of code in the .inx file.

Original comment by maurits....@gmail.com on 2 Sep 2009 at 9:05

[GoogleCodeExporter]

I have only tried the 0.47 development version on Windows. The extension works 
there.
I will try and see if I can get 0.47 working on my Ubuntu-box later. 

If I remember correctly, there is a file called extension-errors.log somewhere, 
where
errors related to extensions are logged. Maybe you can find some hints there. 

Original comment by kjel...@gmail.com on 2 Sep 2009 at 9:20

[GoogleCodeExporter]

I had a look at the extension-errors.log file, however nothing shows up there 
(in
0.47 the extension-errors.log is in $HOME/.config/inkscape).
Let me know if you can come up with something on your linux machine.

Original comment by maurits....@gmail.com on 2 Sep 2009 at 9:29

[GoogleCodeExporter]

Just wondering, whether you've had a chance to look at the compatibility issue 
with
inkscape 0.47?
Unfortunately, my python skills are quite rudimentary... 

Original comment by maurits....@gmail.com on 5 Sep 2009 at 10:07

[GoogleCodeExporter]

I'm sorry, but I have not yet installed 0.47 on my linux machine. I fixed a few 
bugs
recently that prevented the script from running properly, but the extension 
should
still show up in the menu. 

Original comment by kjel...@gmail.com on 5 Sep 2009 at 5:20

[GoogleCodeExporter]

I just installed 0.47 and I can confirm that extensions put in ~/.inkscape/
extensions/ are not loaded. I put the files in /usr/share/inkscape/extensions/ 
and 
the extension worked fine. Seems like they have changed where extensions are 
loaded 
from. Need to investigate this more. 

Original comment by kjel...@gmail.com on 5 Sep 2009 at 8:12

[GoogleCodeExporter]

It turns out that the correct directory for 0.47 is 
~/.config/inkscape/extensions/

Original comment by kjel...@gmail.com on 5 Sep 2009 at 8:34

• Changed state: Fixed

[GoogleCodeExporter]

Great. I did some testing and all works well now. Thanks a lot.

Original comment by maurits....@gmail.com on 10 Sep 2009 at 11:32

[GoogleCodeExporter]

Hi there,

I installed this successfully, but when running the exporter, I get this error 
message:

The fantastic lxml wrapper for libxml2 is required by inkex.py and therefore 
this
extension. Please download and install the latest version from
http://cheeseshop.python.org/pypi/lxml/, or install it through your package 
manager
by a command like: sudo apt-get install python-lxml

I am a little bit confused, because I am on OS X and I have only installed X11,
Inkscape and inkscape2tikz. What do I need more?

I would be thankful for any help!
greetings

Original comment by PooMu...@gmail.com on 14 Apr 2010 at 2:20

[GoogleCodeExporter]

lxml is bundled with Inkscape and it should not be necessary to install it. It 
seems
that lxml is not on your python path when the script is run. Where have you put 
the
extension files?

Original comment by kjel...@gmail.com on 14 Apr 2010 at 6:20

[GoogleCodeExporter]

Thank you for your help, kjellmf

Hmm..maybe LXML and python are already on my machine? Where is typically the 
install
path? If it is already installed, I don´t need to reinstall. Because I could
successfully install Inkscape on my machine.

I put inkscape2tikz in the directory, where your website pointed to. It is in 
my home
folder:

~/.config/inkscape/extensions

And I put these files in it:
simplepath.py
simplestyle.py
tikz_export_effect.inx
tikz_export_output.inx
tikz_export.py

I only installed Mac Tex 2009 (http://www.tug.org/mactex/2009/aboutmactex.html) 
in
Mac OS X 10.6.3

I would be very thankful, for an advice.

Original comment by PooMu...@gmail.com on 3 May 2010 at 10:15