[Kalzium] Porting kalzium to external Avogadro

[Pino Toscano]

Alle sabato 17 aprile 2010, Marcus D. Hanwell ha scritto:
> Avogadro searches for its plugins relative to the binary, which means
>  that the whole thing can be relocated. In the case of Kalzium this
>  breaks down though, as it may not be installed in the same relative
>  position as the binary. If both kalziuma and avogadro were in
>  /usr/local/bin, then the plugins would be found correctly for
>  example.

I see.
Attached there is a try in solving this issue, manually forcing the 
avogadro plugin directory by setting the AVOGADRO_PLUGINS evvar if not 
set. Not pretty, but I didn't find a way to make the PluginManager read 
also a new directory with plugins (loadFactories() looks doing 
nothing?).
Would this approach (ie making kalzium set the avogadro plugin directory 
instead of letting avogadro sort it out) be acceptable?

> The crash may well be due to some of the logic around the Python
>  threading code. I will look into this, as it never seemed robust
>  enough to me. I often build and test with Python disabled, but will
>  be certain to test things out with Python enabled too. The Python
>  threading was added later to facilitate multithreaded Python code (I
>  think - not certain on that as it was a while back).

Nice, thanks!

-- 
Pino Toscano
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kalzium-avogadro-plugins.diff
Type: text/x-patch
Size: 1661 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kalzium/attachments/20100417/2809545d/attachment.diff 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kalzium/attachments/20100417/2809545d/attachment.sig