Save pxo to a proposed text pxo format to allow efficient storage in version control - like LibreOffice allows with .fodt instead of .odt

[brancoliticus]

I would suggest that whatever you are doing with the pxo format to squeeze every last piece of space efficiency should have the alternative of being stored in a textual format to allow for efficient version control storage.

Nothing fancy - just the simplest possible textual implementation - git will sort itself out to obtain the version control efficiencies I am referring to. Hopefully there is no roadblock in the sense that your pxo format creates a lot of random stuff in the diff between two versions of the same project that have minor differences between them resulting from minor editing.

Keep in mind that in git just archiving a text file and a minor version of it and trying to put the two in will have the result that tiny differences in text make doubling the storage required when using the archive format. There are no efficiencies to be had when there isn't a lot of data kept in the file between the two logically minor versions of it. Small differences in logical changes to the project resulting in small differences in the output pxo or mabe future text pxo would make git work wonders when doing version control.

Thanks for the nice tool that Pixelorama is :).