[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-usability
Subject:    Re: misuse/abuse of popup windows - a real-life example
From:       Allan Fields <kde () afields ! ca>
Date:       2004-09-01 7:56:50
Message-ID: 20040901075650.GC34157 () afields ! ca
[Download RAW message or body]

On Tue, Aug 31, 2004 at 09:41:34PM +0200, G?rard Delafond wrote:
>
> I never understood messages like "You cannot perform this operation - OK".
> What other choice do I have ? Why does it need a validation ?
> I am very happy if KDE project goes hunting such boxes.
>
> Gerard

Exactly.  There is no reason to display messages in this inefficient
manner, especially if the information is routine, of low urgency
or periodic in nature.

In this paradigm dialogs are being abused, because there is really
no need for user interaction, just notification.  Soon users could
become numb to all dialogs and just choose "OK" very quickly w/o
bothering to read the message.  Low-priority dialogs add noise
thus detracting from all message dialogs, it also makes the user
experience more bumpy.

Not so coincidentally, I've used the edu/games before in my
informal IRC chat as an example of some interfacing in need of help.
Some would argue that: "It's just a game", but I think consistency
in the games is still important in that it sets a bad presidence
for KDE programmers and new users to ignore usability issues and
detracts from the flow of game-play.

(Not that edutainment can be singled-out or picked on, it's a problem
in KDE even w/ konqueror for example.)

A better interface should exist or messages should be handled in a
more intelligent/ergonomic fashion: I proposed a solution a while
back which I've not yet had a chance to explore/implement.
If implemented poorly, it might mean that users are unaware of
messages which is why authors might often opt for dialogs, the user
will more than likely find it hard to not notice a new window.

It's also perhaps not a good idea to expect application developers 
to implement each their own scheme for specific program such as
using the status bar over another interface style.  Maybe this needs
to be thought through..

How can a user be made to notice a message/event that occurs
w/o the archetypical "OK Computer" dialog window?  Is there an
easy way to avoid the need for user interaction while maintaining
the ability to keep a user informed?

Instead of fighting w/ the established norm, perhaps dialogs should
just be handled more intelligently w/ a generalized (user configurable)
messaging API, which wraps the existing calls and provides control
over events, roughly the inverse of shortcut/gesture specification.

References to existing threads from the list:
http://lists.kde.org/?l=kde-usability&m=107319974715513&w=2
http://lists.kde.org/?l=kde-look&m=98294780630209&w=2


-- 
 Allan Fields, AFRSL - http://afields.ca
 2D4F 6806 D307 0889 6125  C31D F745 0D72 39B4 5541
_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic