The Project file format, while being a plain text, makes version controlling a huge pain because of the way the assignment of project items into groups is done. If any item gets reassigned to a different gruop, the numeric item IDs in the group definitions change heavily.
This problem is much-much worse when doing development in multiple version control branches and merging the stuff between them.
While not completely impossible to merge the project files with some pre- and post-processing via GAWK, it would still be more reasonable to switch to some better, more easily structured/read/written/merged format... like XML or JSON or whatever.
A suggestion: The same could be done to Preferences files.
This problem is much-much worse when doing development in multiple version control branches and merging the stuff between them.
While not completely impossible to merge the project files with some pre- and post-processing via GAWK, it would still be more reasonable to switch to some better, more easily structured/read/written/merged format... like XML or JSON or whatever.
A suggestion: The same could be done to Preferences files.
Last edited:
