3 ms·
An alternative: have two separate interfaces, one for everyday settings (= simple), and another for "powersettings" (= configurable). A good example are the web
by tomp 14y ago
An alternative: have two separate interfaces, one for everyday settings (= simple), and another for "powersettings" (= configurable). A good example are the web browsers: some have a settings dialogue, where settings are presented logically, and they tend to simplify these dialogues, and then you have the about:config or about:flags page, where you can access a bunch of other settings as well.
- DanI-S 14y agoThis makes sense when developer time is not an issue, but if it is, favour simplicity.
- joe_the_user 14y agoI think you're missing what's good about what the gp is advocating. Even as a power user, I quite likely only want to change a few things "under the hood" and otherwise I appreciate a clean design. Further, the more programmers design an interface "for those other people", the more likely they are to make it purely brain dead. So you find up with two lousy interfaces instead of one well designed one (not just two interfaces take time but because you've started with the wrong attitude).