Linked by Thom Holwerda on Thu 17th May 2007 18:54 UTC
Permalink for comment 241355
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2005-07-10
It sounds like you missed my point. I am not disputing that putting the menubar at the top of the screen makes it a faster target to acquire than a window menubar. This is, as you said, a well studied and an established rule.
I am arguing that when you take it a step further and ask a user to perform a full action, which requires them to recall the location of a menu item or search for it, that the time saved by having the menubar at the top becomes so small it is meaningless. At the time I was interested in this, I couldn't find any studies of the top menubar that went beyond target acquisition and focused on the user's time to perform tasks in actual applications, which is why I did it myself and was surprised by the results.
Not to completely derail the thread, but why not offer circular menus? How about a patch to bisect the display of contextual menus at the mouse cursor so menu items are closer to the cursor?
(credit to Victor Zambrano for this idea)
http://www.asktog.com/images/fittsCascadingMenus.gif
These features can be enabled by default and potentially help more users so they arguably make more sense than an off-by-default top menubar.