From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,8dffd960b2d9594e X-Google-Attributes: gid103376,public From: Richter@Informatik.Uni-Muenchen.de (Valentin Richter) Subject: Re: Decent ADA compiler on a Mac Date: 1995/04/02 Message-ID: #1/1 X-Deja-AN: 100721933 references: <3kb9rs$622@goanna.cs.rmit.edu.au> <3khii0$cgi@gnat.cs.nyu.edu> organization: Ludwig-Maximilians-Universitaet, Munich, Germany newsgroups: comp.lang.ada Date: 1995-04-02T00:00:00+00:00 List-Id: In article , vladimir@speedy.intrepid.com (Vladimir Vukicevic) wrote: > This is (IMHO) one major shortcoming of the MacOS interface. If you > want to do something fast, there's no way to do it. If you want to get > into the "Foo:Blah:Bar:Quux:Fap:Blat" folder, you have to click-click- > click-click through all those folders, instead of simply typing "cd > Foo:Blah:...". Point granted. But to be fair one has to take into account all the time wasted when he or she typed something wrong -- and not only successful command line commands. Then on average I doubt that a command line interface is really faster. Besides I strongly side with the fundamental design principle of a GUI: If some object is already know to the system then you don't have to type in its path and name to specify it for some action, but you only need to point at it. To effectively support this principle we need some standard GUI interface elements to quickly locate a needle (objects) in a haystack. These concepts will also overcome the natural limit of a command line being that one has to know the exact name of every object he wants to use. ----- Valentin Richter richter@informatik.uni-muenchen.de A statistician is someone who drowns in a creek whose average depth is three feet. anon (at least to me)