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

List:       kde-usability
Subject:    Re: amaroK usability report
From:       "Zak Jensen" <coolguyzak () gmail ! com>
Date:       2006-05-07 17:35:18
Message-ID: 21bb44f30605071035o6e331b8dnab0dab9b81425867 () mail ! gmail ! com
[Download RAW message or body]

On 5/3/06, Luciano Montanaro <luciano.montanaro@consulenti.fastweb.it> wrote:
> On Tuesday 02 May 2006 21:30, Chi Shang Cheng wrote:
> I'm not really a usability expert, but I have thought up a couple of reasons
> on why the main menu should have all the actions.
>
> One is "discoverability": a user might browse the menus from time to time to
> find out what actions are available. If the main menu has all the actions
> listed, there is a central place where the user can look. The toolbar and
> context menus are just alternative ways to access common actions.

Is there a use-case that uses different interaction techniques to
create "incremental" discoverability? Think of a mac: there are tons
of "expert" features which are only available through special
interactions with the system (in theirs, I believe it is apple-click.
Since KDE can use 2 button mice, right clicking may serve as a
replacement).

This *may* be where amaroK is coming from. Instead of throwing
everything at the user, they use the most visible elements to expose
the "most visible" functionality.

It allows the user to experiment and feel comfortable with what's
available before exploring, say, the wide world of context menus. In a
sense, it is akin to a "beginner, intermediate, expert" modal
interface. However, instead of using the scorned "modality", it places
different access mechanisms where they make the most sense.

Of course, there are still inconsistencies when it comes to this means
of interaction--most of the things you mention are still
"problematic", and (given that scenario) things like scripts shouldn't
be displayed.

> The other one (thinking again, this may be actually the same as above) is
> that there are many users that do not use context menus.
>
> I'm actually confused on how to "unclutter" menus while still offering
> discoverability...

How about supplanting the menu form of discoverability with
tooltip/ktip information? What if the status bar displayed "did you
know that" information when nothing else of importance is happening?
(Or some other form similar to that?). The user has the opportunity to
discover new things about the interface, but the menus and toolbars
can remain minimal.

> Luciano

 -Zak
_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic