Re: Resources (was: MS-DOS FST)

[jimwong@owlnet.rice.edu (Jim Wong)]

In article <1srcec$e2l@altitude.HIP.CAM.ORG> vandry@CAM.ORG (Phillip Vandry) writes:
>Furthermore, I believe the old system (*/Icons/) was much better. In that
>system, people who don't use the Finder (like me, because I hate it) can
>just omit the icon file while installing a program.
>

Wah.

>If a program launcher requires that many of the files it deals with contain
>additional information relevant to that program launcher in order to
>function acceptably, there must be something wrong with that program
>launcher. All the other program launchers work just beautifully without
>icons, application ascociations, etc... why should the Finder require
>special "extras". This goes for Finder.Data/Finder.Root files too: I know
>plenty of program launchers that do -not- depend on such files for
>optimal performance.
>

Most program launchers don't have to keep track of information like
icon placement for each directory.  Most program launchers also won't
associate documents to applications that were released after the launcher.
The Finder does both.


>BTW, the "ascociation" procedure is one to one. A files can only be ascociated
>to a single application. This breaks down if you want to load the file into
>a different program than the one with which it is ascociated. You have to "do
>it the long way", defeating the purpose of the ascotiation system in the first
>place.

What?  Why does it "defeat the purpose" of the system to force you to
do it "the long way" in a special case?  In addition, I'm fairly sure you
can use the option key to tell th Finder to run a different application than
the one that created the document you're trying to open.

-- 
Jim Wong (jimwong@owlnet.rice.edu)