Tag Info

Hot answers tagged

35

If you implement the Ribbon, you are also supposed to implement the Quick Access Toolbar, where the user can add options they require. I find this useful in Office for example, where I can put common commands and not have to remember where they are on the main ribbon.


21

There are three groups of Office users: Casual, or Know-nothing Users. This is your mom trying to type a recipe in Word, or your dad trying to make a list in Excel. These are the people who have no idea how to format tabs, they just hit the spacebar until the cursor is in about the right place. For these people, the Ribbon UI is a godsend, since they don't ...


18

Well, except for the amount of space used, I found it more user-friendly than the classical menu bar. There are many reasons for this: Images: Icons are bigger than on classical menu and toolbar, making it easier to understand for newcomers. Previsualisation: Nearly all the actions that affect the layout can be previewed without leaving the ribbon, making ...


14

I think the best example you could look at is Ms Access. All the CRUD commands are in a Records group and the Find command is in the Find group!


12

In this talk, The Story of the Ribbon, Jensen Harris explains how the Ribbon came to be from the old Office 2003 UI. At this point, he mentions what he calls Command Loops: two or three commands that users often run in sequence, that should be in the same tab of the Ribbon. We looked at Command Loops, which is if you have two commands that you use over ...


11

The ribbon was designed for programs with a lot of commands, CRUD application tend to have just a few commands so maybe the ribbon is not the right UI to begin with. You can do what MS did when they designed the ribbon, take as many people as you can (that know the field, preferably customers) give then a list of tabs/groups and a few command and let them ...


9

Keyboard-related usability issues with the Ribbon The ribbon is great for the discoverability of mouse access to features. However, in my experience, that same user experience isn't really there for when it comes to keyboard access. The main problems are that Office 2003 keyboard shortcuts are no longer discoverable, and the new Office 2007 "Alt key" ...


8

Martin Dostál conducted a study of the Ribbon interface focused on evaluating user acceptance of the new mechanism. He surveyed 117 participants of varying demographics and experience with computers and office software with the following hypothesis: Our hypotheses were as follows: H1 Ribbon user interface is received better by younger people. ...


8

A few options: Have good, easily discoverable keyboard shortcuts. These users sound like expert users, and keyboard shortcuts would probably be faster for them than either the new or old interface. It would depend on them learning this new way of working, though. By "easily discoverable", I mainly mean list the keyboard shortcut in the tooltip. ...


7

Quoting from Microsoft website: Instead of uniform sizing, commands are sized relative to their frequency of use and importance. In addition to making the most frequently used commands easier to find and click, it also makes them more touchable. That last word 'touchable' links to a page which describes various characteristics of the Microsoft touch ...


7

I've got the following probelms with the ribbon bar: It takes up an immense amount of space which on a small screened laptop can actually be really irritating. You can however hide the ribbon bar, but the means to do this is not obvious. There is no way to revert to a "Classic view", I've spent quite some time looking for features which I knew exactly ...


7

It's the same as with any major UI alteration. People familiar with the old UI have to re-learn and that's a considerable downside for them. New (and less experienced users) have fewer adjustment to make. Familiarity with an old interface (or just another interface) may already bias you against change. Objective usability testing is really hard. Hey, ...


7

Nice question. A concept to base some research on for this issue is "kinesthetic memory". Basically, the memory that your body has to complete tasks (such as playing the guitar without looking at the strings, touch-typing etc). I've had a quick look around the web for useful articles, and here's an example. ...


6

Looks into GOMS analysis. It can give you explicit timing for tasks using mouse vs. using keyboard. You will definitely be able to prove the difference this way.


5

Ribbon A ribbon by definition is a bunch of menus placed on tabs. Because the tabs “stick” after being selected, it makes most sense when you can divide your commands at the top level into discrete tasks, where you expect users to execute multiple commands on a single tab without needing a command on another tab. In practice, this is rarely how things work ...


5

It seems like the different options are more related with each other than that they are unrelated. They all manage "tree operation". In that sense it would make a lot of sense to combine them on just 1 tab. It would take away the need for users to constantly switch between the tabs. The fact that you have plenty of screen real estate left is also an ...


4

Can you put it above the ribbon at the tab level?


4

One way would be to implement a new floatable quick access area that's always visible, to where the user can drag and drop the favorit items. Hard to tell if this answer means that you have to alter your current ribbon implementation, as you don't want to. This has the advantage of not forcing the users to always be in their favorites ribbon tab. After all, ...


3

I think you're confusing advanced with complicated. I would say that the most advanced app is the one that gets the job done as easily as possible, with the fewest steps, in the most intuitive way. When you look at it like that, there are many very advanced touch applications. Compare the mail app on the iPhone to Outlook. I think the mail app is more ...


3

I know that this thread was from a lot of years ago, but I was feeling in an irritable mood after yet again having to click-click-click my way just to change to a new window in Excel. (And Alt-Tab is not a solution; I have a LOT of windows open constantly and having to shuffle through every window of every application that I have open is nowhere near as ...


3

I'm in almost the same situation that you are with my application and designing a "Ribbon" interface. I've contemplated a situation where I group commands in the ribbon based upon the core "business" object. In other words, if my app allowed users to manage Clients and Vendors would it make sense to have a ribbon group dedicated to Clients, with all of the ...


3

For starters, I recommend reviewing the official Ribbons guidelines. In general, though, I think the intent of the ribbon is for use as a space to expose commands, not for things like confirmation data.


3

This would be a menu. The image would specifically be a an Options Menu. From there it get's less specific and more descriptive. You could call it a Modal Options Menu or a SlideUp Menu for something that incorporates a description of the accompanied animation. As far as I know, there is no standardized word or label.


2

I've been thinking about this too, and the main idea I've come up with is similar to what Tim Lentine described: having a tab for each of my main business objects. I'd put the most commonly performed commands for that object in the tab for it, for example and "Order" object might have a commands to change status (eg cancel, ship, etc), bill, send invoice, ...


2

Looks like Micrsoft is putting it below the ribbon bar, as seen in the screenshot for Windows 8 file explorer described in the msdn blog. They also have some other components included with the search bar, sich as the forward/back buttons and the location control.



Only top voted, non community-wiki answers of a minimum length are eligible