[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-look
Subject: Re: OK/yes
From: Boris Povazay <boris () jouh ! at>
Date: 1999-09-17 18:09:39
[Download RAW message or body]
Thomas Zander wrote:
> Therefor the dialog should be simple to understand without reading a lot of
> text, preferable reading only the buttons. The latter is not impossible if all
> the questions for kde are in like manner so if someone understands the common
> line in the requesters he/she could predict the question asked.
The text should be read, but complicated questions are not easy to answer, when the
user is in a hurry. So thatīs why the buttons should represent a SPECIFIC answer to
the question. (Yes/No is obviously NON SPECIFIC !)
> Print file?
> [Ok] [Cancel]
Why that?
Shouldīnt it be [Print] and [Cancel] ?
Clicking is "the action", so "the user prints" when "s/he clicks"
> Read error:
> [retry] [ignore] [cancel]
Good!
> Shure to remove dir X and everything it contains?
> [OK] [Cancel]
[Remove] [Cancel]
could also be [Remove file]
This [OK] does give you no information about the question. "OK" is definitly
positve, but a rather negative action is going to happen. So this is completely
misleading!
I donīt want to say that users are incapable to understand what they read, but
again - when things have to be done quickly, decisions are not done by brainwork,
but by intuition. And so intuition is what has to be the guide for button-design!
ciao BoP
--
http://kde.jouh.at - bp@jouh.at
Boris Povazay
[Attachment #3 (text/html)]
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Thomas Zander wrote:
<blockquote TYPE=CITE>Therefor the dialog should be simple to understand
without reading a lot of
<br>text, preferable reading only the buttons. The latter is not impossible
if all
<br>the questions for kde are in like manner so if someone understands
the common
<br>line in the requesters he/she could predict the question asked.</blockquote>
The text should be read, but complicated questions are not easy to answer,
when the user is in a hurry. So that´s why the buttons should represent
a SPECIFIC answer to the question. (Yes/No is obviously NON SPECIFIC !)
<blockquote TYPE=CITE>Print file?
<br>[Ok] [Cancel]</blockquote>
Why that?
<br>Should´nt it be [Print] and [Cancel] ?
<br>Clicking is "the action", so "the user prints" when "s/he clicks"
<blockquote TYPE=CITE>Read error:
<br>[retry] [ignore] [cancel]</blockquote>
Good!
<blockquote TYPE=CITE>Shure to remove dir X and everything it contains?
<br>[OK] [Cancel]</blockquote>
[Remove] [Cancel]
<br>could also be [Remove file]
<br>This [OK] does give you no information about the question. "OK" is
definitly positve, but a rather negative action is going to happen. So
this is completely misleading!
<br>I don´t want to say that users are incapable to understand what
they read, but again - when things have to be done quickly, decisions are
not done by brainwork, but by intuition. And so intuition is what has to
be the guide for button-design!
<p>ciao BoP
<pre>--
<A HREF="http://kde.jouh.at">http://kde.jouh.at</A> - bp@jouh.at
Boris Povazay</pre>
</html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic