What I'm thinking of doing is creating my own filetype extensions not using the standard windows 3 character file extension format, (if it still exists?)
filename.header (contains file header info)
filename.original (original file locked)
filename.edited (original file edited)
filename.txt (import standard ascii text file)
In actual fact all filetypes will be ascii, readable in any text editor.
So for example, using the Xojo FileTypes filter, I can code it so the user can only open/save *.edited files. Which will also be within a strict folder structure under my main application. The only filetypes that can be imported from anywhere will be *.txt files, which can then only be saved and auto renamed *.edited under the edited files folder.
- Header Data
- Original Files
- Edited Files
- App Preferences
I've tested the file extensions by setting up a FileType with various test extensions and it appears to work fine. Also, this question is a pre-cursor to questions I'll be asking in the future regarding File IO operations and the Special Folder.
Anyway, apart from the strict folder structure, my main question here is are there any potential issues using non-standard extensions that I'm not aware of?