[Qgis-developer] Re: import proprietary code inside a python plugin

[G. Allegri]

2012/3/27 Vincent Picavet <vincent.ml at oslandia.com>

> Hi,
>
> > In osgeo4w the gdal-ecw DLLs are released binary compiled. I never needed
> > to compile them by myself. Are you saying that osgeo4w is doing something
> > incorrect?
>
> The gdal/ecw case is particularly complex, as the ECW licence changes
> regularly and is some kind of opensource but not really.
>
> As for YOUR specific case, I think you should have understood by now that
> it's
> not possible to use Arcgis inside a python plugin, whatever the energy you
> deploy to try to convince the world to the opposite.
>

I don't want to convince anyone vincent :)
I'm just exploring the various corner cases to understand precisely what
can be done and what not.
It simply sounds strange to me that, somehow, ECW closed source code can
arrive into the QGis process space. It means there's a hole somewhere. Ok,
ECW releases the headers as open source, but the underlying SDK algorithms
and data structures aren't.
It follows that SOMEHOW some proprietary code can "infect" the purity of
the QGis process.
You can give me all the reasons, but I suppose that if it happens for ECW
it can be reproduced, SOMEHOW, for anything else.

For my plugin I already have decided what to do. This is a general question
now. If a Qgis user can leavarage a proprietary algorithm (ECW), anyway it
happens, it can happen again :)

giovanni
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/qgis-developer/attachments/20120327/229d9fe8/attachment-0001.html