[openbeos] Re: BeOS/Haiku UI question

Hello
There is a windows application (k9) that simply has a status bar and a close button (the x one)
when changing something on the screen, the status bar is updated saying preferences saved.
this could be nice to have.
imho, it would be more intuitive that a preflet is simply viewing the preferences that are stored on disk.
in such a case, closing is simply closing, so when opening again you have the same prefs as when you
pressed close. (all prefs are saved immediately to disk.) (viewer / changer)
for the bemail example, this would mean the email you started earlier would be there when you run the app again.
in dangerous situations, screen changing to unviewable resolution,
conceptually it would be more like a try.. than apply.
but in practice it's the same. still, a count down to revert is available etc.
on usability, consider this example: deleting from a folder - seeing a list of icons and pressing delete means mentally:
to see the list, to search for the right one to pick, and press delete.
vs.
seeing the list, searching for right icon, pressing right click, searching (thinking what labels mean)
for delete button and choosing delete.
what i mean by this example is that to be simple you need to think what mental operations
the user is performing, not just how long it would take (the discussion about cancel / revert / apply)
and lastly, i think being used to the windows way is not necessarily the best way.
using obvious concepts (fast recognition what this thing does)
is better than burdening with more concepts to learn. (look at your email program: send is an envelope with an up arrow, save is a diskette icon, etc.)
beos gives almost a natural feeling, simplicity in operation and concepts, emails are searchable message files, find behaves as if all your partition files are in one directory. (easier to grasp)
hope this helps to clear this up.

that's my point of view on this.
Thanks, Kobi.

On Thu, 16 Feb 2006 01:41:38 +0200, Jorge G. Mare <koki@xxxxxxxxxx> wrote:

Hi all,

The BeOS way from preflets tends to be (Apply)/Revert/Close. I have
also explained why I think that is  a very sensible way of doing
things. 

I think your opinions are somewhat biased by your experience of
Windows. You understand what "Cancel" does because of your experience

with windows,

Yes, I admit my guilt: I am tainted with Windows!

But so will be many users that at some point in time may try Haiku. Not
I that I think that this creates an unsurmountable learning curve for
most people, so be it. :-)

Stephan Assmus <superstippi@xxxxxx> wrote on Wed, 15 Feb 2006 23:48:13
+0100

1) for settings that cannot be applied live:
Defaults Revert Apply (leaves window open) Tab-Close (applies
settings too)


Hmmm.... I think in this case, Tab-Close should not apply changes. At
least that's what I understood.

As a visual feedback to the user, preferably the Apply button should be
disabled when you open the window, and enabled only when there is a
change to apply.

2) for settings that are applied live:
Defaults Revert Tab-Close (simply closes window)


Sounds good to me.

"Marcus Overhagen" <marcusoverhagen@xxxxxxxx> wrote on Wed, 15 Feb 2006
23:49:45 +0100 CET

- The order of [Defaults] [Revert] and optionally [Apply] buttons
should be consistent


I fully agree with this. Consistency is very important.

Some preferences use "Save", "Use", "Done" and "Apply". I think this
should be reviewed,
and changed into "Apply".


Agreed here too.

Thank you guys. I have a much better understanding now.

Cheers!

Koki





Other related posts: