[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-look
Subject:    Re: Comments on GUI Standards
From:       Rik Hemsley <rik () rikkus ! demon ! co ! uk>
Date:       1999-09-26 15:01:13
[Download RAW message or body]

#if Alistair
> And I'll bet you that NO application will prompt you as it's closing "You
> have made changes to the application settings. Do you want to save them ?".

XFMail ! (The worst UI ever)

> [...] The author essentially argued that changes should be savd as they are
> made. Combined with sophisticated Undo and Revision mechanisms, I think this
> is an excellent approach.

Agreed. I remember many years ago I used a Mac for the first time, and was
surprised when I scribbled over a picture in HyperCard and it saved my
scribble without asking. That's a little crazy, but I do believe that when
you press a switch, you shouldn't have to press another two switches to confirm.

Taking it too far is when you change the setting as the switch is pressed (in
a settings dialog). XFMail does this ! A simple 'OK' and/or 'Apply' is perfect.

> Some guidelines or heuristics on the (over) use of colour in apps should also
> be present.

Yes, like 'Don't use them !' What I mean is, if you use any colours that
aren't user configurable from the Display Settings dialog, you should make
them configurable. Just making something red isn't a smart move when someone
is using a pink background. Better to use a colour from the standard scheme
that is guaranteed (well, almost) to contrast with its surroundings.

> Also of use would be a study of BeOS and OS/2. Remember that Be was started by
> some ex-Apple staff, so they probably have some good ideas we can steal (no
> point in reinventing the wheel, eh?).

Certainly. The thing that most impressed me about BeOS when I first used it
was the _lack_ of configurability. The interface was easy to use, and didn't
need to be changed. Sure, some people would prefer their little tweaks here
and there, but nothing is that important. Everyone can change their habits
to ones that have been proven to be good defaults, whether they like it or
not. If they're that bothered, they can not use the system. (ooh that was
a bit contentious)

One more thing I noticed yesterday:

When you select a menu item that may be checked (or is a 'radio button'), the
menu disappears immediately.

I'd like to see menus work more in the NeXT style, where the item wiggles
a bit before the menu disappears. I don't know if this would slow people down
too much, but I find it quite reassuring to be given some visual feedback
of what I've just done.

Cheers,
Rik

[prev in list] [next in list] [prev in thread] [next in thread]