Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!lll-crg!mordor!sri-spam!ames!ucla-cs!sdcrdcf!trwrb!cadovax!keithd From: keithd@cadovax.UUCP (Keith Doyle) Newsgroups: comp.sys.amiga Subject: Re: Statement Message-ID: <1258@cadovax.UUCP> Date: Fri, 12-Dec-86 20:01:03 EST Article-I.D.: cadovax.1258 Posted: Fri Dec 12 20:01:03 1986 Date-Received: Mon, 15-Dec-86 21:43:40 EST References: <8612021654.AA00831@cory.Berkeley.EDU> <2762@gitpyr.gatech.EDU> <1087@cbmvax.cbmvax.cbm.UUCP> Reply-To: keithd@cadovax.UUCP (Keith Doyle) Organization: Contel Business Systems, Torrance, CA Lines: 25 In article <1087@cbmvax.cbmvax.cbm.UUCP> carolyn@cbmvax.UUCP (Carolyn Scheppner) writes: >>> IF Workbench ICONS were stored in a single file per directory rather >>>than in a lot of little files, I would use it (the workbench). >>> With all due respect, if you don't change it soon, I will huck your >>>Workbench and write my own. >>> -Matt > Personally, I like to be able to manipulate individual .info files >and program/program.info pairs from CLI. > >Carolyn Scheppner -- CBM >>Amiga Technical Support<< Yes, but look at what you just said. It's convenient from the CLI point of view, but not the WORKBENCH point of view (too slow). And why are the .info files there? Not for the CLI but for the Workbench. I like being able to manipulate the files seperately too, (the Apple resource/data fork mess is a pain in the ***), BUT one of the main reasons I don't use the Workbench, is it's poor performance. When I'm looking over the shoulders of a freind on a MAC, the icon interface is snappy enough to be useful. I believe the performance of an icon based interface to be in direct correlation to it's usefulness. Keith Doyle # {ucbvax,ihnp4,decvax}!trwrb!cadovax!keithd # cadovax!keithd@ucla-locus.arpa