[Qgis-developer] Improving ftools geoprocessing tools
a.neumann at carto.net
Thu Oct 22 06:13:30 PDT 2015
If we'd replace the ftools (vector and raster menu) through processing.
What would replace them? Would we do research and see which of the
alternative processing providers provides best speed/reliability - if
there are multiple versions? It may be, that for Algorithm A, Saga works
best, whereas for algorithm B GRASS is better and for C GDAL or the QGIS
builtin in mechanism.
On 22.10.2015 14:59, Victor Olaya wrote:
>> * Why is the processing toolbox not an option for your users? (Do you
>> require shortcuts (menu entries) to the tools? Is it the parameter
>> interface which is more fine-tuned? Missing functionality?)
> If what you need is to have the tools in a menu, we have been
> discussing that before, and the idea is to mantain the same menu
> structure if the users wants that, but have the algorithms based on
> Processing to avoid redundant (and more difficult to mantain) code. As
> I said, this has already been discussed, but it is not yet
> implemented. Maybe your funding could help us do it?
> And if algorithms are not performant enough, it's clearly better to
> put your effort in the Processing ones (which, in general, are just a
> copy of the ftools ones), and have them exposed through the menus, as
> explained above.
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
More information about the Qgis-developer