Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 May 1995 22:14:48 -0700
From:      "Jordan K. Hubbard" <jkh@freefall.cdrom.com>
To:        Julian Elischer <julian@ref.tfs.com>
Cc:        hackers@FreeBSD.ORG
Subject:   Re: [On the new Install] 
Message-ID:  <15051.801897288@freefall.cdrom.com>
In-Reply-To: Your message of "Tue, 30 May 95 20:29:51 PDT." <199505310329.UAA21742@ref.tfs.com> 

next in thread | previous in thread | raw e-mail | index | archive | help
> I'd more want a message saying "This is not being written yet..
> it's safe to play with this screen"
> or something..

Hmmm.

> I think you are wrong..
> it assumes you have EITHER the correct size or correct number of cylinders..
> for IDE and SCSI, you DO have the correcdt size anyhow..

Huh?  It doesn't assume anything of the kind!  It simply lets you edit
all three fields as one string.  And hey, I ain't changin' it so
there's not much point in arguing over it anyway! :-) If you feel like
working something up that you think is better suited then I'm not at
all adverse to looking over/adopting your code, it's just not
important enough to me to do anything about it personally!

> > Huh??  You mean OK and Cancel, right?
> (whatever.. the point is you can't GET to OK on some of them)

Well, I _am_ constrained somewhat by the objects that libdialog gives
me!  In this particular case, I have no other way of knowing when the
user wants to leave the menu!  When you're selecting an item and
hitting return, what you're REALLY doing is selecting the OK button
(you'll notice that the cursor stays over it after the arrow keys have
brought you to some item of choice).  If I want to leave, rather than
make a choice, then I have to use Cancel.  Sorry, but again - if you
want to see some other behavior, you'll have to make the (reliable!)
hacks to libdialog yourself and submit them.  I have zero interest in
making changes of that sort at this late stage!

> CANCEL IN EVERY OTHER APPLICATION ON EARTH means 'leave it untouched!'

See above.

> no, you are seeing it as a person who knows what it's doing,
> and I'm seeing it as a new user..

I'm also seeing it as a person who knows what's easily _possible_, so
kindly try to take a little of that into account.  I'm not wholly
blind to good end-user-oriented suggestions, believe me, but if a lot
of the things you're asking for were EASY then you may rest assured
that I'd have done them already!  To return the accusation, I think
you're not thinking enough like a FreeBSD hacker yourself, and you're
not making informed suggestions based on a reasonable analysis of the
tools available.  Please go look at libdialog (and heck, sysinstall) a
little more before you get too far out with the suggestions, please!

> no, 99 for example is MACH.. you don't print that, even though old fdisk
> knows about it (came from MACH after-all) I know I just watched it again..

Well, I'll take it up with Poul.  I thought that we were handling all
known types, sorry!

> let me edit a table you can slurp back in...

Ok!

> > No problem.  Just (M)ount the entries rather than creating them.
> oh that's so obvious!, surely you can make it more inscrutible?

Like I said, there WILL be a help file there that makes it pretty
obvious!  If the user is not willing to even read what doc is there
(when it's made available) then I truly have no interest in bending
over backwards to accomodate them.  There has to be some give and
take, and I have the sneaking suspicion that you yourself didn't read
ANY of the documentation files! :-)

						Jordan



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15051.801897288>