Roger wrote:
As long as there is still a rc/config file in place for users whom want to editthe config file by hand using VIM. Personally, I'd rather use VIM rather then a GUI interface. Using VIM, editingconfig options much faster. GUI can be much easier or the lackadaisicalmethod.
Of course there is still an rc file; the GUI could even be modified to nicely comment it (though it doesn't right now, to keep the code size down). But imagine you're a new user and not really all that tech-savvy. Say staring at white webpage backgrounds all day makes your eyes hurt. Would you rather a) spend hours looking through a long configuration file looking for an option to somehow darken them; or b) click a button that says "Darken white backgrounds"? If you choose option a) and you're persistent -- remember you're still pretending to be a non-savvy, first-time Dillo user -- you might discover there are two separate settings for this: - allow_white_bg sets whether white backgrounds are allowed, and - bg_color takes the hexadecimal(!) code for your desired background color. (Remember as a non-savvy, first-time user, you don't know hexadecimal.) On the other hand, if you choose option b), you probably saw it here: http://dillo-win32.sourceforge.net/dillo/screenshots.php?closeup=Win95-09.pn... That's much simpler, wouldn't you say? As a side note, "Allow white backgrounds" is a bad option name from a user's perspective: since most users automatically assume white backgrounds are the norm, an "Allow white backgrounds" option forces them to think in negatives. "Darken white backgrounds" is better, because it recognizes this implied norm. The word "darken" also states a clear action, unlike -- for example -- "disallow." A user should never have to stop and think, "What does 'Disallow white backgrounds' mean?" if there's a more obvious way to word it. (And yes, I know mainline darkens backgrounds by default, but it makes a convenient illustration. And yes, if you're wondering, little things like this DO make a surprisingly huge difference in usability.) Cheers, ~Benjamin