Bug 1876 - [Wizard] - Wizard errors are too obtrusive (1GCTEMX)
Summary: [Wizard] - Wizard errors are too obtrusive (1GCTEMX)
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: All Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Kevin Haaland CLA
QA Contact:
URL:
Whiteboard:
Keywords: investigate, usability
Depends on:
Blocks:
 
Reported: 2001-10-10 22:21 EDT by Nick Edgar CLA
Modified: 2002-08-30 10:17 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Edgar CLA 2001-10-10 22:21:20 EDT
Wizard errors are too obtrusive, and often complain at inappropriate times.

For example, as I'm entering a package name, it complains every time I type '.',
since a package name can't end in '.'.
As another example, create new project, and enter "New Project".  It complains as soon as I hit space

But I shouldn't care about this until I've finished entering my input.
That is, it's checking at a finer grain than my unit of input, which is not helpful.

According to Jef Raskin's book "The Humane Interface", this would qualify our UI as inhumane.

The placement of the errors causes me to be distracted from my locus of attention.
It also hides useful information (the wizard page description).
It would be better to place them nearer to the OK or Next button, since any error message
is useful at the time I go to try to use them and find them disabled.

Ideally, if I enter valid input, I should never have to see an error message, even if I enter something
invalid along the way.

To compare, spelling and grammar checking in Word aren't activated until a meaningful unit of input
has been entered (a word for spelling, a sentence for grammar checking).
Also, it clears the error as soon as the unit of input is edited again, and does not check again until done
editing the unit of input.

I recommend:
	- enabling or disabling the buttons right away, to avoid them being pressed with invalid input
		- they are far enough away from the user's locus of attention that this shouldn't be distracting
	- have a delay of 0.5 secs before showing the error message
	- show it near the buttons, not near the top, and not hiding useful info
	- don't use high contrast for the error

VA/Java actually does a pretty decent job of this, even without any delays.

NOTES:
Comment 1 DJ Houghton CLA 2001-10-24 06:48:49 EDT
PRODUCT VERSION:
0.048

Comment 2 Kevin Haaland CLA 2002-01-21 19:42:26 EST
There are no plans to change the current behavior. 
Comment 3 Randy Giffen CLA 2002-08-06 15:11:24 EDT
Reopened for investigation.
Comment 4 Kevin Haaland CLA 2002-08-30 10:17:44 EDT
This isn't going to change.