This is a page where arguments for and against each possible NoDo topic can be summarized (please add links to mailing lists and IRC discussions when they happen. Also you MUST add your signature to the edits or they will be removed. Remember to keep arguments POLITE and objective.

---

Customizable menus

Overview

This possible NoDo is about allowing the user to have full control over which menu items appear in the rockbox menus (full menu structure and tree/WPS/etc context menus), and also where they should be displayed

Pro's

• More flexibility for the user
  • The whole point of rockbox is because users want choice, yet me force a horrible menu structure one them? -- JonathanGordon - 2010-03-31
• Trivial to implement
  • just about every menu item is accessable with a "unique id/path" already so it could be very simply built from a text file by walking the current menu and moving items around in RAM. -- JonathanGordon - 2010-03-31

Con's

• support issues (it would be theoretically possible to make screens impossible to access, including the WPS).
  • IMHO this should not be taken into consideration because we can always tell the users to reset settings before giving them help. Also we could make it required that certain items must be in the menu structure (Although I'm against that) -- JonathanGordon - 2010-03-31
• Bin/RAM delta

---

FULL Customizable keymaps

Overview

This possible NoDo is about allowing the user to have full control over which button does what in each screen.

Pro's

• More flexibility for the user
• Trivial to implement

Con's

• support issues!
  • This will be a nightmare to support and should no question be a NoDo -- JonathanGordon - 2010-03-31
• Bin/RAM delta

---

PARTIAL Customizable keymaps

Overview

Some targets have "spare" buttons, or buttons mapped not-so-logically. Allowing these buttons to be user configurable on a narrow set of functions is what this NoDo is about.

Pro's

• More flexibility for the user
  • I dont use the pitchscreen on the WPS but I do use the id3 info, why should I be forced to alocate a button to the function I dont use? -- JonathanGordon - 2010-03-31
• Use all buttons on the target

Con's

• support issues
• Bin/RAM delta

---

Add support for non standard tag formats (specifically APEv2)

Overview

A few formats have multiple competing tag formats. MP3 is most obvious with ID3v1 and ID3v2. Additionally MP3 can have APEv2 tags (popularized by hydrogenaudio in the early to mid 2000s), Vorbis can have ID3v2 tags (generally due to people not properly understanding Ogg), etc.

Pro's

• Support is 'free' on SWCODEC (we already have an APEv2 parser in rockbox)
• Better compatibility with various tagging software

Con's

• APEv2 tags must be checked for after ID3v1 tags, which means seeking a further 96 bytes into the file if the file contains no ID3 tags
• More inelegant to support 3 tag formats for MP3 than to support 2
• mp3 files with APEv2 tags in them are technically corrupt.