Here's how it currently looks (very early in development):
What I want to know is a simple question: what would be the best extension for the NES colors palette (containing RGB representations of each of all available colors) and the PPU palette containing the 32 colors currently in use? I want to let the user use whichever palette he wants and not be stuck with one or a list of palettes I provide, but then there's the problem of calling everything palettes and the files all being .pal, as they are obviously not compatible.
YY-chr differentiates these as .pal and .dat. But dat is too generic to me.
NST only has pal and I think you can't choose another color set.
Since the user will handle PPU palettes a lot, I thought maybe keep those as palettes/.pal and choose another name for the NES colors values. Maybe .yiq? .rgb? Would it be called "NES Colors" or something?
Then again, we download palettes and they are all .pal. There doesn't seem to be a consensus.
Suggestions are welcome! Thanks.
For the 4/16/32 bytes colour index palette data used in NES games, I think there are a bunch of common ones. .bin, .pal, .dat, etc.
All I'd suggest for the latter is don't force the user to use only one of those. Let them open and save files with an extension of their choice.
For sorting out the difference between an RGB triple .pal or an NES index .pal, I think that's more of a problem for the user organizing their files, not something that a utility needs to solve. If they've thrown a bunch of these into the same folder and don't know which is which that's an issue they created for themself. ;P
Still open for more people to share their opinion though. I'm inclined to have a suggested standard that differentiates them.
Code: Select all
Palette -> Import bg pal = rename: Import native palette (BG) -> Export bg pal = rename: Export native palette (BG) -> Import spr pal = rename: Import native palette (Sprite) -> Export spr pal = rename: Export native palette (Sprite)
You can also replace the word "native" in the above menus with "NES" if you want. I chose the word "native" to imply native-to-the-NES. "Import/export palette indices (BG/Sprite)" would also be OK.
You can pick whatever file extensions you want for these, but I would recommend .bin. .pal will just confuse people, making them think that they're RGB palettes for emulators. To ensure someone can't load one of those, you should check the file contents to see if they're != 16 bytes (or != 32 bytes), and if so, tell the user that they're trying to load the wrong kind of palette file (see below).
Importing/exporting raw RGB palettes affect the on-screen colour in the editor itself, and thus should be under a COMPLETELY different menu section to differentiate the purpose. This makes the difference clear to the user. For example:
Code: Select all
Edit -> Preferences -> Editor palette -> Import palette (RGB) -> Export palette (RGB)
Thank you for making an editor! Tools like this will greatly help people. We need more of this. :-)
"Please turn to page 5 of the manual and enter the fifth word line 3"koitsu wrote:We live in a time where most people don't read README.txt that comes with software etc. and that's their own fault -- do not cater to that!