Il 08/08/2016 03:00, Nyall Dawson ha scritto: > On 8 August 2016 at 10:36, Chris Crook <[email protected]> wrote: >> As an alternative to building and maintaining a bunch of translation code, >> how feasible would it be to build something like a python project migration >> tool? >> >> I'm not very familiar with the project XML structure but I'm wondering if it >> could be done using a python xml library which could update the appropriate >> bits of the project file without needing to handle the full structure (eg >> using libxml or something like that). That would provide some support to >> users if their projects were broken by the updates without adding to the >> core code base. (Similar idea to python 2to3 tool, but a lot simpler of >> course). It needn't be perfect - if it handled 95% of cases then that would >> still be a great improvement. > > That's a good alternative. The conversion wouldn't actually be that > complex - it's just a matter of time really. > >> >> Note that while 2.6 may seem ancient history from a developer point of view, >> for users in secured corporate environments it can be difficult to get newer >> versions of software approved and installed. I suspect that running older >> versions is more widespread than you might think! > > Sounds like a perfect opportunity for one of these companies to step > up and sponsor this work...
Hi all, agreed: * let's drop compatibility * make this very clear in release notes * offer the opportunity to sponsor an external utility (a plugin?) to convert old project. Thanks. -- Paolo Cavallini - www.faunalia.eu QGIS & PostGIS courses: http://www.faunalia.eu/training.html _______________________________________________ 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
