Hi all, I think this new approach is more or less the same approach used in the early times of Sextante, before it is ported to QGIS core and become Processing.
I remember that Sextante at that time had a very good feature, being an external plugin, that was the updates. They were not dependent of the QGIS release schedule, and so bugs were solved and new versions made available very quickly. Having the providers as plugins, we will regain this flexibility. The counterpart is that there may be providers that may no longer exist in Processing, due to lack of workforce. But getting them integrated, without this workforce, lacking maintenance, is not a good idea either. So I think this new approach, taking pros and cons, might work well. I understand Rashad who thinks it would be better to have all providers, out-of-the-box, after installing QGIS, but we can not get the best of both worlds in just one. And it seems to me, that OTB's integration into QGIS is assured, at least as much as it depends on Rashad's will! Best regards, Pedro 2018-02-02 11:11 GMT+00:00 Paolo Cavallini <cavall...@faunalia.it>: > Hi Rashad, > > Il 02/02/2018 10:47, Rashad Kanavath ha scritto: > > > A user of application can select -type gaussian -type.gaussian.radius 3 > > when launching application. > > otb application check for invalid cases such as if type is gaussian then > > one cannot use -type.mean.radius > > This is okay for command line, but for graphical interface one has to > > hide /show parameters based on the value of it's parent. > > > > This is a limitation of qgis processing that upstream was forced to > > split applications based on group. I am not blaming or targeting here. > > Just saying about a missing feature for support for one provider. > > Very interesting. Wouldn't make sense to have it upstream? This would be > useful also for other providers. > > > QGIS users now have three application for smoothing and maybe 10 or > > more application for TrainImagesClassifer. > > This was originally made on purpose, with the idea of having simplified > atomic commands. Nowe the ecosystem is more riche, and there is room for > more complex interfaces. > > Thanks for your input. > > -- > Paolo Cavallini - www.faunalia.eu > QGIS & PostGIS courses: http://www.faunalia.eu/training.html > https://www.google.com/trends/explore?date=all&geo=IT&q=qgis,arcgis > _______________________________________________ > QGIS-Developer mailing list > QGIS-Developer@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer >
_______________________________________________ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer