On Thu, Mar 27, 2008 at 08:57:54PM -0700, Lan Barnes wrote:
On Thu, March 27, 2008 4:43 pm, David Brown wrote:
On Thu, Mar 27, 2008 at 04:05:34PM -0700, Lan Barnes wrote:
I completely disagree. Successful progress should be silent. If
reassurance is necessary, a -v or -h (as in "print hash marks") can be
added.
It's fine that you disagree, but not very significant. A vast majority of
users want/need progress. User interface guidelines require it.
Whose interface guidelines, we ask.
All, as far as I know. It is pretty much a universal guideline, to the
point where I would argue that "Successful progress should be silent" is
just plain wrong, at least in the sense that everyone disagrees with it.
Gnome. Gives time limits for various types of feedbacks. Basically
requiring a progress indicator within 1 second of a user initiated action
that will take longer than 1 second.
<http://developer.gnome.org/projects/gup/hig/1.0/feedback.html>
Apple recommends providing feedback such as a progress bar. If an
application doesn't respond for 2 seconds, the OS will "beach-ball" the
cursor. A proper application shouldn't have this happen.
Cornell's UI Ergnomics guidelines:
<http://ergo.human.cornell.edu/ahtutorials/interface.html>
Microsoft:
<http://msdn2.microsoft.com/en-us/library/aa511486.aspx>
"Usability studies have shown that users are aware of response times of
over one second. Consequently, you should consider operations that take
two seconds or longer to complete to be lengthy and in need of some type
of progress feedback."
"During a lengthy operation, users need a general idea of what the
operation is doing. They also need to know:
- That a lengthy operation has started.
- That progress is being made and that the operation will eventually
complete (and therefore hasn't locked up).
- The approximate percentage of the operation that has been completed
(and therefore the percentage remaining).
- If they should cancel the operation if it isn't worth continuing to
wait.
- If they should continue to wait or do something else while the
operation completes."
David
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
