Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mimsy!cvl!umd5!louie
From: louie@sayshell.umd.edu (Louis A. Mamakos)
Newsgroups: comp.sys.amiga
Subject: Re: workbench
Message-ID: <1415@umd5>
Date: Tue, 13-Jan-87 08:33:44 EST
Article-I.D.: umd5.1415
Posted: Tue Jan 13 08:33:44 1987
Date-Received: Tue, 13-Jan-87 20:41:58 EST
References: <1111@spice.cs.cmu.edu> <1394@umd5> <5394@ukma.ms.uky.csnet> <1986Dec24.191136.2866@utcs.uucp> <1318@cadovax.UUCP>
Sender: nobody@umd5
Reply-To: louie@sayshell.umd.edu (Louis A. Mamakos)
Organization: University of Maryland, College Park
Lines: 24

In article <1318@cadovax.UUCP> keithd@cadovax.UUCP (Keith Doyle) writes:
>In article <1986Dec24.191136.2866@utcs.uucp> wagner@utcs.UUCP (Michael Wagner) writes:
>>>In article <1394@umd5> louie@sayshell.umd.edu (Louis A. Mamakos) writes:
>>>Why not just store the icon information in the original file?  Having two
>>>files is awfully messy.
>>
>>Ah, but putting it in the same file is also messy.  I think, in general,
>>one wants the icon (and other) information in the .info file to persist
>>even when an executable is replaced by the compiler, or a table is changed
>>by an editor.  Stupid programs should be allowed to ignore .info files and
>>not break things.  That's what's wrong with FILENOTE...no programs preserve
>>it, because none know it's there.

First of all, I didn't make the statement 'Why not store the icon information
in the original file?', nor would I ever.  It is a stupid idea.  

In the second place, you CAN INDEED STORE ALL THE ICONS IN A SINGLE FILE WITHOUT
CHANGING ANY WELL WRITTEN PROGRAMS.  Period.  You just have to hack 
icon.library to look in a different place, and create/update icons differently.

The solution exists.  The problem (can be) is solved.

Louis A. Mamakos  WA3YMH    Internet: louie@TRANTOR.UMD.EDU
University of Maryland, Computer Science Center - Systems Programming