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

List:       kde-usability
Subject:    Re: simpler UI for konqy
From:       Aaron Seigo <aseigo () kde ! org>
Date:       2004-01-06 15:44:15
Message-ID: 200401060844.15984.aseigo () kde ! org
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On January 06, 2004 7:54, Rui Malheiro wrote:
> Opera uses a single, alteranting stop/reload button. First time I used it,
> I liked it a lot and didn't find it a bit confusing. I also think that
> having a single button can be used as a hint to show when the page has
> finished loading.

Q1. are reload and stop the same action?
A1. no. the principle of "one element, one action" is therefore invoked.

Q2. do we already have means to show when a page is finished loading?
A2. yes, the stop button disables and the throbber stops.

safari also does the toggle between stop/reload thing, but i really think 
that's a mistake. each UI element should have one and only one purpose. the 
book "The Humane Interface" covers the reasons for this quite thoroughly 
(including real-life case studies) but the basic principle is that if a 
button's action changes on you then the user must stop and consider the 
current context (the icon on the button, the state of the application, etc) 
which slows the user down, decreases confidence levels and is just asking for 
a mistake to be made (people aren't great at managing "modes" as contexts).

the quest for simplicity should not become an excuse for poor usability.

- -- 
Aaron J. Seigo
while (!horse()); cart();
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQE/+tfP1rcusafx20MRAgSSAJ9uwhy239m081md5aRPsDYlCAxbPgCfYeHt
zVQcwzjAjDxS4rBlJHgwynQ=
=c5oU
-----END PGP SIGNATURE-----
_______________________________________________
kde-usability mailing list
kde-usability@mail.kde.org
https://mail.kde.org/mailman/listinfo/kde-usability

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