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

List:       kde-look
Subject:    Re: OK/yes
From:       Derek <fountai () hursley ! ibm ! com>
Date:       1999-09-17 7:43:37
[Download RAW message or body]

> If at all possible use one of the following options (in order of preferability)
> 
> Quit
> Save
> Print
> Overwrite
> Change
> Stop
> etc.
> 
> Cancel
> OK
> 
> Yes
> No
> 
> Why?
> Well with the single word options you would know immidiately what the question
> would be.

Verbs are great in user interface buttons. The user knows what will
happen when they click them. First choice wherever possible. Agreed.

> The rest is historic, OK cancel is used from the first Xerox system upto today..
> Yes/No forces the user to read the text, not what we want.

Wahh???? Splutter!? You are suggesting we define user interface
guidelines which state that we don't necessarily want the user to read
the text? This is madness. We're trying to define a user interface here,
not a guessing game.

> Supply enought buttons to create a simple question:
> 
> File exists:
> [Overwrite] [cancel]

Great. Verbs. 

> Save before closing?
> [Save] [Save as] [don't save] [Cancel]

Great. More verbs.

> Print file?
> [Ok]  [Cancel]

Why not Yes/No? 

> Read error:
> [retry] [ignore] [cancel]

Crap message, buttons could be better:

  There was an error reading from the disk.
     [Retry] [Continue anyway] [Cancel]

> Shure to remove dir X and everything it contains?
> [OK] [Cancel]

  Deleting directory XXX will also delete everything it contains.
              Are you sure you want to do this?
                         [Yes] [No]

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