PyPlanning is currently using a .xml extension by default when saving/openning a planning file. This is not very convenient, as you can't open a planning file directly from the file browser and you need to open PyPlanning first. As XML is widely used, telling the operating system to open .xml files with PyPlanning doesn't seems like the right solution, so a dedicated file extension seems like a better option.
PyPlanning can already save and open file with a different extension than xml, so this would only require:
- choosing a dedicated extension
- use the new extension by default in the save as/open window (keep the xml format available for backward compatibility)
- adding PyPlanning as the new default app for the new file extension during installation.
Here are a couple suggestion for the custom extension:
- .pplan
- .pyplan
- .ppl (though already used by other niche applications)
PyPlanning is currently using a .xml extension by default when saving/openning a planning file. This is not very convenient, as you can't open a planning file directly from the file browser and you need to open PyPlanning first. As XML is widely used, telling the operating system to open .xml files with PyPlanning doesn't seems like the right solution, so a dedicated file extension seems like a better option.
PyPlanning can already save and open file with a different extension than xml, so this would only require:
Here are a couple suggestion for the custom extension: