I saw we keep both: a generic ocnfiguration screen that can control all the voodoo magic, and a user friendly configuration screen for the commonly used options. like firefox options screen and about:config. Martey Dodoo wrote: > Hi guys, > > Marco and I have been talking about redesigning Gregarius' > configuration pages to make them more user-friendly and less crufty. > We have about 40 configuration options now, and the page is only going > to get more difficult for users to edit as it grows. As it is now, I > am forced to use my browser's Find feature in order to find the > options I am looking for when I need to change something. > > While a few of the options might be able to disappear without the > majority of users caring, I think that the majority of the options > will stay visible. I see two options for their better organization: > > - use the pre-existing categories (i.e. rss.output) to organize the > configuration page into sub-pages that appear as tabs on each page, > like the current WordPress administration panel (see the image at > http://feedtree.net/blog/2006/01/30/wordpress-plugin-available/ for an > example). > > - make custom category pages. The simplest way to do this would > include hard-coding individual options into the configuration pages. > This would require these pages to be edited each time a new > configuration option was added, though, but would offer more > flexibility in the positioning of configuration options on the page. > > Any thoughts on which method would be best?