Right clicks are not necessarily discoverable, but they can be
useful. They help with that pesky "fitts law stuff" i.e. the closer
and larger the target, the faster and more easily a user will execute
the action.
That said all web apps constitute a compromise-- is the browser the
application, or is the "web app" the application?
I would not worry too much about the browser context menu
personally-- in my experience (the apps I have led design/HCI effort)
users (typ. 20-40yr old businessfolk accessing an app a couple of
times a week for the 20,000ft demographic) seldom use the context
menus. They usually look for a toolbar, and the power users look for
the keyboard.
(Thats also a generational thing btw)
just my .02
Jeremy
On Nov 6, 2007, at 4:12 PM, Matthew Eernisse wrote:
Travis Vachon wrote:
Like a right click context menu? How would that work? Are you
suggesting catching the right click event and not popping the
normal browser context menu? I always find that ugly and not what
I want, but I suppose I'd be open to being convinced otherwise.
I'm not normally in favor of the right-click in Web apps either,
although I suspect more than a small part of that is my developer
hat talking (not wanting something to keep me from getting to the
right-click browser menu).
As long as it's not trapping right-click for the entire page, and
it's confined to specific, obvious parts of the UI (the Collection
Selector, the lozenges), I think it might be workable.
We got fairly consistent commentary from the FLOSS Usability Sprint
that a context menu could be really helpful for certain common
actions. Granted, it's UX people talking, not normal end-users, but
the feedback was pretty universal.
Matthew
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
