669
edits
Talk:Menu cleanup: Difference between revisions
Jump to navigation
Jump to search
More elegant solution
Broccauley (talk | contribs) (More elegant solution) |
|||
| Line 107: | Line 107: | ||
I don't think it should be removed from the menus. At least not completely. But I don't think it should be changed at all, because it's a relevant feature for many people (and if the auto-detect may make the dial-up users thing irrelevant, forcing the browser to use the cache instead of the server is not). | I don't think it should be removed from the menus. At least not completely. But I don't think it should be changed at all, because it's a relevant feature for many people (and if the auto-detect may make the dial-up users thing irrelevant, forcing the browser to use the cache instead of the server is not). | ||
--[[User:Tiago Sá|Tiago Sá]] 14:30, 2 June 2010 (UTC) | --[[User:Tiago Sá|Tiago Sá]] 14:30, 2 June 2010 (UTC) | ||
== More elegant solution === | |||
Someone posted a mockup that allows this to be handled much more elegantly by not using a standard Windows menu: | |||
https://wiki.mozilla.org/Talk:Firefox/4.0_Windows_Theme_Mockups#An_idea_for_the_App_button | |||
With a bit of added creativity you could encompass *all* the current menu options like this. The most used functions could be with large text and icons - easy to find and click. Less used options could be in a sub-menu that you could click saying something like "more" or "advanced" etc. | |||
The cool thing about non-standard menus like this is that you really can be creative with each individual menu item. For example the mockup shows a "zoom" option - as well as having a cascaded "zoom" option as in the mockup you could put little "+" and "-" icons that would zoom directly in and out without having to navigate the cascaded menu. [[User:Broccauley|Broccauley]] 21:15, 5 July 2010 (UTC) | |||