Hey Nathan I agree with you, and I have been wanting to do this...but it requires some work, since not only the format has changed, but also the inner structure of the models. Unfortunately, I am not having too much time to work on Processing lately, but I guess it will be ready for the next release. I would be a pity to ship QGIS with the older version, since this new one has plenty of improvements and good new things
Thanks for the advice! 2014-08-11 5:03 GMT+02:00 Nathan Woodrow <madman...@gmail.com>: > Hi all, > > I have noticed that old models don't work in the new processing modeler. > This is really, really bad. Breaking a format is just as bad, or even > worse, as breaking a API. Users don't care (much) for APIs but they care > about formats and when they stop working people get annoyed. > > Processing is a core plugin and therefore people consider it part of QGIS, > changes in it effect us as a whole product. If I break one of my plugins > that hurts me, if I change a core format (e.g qgs, qlr) that hurts the > whole QGIS project. > > I can understand the need to move forward to something better, and the new > JSON format is much better then a custom format I will never argue for the > later. However not providing a way to import old models, or even doing it > by auto magic, is really bad. > > Some people invest a lot of time into creating models for processing and > having it break under them with no option but to recreate will leave a bad > taste with people, trust me on that. As processing has been "core" since > 2.0 you can expect a lot of models in the wild and a lot of annoyed people > if there is no option to upgrade. > > What I am NOT proposing is to revert that work, we do need to move forward > but I do think there needs to be a conversion function/s. > > However if it comes close to release and there is no conversion ability > then I would say we should revert the plugin in core and wait for the next > release to upgrade the models. Breaking the models on people with no > convert option will have much more effect then not having some of the new > features. > > Regards, > Nathan > > > _______________________________________________ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer >
_______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer