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: <1394@umd5>
Date: Fri, 19-Dec-86 09:12:50 EST
Article-I.D.: umd5.1394
Posted: Fri Dec 19 09:12:50 1986
Date-Received: Sat, 20-Dec-86 00:16:50 EST
References: <1111@spice.cs.cmu.edu>
Sender: uucp@umd5
Reply-To: louie@sayshell.umd.edu (Louis A. Mamakos)
Organization: University of Maryland, College Park
Lines: 14

I want to agree that having a file per directory to store the icon information
rather than a .info file for each file is a big win.  And the best thing of all
is that you can make this COMPLETELY TRANSPARENT TO WELL WRITTEN APPLICATIONS.
The GetDiskObject() and related library calls to manipulate icons from 
application programs take the name of the file that the icon refers to, NOT
the actual name of the icon (that is, "foo" rather than "foo.info").

All that is needed is the appropriate hacks to the Workbench to display and
manage this per directory file, and perhaps an "icon mover" program to copy
them.  I guess you could use the icon editor to perform this function.

Note that the internal stucture of the .info files has NEVER been documented;
only the memory resident stucture that {Get,Put}DiskObject() manipulates.  
Programs that hack with the .info files directly are bogus.