[40] in installers
Re: eudora 3.0.2 installer
daemon@ATHENA.MIT.EDU (Scott G. McGuire)
Tue Mar 18 13:28:35 1997
In-Reply-To: <v03020906af532f15f278@[18.81.0.167]>
Date: Tue, 18 Mar 1997 13:28:06 -0500
To: Alicia Allen <iggy@MIT.EDU>
From: "Scott G. McGuire" <smcguire@MIT.EDU>
Cc: installers@MIT.EDU
Alicia Allen <iggy@mit.edu> writes in regard to how the Eudora Installer
decides whether to configure new settings or not:
>Hmm, I think you should reconsider how this works then,
>perhaps it could tell the clients, "here are your current settings,
>shall we change them?"
>
>People may think that they don't have this stuff on their computer, because
>they want to use it to set up multiple logins, or they have inherited
>someone else's computer, or something, but they really do...
>
>I don't know what sort of complexity this would add, so of course
>I don't know if this is a reasonable suggestion or not.
Well, the main problem is, what do you do if the user has multiple Eudora
Settings files on their computer (or the computer's set up for multiple
users)? Ask them about each one? Might get a little tiresome, and there's
no way to identify which one is their "main" settings file.
I suppose we could ask, "There are existing settings files on this
computer, but would you like to configure a new copy which will be stored
in your System Folder?"
Also we didn't want to throw a lot of dialogs up at the user, because we
didn't want to confuse/annoy them with a lot of questions. So we tried to
do what seemed to make the most sense (although it's good to get feedback
to see if anyone else thinks our choices are "sensible"). There are a lot
of potential setups, and we can spend time trying to anticipate them, but
we'll never anticipate all of them, so you have to stop somewhere.
--Scott G. McGuire / smcguire@mit.edu
