Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!genrad!panda!talcott!harvard!seismo!ut-sally!utastro!cositex!bubba!san
From: san@bubba.UUCP
Newsgroups: net.micro.amiga
Subject: Perfect Product...
Message-ID: <170@bubba.UUCP>
Date: Tue, 25-Feb-86 12:40:17 EST
Article-I.D.: bubba.170
Posted: Tue Feb 25 12:40:17 1986
Date-Received: Sat, 1-Mar-86 00:51:58 EST
References: <1349@caip.RUTGERS.EDU> <737@amiga.amiga.UUCP>
Organization: COSI Texas,  Austin, Texas
Lines: 35

...
> == Anyone want to open discussion on "what a perfect product looks like" ?
> I'd be glad to start it off or contribute.
> ---- If these opinions were those of my employer life would be different. ---
> Bruce Barrett

I'd be interested in what people consider an optimal layout (configuration)
for released products.  Consider copy-protected (oh no!) and non-copy-protected
programs.  For instance:

	On a production and non-copy-protected program, is a diskette
	with the tool and sample projects enough?  This may imply (to the
	user) that the disk must be inserted every time that tool is to
	be used.  This may sound ok for a floppy disk based system,
	but what about whenever hard disks become more popular?  Since
	there is an hierarchal filing system, what if the tool is moved
	to a different location in the tree?  Since the MacIntosh people
	may have answered these questions already, perhaps we could get
	some feedback from them?

	As far as personal preferences, what type of production/release
	diskette would *you* like to see for an over-the-counter/average-
	end-user application?

And of course, I don't imagine that the ``perfect product'' subject is limited
to just installation/release stuff.

		Thanks,

		Steve Sanderson
-- 
Steve Sanderson, COSI Texas
		 4412 Spicewood Springs, Suite 801 Austin, Texas 78759
UUCP:	{ihnp4, seismo, ctvax}!ut-sally!cositex!san, san@cositex.UUCP
AT&T:	(512) 345-2780