On Thu, Jun 07, 2007 at 08:42:41PM +0200, Peter D'Hoye wrote: > > As I didn't attend DevCon I'm not aware of the discussion > > you guys had there, but I see a lot of discussion everywhere > > regarding keyboard mappings in different parts of Rockbox. > > IMHO it would be fairly easy to abstract the buttons layer > > and use only "actions" everywhere in the code (actually this > > is already done), but then, it would be easy to make a > > setting screen in which the user can assign keys, key > > combinations or long key presses to these actions. So > > everyone can choose, no matter the target, the keys best fit > > what they usually do. > > This has already been brought up many times, and always rejected for the > simple reason that this will be a support nightmare...
Well, there are many other support nightmares in Rockbox, we have many questions, which pop up from time to tiime on the list, and people ask things that have been very clearly documented in the manual. I think that we should not reject a feature which would be so useful, because some people cannot use it properly. If Rockbox would read text-based keymaps, which should be created manually using a tet editor, then we would have much less trouble in supporting. This would also be much easier than trying to create a simple UI for adjusting keymap. A file could look like this: [default] LONG REC = recording_screen VERY_LONG REC = run "/.rockbox/plugins/rockblox.rock" REC+MENU = toggle "voice menus" REC+UP = set "sleep timer" 900 # (15 minutes) [WPS] REC = wps_editor [Files] REC = insert_current_to_playlist [Database] REC = insert_current_to_playlist [Menu] REC = insert_current_to_playlist # ERROR: Nothing is selected, when in menu # ANd so on LONG and VERY_LONG should be configurable (from 0.5+ seconds) I guess that I would not be the only one who would benefit from this. I really feel that rejecting features bacause they are too difficult to understand by some users is not a good way to go in FOSS. Configurability is one of the reasons why we don't use the stock firmwares. I don't mean that this would be easy to implement, and certainly I'm not able to code that bit, but it doesn't seem to be impossible especially if we use text-based keymaps. -- Tapio
