Path: utzoo!attcan!uunet!super!udel!gatech!uflorida!haven!ames!pasteur!ucbvax!hplabs!hp-pcd!hpcvca!charles
From: charles@hpcvca.HP.COM (Charles Brown)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Amiga Roadblocks to User Friendliness
Message-ID: <1410011@hpcvca.HP.COM>
Date: 23 Dec 88 21:22:14 GMT
References: <9407@gryphon.COM>
Organization: Hewlett-Packard Co., Corvallis, Oregon
Lines: 53

> Except that clean removal is cleaner if all the applications keep their
> specific commands in a common applications execute file, as they can
> have no fear of removing commands that were inserted by them, assuming
> we can all agree on a format.

Sounds good.  (see below)

> Wouldn't it be better to have:
>	execute s:appspecifics
> in your startup chain, and then appspecifics would look something like:
>	;# Aegis Videoscape 3D specifics
>	assign vid3d: dh2:viddir
>	path dh2:viddir add
>	;# NewTek Digi-View specifics
>	assign dview: dh2:dviewdir
>	path dh2:dviewdir add
> etc.

Except that I don't believe manufacturers would make it as clean as
you show here.  Why should they bother putting in the header line?
	;# NewTek Digi-View specifics
Financially it only helps them to make it easy to install the program.
It does not help them at all to make it easy for me to remove their
program from my system.

If we combine both proposals we make the s:appspecifics file look like:
	execute s:ea_startup
	execute s:aegis_startup
	execute s:newtek_startup
I like this best of all.  I figure that the less editing the install
does to my global files, in this case s:appspecifics, the less chance
my system will get destroyed and the better chance I have of restoring
it if it is damaged.

> And then make sure each program as an install/remove icon that will
> automatically insert and delete their appropriate sections?  

Icon???  I don't DO icons!

> Granted, applications need re-install (move to somewhere else) and
> remove options as well as install, all of which operate on the
> s:appspecifics file.
> --Keith Doyle

Now this sounds VERY dangerous with your proposal.  What are the
chances that the string search for ea specific lines will accidentally
find some aegis lines as well?  When we combine both proposals this
becomes a simple matter of editing s:ea_startup, which I am much more
likely to trust the application to do.  After installation, the
s:appspecifics file does not need to be touched at all.
--
	Charles Brown		charles%hpcvca@hplabs.hp.com
	Not representing my employer.