On 09/14/2016 11:32 AM, Nyall Dawson wrote: > On 14 Sep 2016 7:20 PM, "Matthias Kuhn" <[email protected] > <mailto:[email protected]>> wrote: >> >> Hi, >> >> If one wants to create a C++ processing algorithm, is there any >> preferred way to ship it? I don't think we are doing that yet apart from >> calling 3rd party tools. >> >> The possible approaches I can see are >> >> * Add a new QGIS module "algs" next to gui/core etc and use >> it's python bindings to call the code from a small python wrapper. > > So it would sit between core and gui (ie no widgets)?
That should go into a separate module. I'll need to ship different QML widgets instead. > > I'd lean this way, but am wondering why not just put the code in core? > What specific algorithms do you have in mind? Separation of concerns ;) Basically rendering tiles into a geopackage. Matthias > > Nyall > >> >> * Port some processing core classes to C++, mainly GeoAlgorithm, >> outputs and parameters (and possibly some dependencies). >> >> * Ship it as a separate module and do it all the grass/saga etc. way. >> >> Context is, I will probably need this on QField with no python. I could >> do it without processing there but since the trend is to processize >> whatever possible, I thought it would be a good opportunity to bring >> this subject to the table. >> >> Matthias >> _______________________________________________ >> Qgis-developer mailing list >> [email protected] <mailto:[email protected]> >> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer >> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer > _______________________________________________ Qgis-developer mailing list [email protected] List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
