Re: Why the Apple II was on the right track...

[jefbla@bconnex.net (Jeff Blakeney)]

On Fri, 7 Mar 1997 23:32:33 +1300, dempson@actrix.gen.nz (David
Empson) wrote:

>Jeff Blakeney <jefbla@bconnex.net> wrote:
>
>> This is why I am against the idea of a */SYSTEM/PREFERENCES folder as
>> well as the */SYSTEM/HELP that Seven Hills started with their new help
>> NDA.  Preferences for a program and any related help files should be
>> stored with the program.  Either in the same directory as the program
>> or in its resource fork.
>
>I agree in the case of help, but preferences certainly shouldn't go in
>the application resource fork, and there are good reasons for not
>storing them in the same directory as the application either.
>
>1. [Resource fork.] The application will be modified, making it
>difficult to determine whether two separate copies of the program are in
>fact the same version.  In addition, reinstallation will cause the
>preferences to be lost.

Agreed.  It can also mess up any virus scanning software that sees a
program changing a program on disk and would probably flag it as a
possible virus.  Not really all that serious, but it would be
annoying.

I just worded that last sentence to save typing and it came out with
my meaning a little unclear.  Preferences should be in the program's
directory and help files should be in the program's resource fork.

As to determining whether two copies of a program are the same
version, they should have comments in their resource fork to give you
that information when you ask for Icon Info.

>2. The application might be on a read-only volume.  (The system folder
>should never be, except with a rather small floppy system.)

I can't really see under what circumstances you would have your
program on a read only volume.  I can see it if you are running a
program from its original write-protected disk in which case, you
should be using a backup copy or installing it onto another drive.

There is also the case of CD-ROMs but I don't think many people really
want to run applications from a CD-ROM either.  With the fact that
they are getting faster, this might become more of an issue but I
think most people would still prefer to have their commonly used
applications always available on their hard drive rather than having
to find and insert the CD with the application they want to use.

>3. The application might be on a file server and be shared between
>multiple users.  Each user should have their own preferences.

This is something I don't ever think about as I don't use, nor have I
ever used, a network.  I'm thinking from the point of view of your
typical home user.

It should be possible to get around this problem here as well by using
aliases.  The use double clicks an alias in his directory to execute
the program from the network drive while passing it the location of
his/her preference file.

>4. Storing data files (such as preferences) along with an application
>makes backup/restore a harder operation.  On my Mac, I don't need to
>keep regular backups of my application folders, only my data and system
>folders.

This could be a problem but I'm wondering, when a program is
installed, does the backup bit get set to say the program needs to be
backed up?  If so, here is another place where the installation
program could help out.  If you install a program and only the
preference file is flagged as needing to be backed up, then backing up
all your applications preference files would be easy.  Just select all
your application folders in your backup program.

Personally, I don't back up my system folder or applications because
of how infrequently I need to re-install my operating system or
programs.  Setting my preferences again after a re-install isn't too
difficult or time consuming especially when I only have to re-install
maybe once a year.

So it would seem that what I would like to see is installation
programs that allow you to set where you want to store your preference
file, give you the option to flag all the program files or just the
preference file for backup and ask if the user would like an alias
created somewhere that will start the program with a certain set of
preferences.

Hey, I just realized that this would also allow you to set up multiple
preferences for a program and you just have to double click the
appropriate alias to use it.  Could be useful for families where each
member would like different preference settings for the same program.
For instance, you could have alias' called Mom's Spectrum, Dad's
Spectrum, John's Spectrum, etc.

What do you think, am I getting a slightly better system set up here
or am I just dreaming again?