Originally posted by lfroen
lionel77: including option is escape from responsibility. You must be thinking "more options => better", but this is wrong all over. You must have clear model of user expectation from GUI before you designing it.
I was suggesting to include an option because personally I would hate for status messages to vanish after some delay and I was expecting some other users to feel the same way. I would be more than happy to have no option and keep the status msgs around the way it currently works.
You gotta be kiddin' when you bring up Microsoft as an examble for good GUI designs. They have some techies putting together the interface who don't know shit about human factors ("click start to shutdown", anyone?) and then they have some graphic artists who slap some mediocre icons on top of that. If you want to see some examples for good interface design, have a look at Apple's products. In contrast to MS, these guys actually spend a lot of money and resources on trying to find the most ergonomic designs.
But in terms of Outlook's popularity I have to agree with you: it's like with Internet Explorer -- these products dominate their competition because of superior design and technology and not because of users' laziness or lack of awareness of better alternatives...

Originally posted by lfroen
That's exactly my point. "Familiar" is key here. Means "like other programs they already know"
The problem is that you can't compare amule to MS Word or any other "regular" GUI-app. The main difference is that amule primarily runs in the background and even then stuff is actually happening that produces status msgs. In contrast, a "regular" GUI-app just idles when the user switches to another app, so status msgs only appear when the user is working with the app and therefore able to see the message immediately. So with "regular" GUI apps there is no problem (actually it's very preferable) if status msgs vanish after a short delay, but with a program like amule that a user only checks every 30min or so it imho doesn't make sense to have the msgs go away after a short period of time. Then you could just abolish the status msgs altogether and categorically force the user to log at the log. It's sort of like an email client that only displays new messages for a short period of time.