Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!ucdavis!iris!lim
From: lim@iris.ucdavis.edu (Lloyd Lim)
Newsgroups: comp.sys.mac.programmer
Subject: Re: INIT User guidlines proposal
Message-ID: <5783@ucdavis.ucdavis.edu>
Date: 1 Nov 89 20:55:42 GMT
References: <8910310234.AA09180@decwrl.dec.com> <1235@eutrc3.urc.tue.nl>
Sender: uucp@ucdavis.ucdavis.edu
Reply-To: lim@iris.ucdavis.edu (Lloyd Lim)
Organization: U.C. Davis - Department of Electrical Engineering and Computer Science
Lines: 29

My two cents:
The comment that all INIT icons should write on top of each other seems
to be a rather personal and arbitrary choice.  It also doesn't go along with
the current ShowInit scheme.

As for ease of use, this scheme might be better than the current no scheme but
it certainly doesn't seem that easy.  Three modifier keys are involved although
probably only two during a startup when you want to disable one thing or
something.  Even though there is "slow-motion", there is still some timing
skill involved in order to hit the right modifier on the right INIT.

I don't think this even begins to compare with any of the INIT managers out
there where you just hold down one modifier and you get an explicit list of
INITs that you can enable/disable individually or as a group.  This is a
clearer and easier approach.

I don't think you should have to be able to set INIT options at startup.
That's what CDEVs are for.  Setting INIT options at startup makes the code
unnecessarily bigger and violates the dialog at startup no-no.

I think the answer for now is the use of one of the INIT managers (personally
I like INITPicker).  I think the ideal solution for the future is a rewrite
of INIT 31 to include the one modifier, explicit list ease of use for all
INITs.  Only Apple or someone with lots of guts could do this.

+++
Lloyd Lim     Internet: lim@iris.ucdavis.edu (128.120.57.20)
              Compuserve: 72647,660
              US Mail: 146 Lysle Leach Hall, U.C. Davis, Davis, CA 95616