On Aug 21, 2011, at 1:23 PM, Michael_google gmail_Gersten wrote: > My view on the ribbons vs menus is pretty simple: > 1. I can read English. It's standard. > 2. Everyone has different iconography. I cannot read that. > > As long as I can pull down menus with one key, and then move across > the menu bar with another, I can read all the actions very, very > quickly. This is part of why I hate submenus -- they hide the command > list. > > Ribbons? Ribbons are there to be cut. Menus are for ordering > something, like an action.
Yeah, I still find the ribbon in Sibelius to slow me down. It's just not fast, natural. I'm learning the keystroke shortcuts to bring the ribbon up and to open the appropriate tab, then select the correct item. However, it's still a vast amount of hunting and the visuals are difficult. I can read a bunch of menus much faster than navigating the ribbon. I'm using it all day long of late as I have a composition to complete and deliver next Thursday, and I'm still not comfortable. Other things too, like not giving you the standard Mac print dialog box so that I can quickly email a PDF rendering or save it out to one of my PDF rendering aliases. Instead, there's a custom window for handling files - you then have to choose Export, then select an export format/type, then click the export button - name the file etc then go find the file in the Finder .. then use Services (I do) to email with attachment. Is this how things are done on Windows? a zillion steps to do something? In the read me, the Sibelius docs mention right away Microsoft Word and the ribbon concept. I think a lot of other actions must be Windows like as well. If you are a developer, please do not implement ribbons! -Kevin _______________________________________________ MacOSX-talk mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-talk
