On 14 September 2016 at 11:20, Matthias Kuhn <[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.
overhead? > > * Port some processing core classes to C++, mainly GeoAlgorithm, > outputs and parameters (and possibly some dependencies). I would be against this... I would leave Processing as pure python core plugin allowing it more dynamic respect qgis release > * Ship it as a separate module and do it all the grass/saga etc. way. IMHO the best solution... what is your use case to justify a different workflow? > 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 cheers _______________________________________________ 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
