Honestly I think script syntax wasn't that bad. At least it was quite easy for a set of power users, as I could verift during my past courses. Anyway I agree with the rationale: having a unified, pythonic way, to write both algorithms and scripts... well, might be the case to ultimately drop scripts?
Whatever the choice, we should make users aware of the current unclear situation, that things are being discussed and still evolving. This will prevent confusion and maybe encourage participation. How could this discussion be brought forward? My first question would be: do we still need scripts? In any case thanks to Nyall and the others for the great work! ;) Giovanni Il 27 gen 2018 12:15 PM, "Paolo Cavallini" <cavall...@faunalia.it> ha scritto: > Il 27/01/2018 00:39, Nyall Dawson ha scritto: > > > It's not too late to improve this for 3.x. Why don't we get the daily > > Python users and experts involved here and come up with a more > > Python-like approach to processing scripts? > > IMHO this is worth a wider announcement and call for help, if possible > with some kickoff instructions. > All the best. > > -- > 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
