On 12/6/2013 2:18 PM, Jeremy Sanders wrote:
I didn't really understand your point about storing in HDF5 before. I see you would like some sort of vsz hdf5 saved file. I can see that might work. However, I can't see a nice way of storing the document tree in HDF5 file, unless it's encoded in XML. I'll read up a bit more about HDF5.
Why not keep the document tree format the same python text that it is now and just store it as a string in the HDF5 file? The only objects in the save file that are large enough to benefit from HDF5 storage are the datasets themselves, and adding a new "create Veusz dataset from a dataset in this HDF5 file" command is easy enough. So the hypothetical
.v5z binary format might be an HDF5 structure with /veusz -- the .vsz stored as a string /datasets/* -- actual storage for the datasets Thoughts? -- BKS _______________________________________________ Veusz-discuss mailing list Veusz-discuss@gna.org https://mail.gna.org/listinfo/veusz-discuss
