08-01-2017, 01:33 PM
(This post was last modified: 08-01-2017, 01:33 PM by tomaszkax86.)
For binary files, file name extensions are not necessary because they often have headers with magic numbers that identify them easily.
Most often the case with images, audio and video files, executables and so many others. But with text files there's no easy way to tell right away what the format and meaning are, so the extension can tell you exactly what a given text file is meant to be. .txt are simple text, .ini files are Windows configuration files, .inf are installer files, and every computer language has its own set of extensions to identify source code. This is why it would be better, in my opinion, if Colobot used special extensions for at least some files.
I think we can at least agree that CBot source code could use .cbot extension. The language definitely deserves some recognition and by reserving unofficially this file name extension we can give it some.
Once we get to fixing this mess with model formats, we could decide if we want to introduce new file name extension for new formats or not. I checked that .cbm and .cmod are already used for some files, but .cbmod and .cbmf are available.
Scene and SatCom files could also use their own extensions to clarify what they mean. We could just use .scene and .satcom since they only really have a meaning within Colobot so it wouldn't cause real problems. We could also use 4-letter extensions and they could start with .cb, like .cbsf for scene files and .cbsc for SatCom files. Both are currently not in use.
Most often the case with images, audio and video files, executables and so many others. But with text files there's no easy way to tell right away what the format and meaning are, so the extension can tell you exactly what a given text file is meant to be. .txt are simple text, .ini files are Windows configuration files, .inf are installer files, and every computer language has its own set of extensions to identify source code. This is why it would be better, in my opinion, if Colobot used special extensions for at least some files.
I think we can at least agree that CBot source code could use .cbot extension. The language definitely deserves some recognition and by reserving unofficially this file name extension we can give it some.
Once we get to fixing this mess with model formats, we could decide if we want to introduce new file name extension for new formats or not. I checked that .cbm and .cmod are already used for some files, but .cbmod and .cbmf are available.
Scene and SatCom files could also use their own extensions to clarify what they mean. We could just use .scene and .satcom since they only really have a meaning within Colobot so it wouldn't cause real problems. We could also use 4-letter extensions and they could start with .cb, like .cbsf for scene files and .cbsc for SatCom files. Both are currently not in use.
"After three days without programming, life becomes meaningless."
~The Tao of Programming
~The Tao of Programming