With the sheer amount of programs I have, combined with how often I make new ones to mess up the list, I voted for the first option.

I was just reminded about the ability to make custom icons for MOS and DCS instead of the default Axe logo.  I've been thinking about it but I'm having a hard time thinking of a good format for this that is easy to use and unambiguous.  I challenge anyone to think of a good format for this.  It should be:

1. Near or at the top of the header.  Must come before program and data.
2. Parsed as a comment or something that is ignored when its not needed.
3. Similar to existing commands/conventions.
4. Relatively simple to implement.
5. No new tokens.
6. Not simply a commented out sprite since many people comment sprites at the start of their code.

Ya, I like Builder's idea. Just have it detect the "[" or what ever in the first line after the title (with or without the description). The only other idea I had was to have it on the next line with a ".[" signifying it.

if the description just happens to be an open bracket followed by 16 characters of hex followed by a closing bracket and nothing else then i guess they are out of luck

I think that you should extend headers more, actually.  Perhaps you could use psuedo-xml, which couldn't possibly be mistaken for commented out code, and could be more extendable.  I was thinking:
.PRGMNAME
.<SPRITE>HEX</SPRITE>
.<TARGET>APP/MOS/DCS6/ION/NOSTUB</TARGET>Of course, only PRGMNAME would be required.  Sprite would default to the axe one, and target would override the settings if present.

Oooor.

Code: [Select]

.PRGMNAME SPRITE TARGET DESCRIPTION
You could recognize each space before DESCRIPTION as something else.

The problem with that is that in Ion/Mirage, this is supposed to be the file description. Example: .ROL3 The Reign Of Legends 3 would show The Reign Of Legends 3 in MirageOS. Maybe we should use some sort of XML-style header, as Sir suggested. I like the icon idea personally. I think the default Axe icon should be used by default when not using any, though.

Also I don't think target is needed?  Since the target is defined in axe, not in the program.

It would actually be better if specified in the program imo.