[Qgis-developer] QGIS Processing Framework

Camilo Polymeris cpolymeris at gmail.com
Wed May 11 11:24:39 EDT 2011


> - Even though its clear that the main objective is to have this framework
> well integrated in Qgis, it would be nice if it could be accessed without
> running Qgis, at least for the "back end" part. Being able to access it
> through a standard Python shell would be very usefull. I think it converges
> with Paolo's idea of having a scriptable Qgis.

I will try to keep separeted what depends on QGIS-Core and what
depends on QGIS-GUI. One reason to move everything UI-related to the
QGis side is precisely that: so the backends will be usable in other
contexts.

> - Having the backend accessible through a C/C++ interface would then be
> great , so that we can access it not only from Python, but also from other
> non-Python-compatible langages/applications (say Java for example, to be
> able to integrate it in current state of the art WPS implementations)
>
> - Being able to run each module GUI independently, outside Qgis, would be
> nice also. Less sure on this one... At least not the priority.

Could be done, I guess, would just need a non-QGIS reimplementation of
the front-end that talks to the modules through the same API. E.g. web
or command-line frontend is very plausible, but would need a lot of
work, of couse.

> For the OTB modules we have some other target applications where we would
> like to push our modules. I'm now seeing things in a much wider scope thanks
> to this discussion, and I'm telling myself we should handle things one step
> above : it is probably the Qgis framework that we will want to wrap in other
> applications.
> As already said, using as much manpower as possible from the open source
> community is important so that it becomes a success story.

Feedback from other application's developers that could wrap this
frontend would be appreciated, to see if the current incarnation of
the design fits their needs. Of course, the primary goal is to make it
work for QGIS, but flexibility is a good thing, IMO.

The "design document" is, as always, here:
https://github.com/polymeris/qgis/wiki/QGIS-Processing-Framework
And I have started writing Python stubs, here:
https://github.com/polymeris/qgis/tree/master/python/processing

Please, correct or comment.

Regards,
Camilo


More information about the Qgis-developer mailing list