This suggestion accidentally got brought up in irc and seen as noone else is around I thought it might be a good idea to discuss.
The idea is to rename settings into groups (i.e "theme.wps" or "remote.theme.wps"). Pros: - it would mean settings_list.c would get some much needed love (i.e organise related settings into groups). settings_list.c has almost no ordering requirements[1] so this isn't dangerous - It would mean config files are easier to manage (users could choose to only save theme. settings or general. or recording. instead of only having the option of the 3 current flagged groups), it also means finding settings in the .cfg is easier - Hopefully would make the setting names consistent - It could allow for some interesting plugins which wouldn't replace the menu, but complement them. - could lead to out-of-menu options Cons: - needs a plugin/viewer to convert old .cfg's to new ones. - a fair amount of work for no "real" benefit - could lead to out-of-menu options Another way this could be done is if a dummy grouping option is added into settings_list for each group (it might get dumping into the .cfg as [group name] so the current names arent changed). Thoughts? Jonathan [1] - the only order in settings_list.c is the settings which are loaded into nvram(.bin). So the order only matters if a new one is added, which is almost never.
