Xref: utzoo comp.sys.ibm.pc:40616 comp.sys.mac:44990
Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!zephyr.ens.tek.com!tektronix!percy!parsely!bucket!leonard
From: leonard@bucket.UUCP (Leonard Erickson)
Newsgroups: comp.sys.ibm.pc,comp.sys.mac
Subject: Re: User interface(was Re: Xerox sues Apple!!!)
Message-ID: <1830@bucket.UUCP>
Date: 21 Dec 89 10:12:47 GMT
References: <6767@tank.uchicago.edu> <1989Dec17.112127.27333@me.toronto.edu> <JACOBS.89Dec18135051@cmos.cs.utah.edu>
Organization: Rick's Home-Grown UNIX; Portland, OR.
Lines: 25


Here are my two favorite examples of why it is at least *sometimes*
a good idea to have a command line interface available.

1. del *.bak
	vs
   {long sequence of click and drags}

2. copy \subdir\filename.ext
	vs
   {the totally *non* intuitive sequence needed to move a file from
    a subdirectory to the root directory}

I make extensive use of utilities with a "point and shoot" interface,
so I know that command line isn't perfect. But on the other hand, there
are times when command line is a whole lot simpler.

BTW how come I can't drag the file onto the desktop, close the window
on the subdirectory, then grab the file from where I left it and drop
it into the window for the root directory? *That* would be intuitive!
-- 
Leonard Erickson		...!tektronix!reed!percival!bucket!leonard
CIS: [70465,203]
"I'm all in favor of keeping dangerous weapons out of the hands of fools.
Let's start with typewriters." -- Solomon Short