Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!pasteur!ames!lll-winken!uunet!cadnetix.COM!cadnetix!eriks
From: eriks@cadnetix.COM (Eriks A. Ziemelis)
Newsgroups: comp.lang.c
Subject: Re: Iconitis
Message-ID: <7392@cadnetix.COM>
Date: 10 Apr 89 17:39:06 GMT
References: <1930@dataio.Data-IO.COM> <11555@lanl.gov> <17376@cisunx.UUCP> <8160@chinet.chi.il.us>
Sender: news@cadnetix.COM
Reply-To: eriks@cadnetix.COM (Eriks A. Ziemelis)
Organization: Cadnetix Corp.,  Boulder, CO
Lines: 32

In article <17376@cisunx.UUCP> jcbst3@unix.cis.pittsburgh.edu (James C. Benz) writes:
>In article <11555@lanl.gov> jlg@lanl.gov (Jim Giles) writes:
>>My major objection with icons is that often I know very well what I want
>>to do, but I can't do it without walking down some menu...  The
>>icon interface simply slows down experienced users.

And at times, icons slow down or prevent the novice user from becoming
an experienced user.

In a previous job, I did some support of a CAE/CAD system that uses
pull-down menus, icons, pop-ups, etc. I found that many users got so
used to working with these various non-keyboard interfaces that they
never progressed past them: they did not know of the other commands
available to them.  They would rarely read any of the reference manuals;
their sole source of information, in most cases, were the tutorial 
manuals they had used which usually focused on the non-keyboard methods.

They could perform the simple tasks that were programmed
into the icons and menus but would be lost when something "unexpected" would
happen or had to do something more complex that could not be performed
solely using icons etc.


Eriks A. Ziemelis


Internet:  eriks@cadnetix.com
UUCP:  ...!{uunet,boulder}!cadnetix!eriks
U.S. Snail: Daisy/Cadnetix Corp.
	    5775 Flatiron Pkwy
	    Boulder, CO 80301
Baby Bell: (303) 444-8075 X336