I am not entirely sure I am correct but I am pretty sure that when making a python extension - because its sandboxed to the included python executable - we can only import packages that are included with inkscape. We can't (say) do an import of something like matplotlib to get the svg and then bring it into an extension.

I imagine it's possible if you know the code well, and where to manually install external packages, but for most users this is too hard. People making complex extensions sometimes run into this problem.

Similarly Extensions that depend on IM have to use the included version. (Personally the IM limitiation has not caused me any problems)

On 12/5/2016 4:19 PM, Maren Hachmann wrote:

Hi Ken,

I'm not one of the developers, but as far as I know, only Inkscape extensions can currently depend upon IM. A quick search in my current extensions directory (the ones that come with Inkscape) shows that only the webslicer extension seems to have an optional dependency upon IM, for jpg and gif export.

So from this, I would conclude that for normal Inkscape usage, IM version is (mostly) irrelevant, but that if you install an externally created, user-contributed extension, that one may be incompatible (as this one seems to be for Windows, as a result of im fixing the problem with Windows having a 'convert' function already: https://github.com/giacmir/Inkscape-JPEG-export-extension/issues/14).

Please someone correct me if I'm wrong :)

See also: http://wiki.inkscape.org/wiki/index.php/Tracking_Dependencies

Regards, Maren

Am 05.12.2016 um 03:57 schrieb Ken Moffat:

...

There was a report to BLFS that not all packages which could use ImageMagick recognized the changes in IM7. So we reverted to IM6. Now that I've had time to look at this, inkscape is a major package in this category. ImageMagick-7 has changed a lot of things. And as somebody who uses ImageMagick tools, I don't want to be stuck with the old version.

Can I fix that ? Probably not, particularly with the move to cmake (I have no idea how to deal with different versions of a package in cmake, unlike configure scripts where there are usually things to copy).

Perhaps I can start to take a look when I get some time. But what I will need is an idiot's guide to what IM brings to inkscape, so that in the (unlikely) event that I produce a patch I can test it to see if it works. For the moment, all I know is that inkscape can use IM

• but the details/benefits elude me.

Any pointers, pretty please ?

ĸen

---

---

Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

---

No virus found in this message. Checked by AVG - www.avg.com Version: 2016.0.7924 / Virus Database: 4728/13535 - Release Date: 12/04/16

On Mon, Dec 05, 2016 at 03:21:13PM +0100, Maren Hachmann wrote:

Ah, I see now, it's even in the CMakeLists.txt. Seems to be required for "raster extensions (those written in C) and image import resolution" and is ON by default (but can be deactivated). Sorry for wrong info! The files I'd look at for the extensions would be src/extension/internal/bitmap/imagemagick.h / .cpp - for the import resolution, don't know. Regards, Maren

OK, thanks to you both. I'll need to google for extensions, to see if I can find something which even I can test.

Cheers.

ĸen