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

---