Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!dewey.soe.berkeley.edu!oster
From: oster@dewey.soe.berkeley.edu (David Phillip Oster)
Newsgroups: comp.sys.mac.programmer
Subject: Re: INIT User guidlines proposal
Message-ID: <32278@ucbvax.BERKELEY.EDU>
Date: 31 Oct 89 16:53:14 GMT
References: <8910310234.AA09180@decwrl.dec.com> <1235@eutrc3.urc.tue.nl>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: oster@dewey.soe.berkeley.edu.UUCP (David Phillip Oster)
Organization: School of Education, UC-Berkeley
Lines: 26

1.) there should be some indiciation that an INIT failed to load
successfully. Either drawing an X on its icon, or not drawing its icon are
okay choices, though I prefer the former.

2.) There should be a one-key way to make an INIT not load. The command
key is a good choice.

3.) Inits should have NO user interface, NO modal dialogs.  If the init
needs to talk  to the user, it should do it through a Control Panel CDEV.

4.) I don't like TOP's modal dialog. It gets in the way when all I want is
to reboot without multifinder.

5.) There already is a good interface for turning INITs on and off. It is
called the Finder. Provided you can turn off a buggy INIT so you can get
up under the Finder, you can choose what INITs you want by just moving
things into and out of the system folder. Arrange your INITs in patterns
that make it easier.  Apple wants users to use the Finder for this kind of
thing, for example the Font/DA mover will be replaced by just dragging
fonts and DAs around in the Finder, in System 7, in all likelihood.

> The mac is a detour in the inevitable march of mediocre computers.
> drs@bnlux0.bnl.gov (David R. Stampf)
--- David Phillip Oster          -master of the ad hoc odd hack. 
Arpa: oster@dewey.soe.berkeley.edu 
Uucp: {uwvax,decvax}!ucbvax!oster%dewey.soe.berkeley.edu