On the other hand, if you program's commands don't map naturally, don't try to force it. Determine a more natural structure, and be sure to perform a lot of user testing to make sure that you've got it right.
The Home tab is an exception to these considerations. While you don't have to have a Home tab, most programs should. The Home tab is the first tab, and contains the most frequently used commands. If you have frequently used commands that don't fit into the other tabs, the Home tab is the right place for them. If you can't determine a meaningful, descriptive tab name, it is probably because the tab isn't well designed.
If your ribbon organization just isn't working, reconsider your tab design. Dividing commands into groups structures the commands into related sets. The group label explains the common purpose of its commands. In this example, the Font and Paragraph groups are more noticeable than the Clipboard group, because they are what the eye sees first when moving up from the document.
In this example, the Tracking group receives the most attention, in part because the highlighted Review tab acts as a focal point. You can use various types of previews to show what will result from a command. By using helpful previews, you can improve the efficiency of your program and reduce the need for the trial-and-error learning approach. Live previews also invite experimentation and encourage creativity. In this example, Word changes the Text highlight color and Font color commands to indicate their current effect.
In this example, the Page Color command performs a live preview by showing the effect of the color options on hover. Live previews are a powerful feature that can really improve your users' productivity, but even simple static previews can be a big help.
Scaling a toolbar is simple: if a window is too narrow to display a toolbar, the toolbar displays what fits and makes everything else accessible through an overflow button. A goal of rich commands is to take full advantage of the available space, so scaling a ribbon requires more design work. There is no default ribbon size, so you should not design a ribbon with a particular width in mind.
You have to design layouts with a wide range of widths and realize that any one of them could be the one most of your users will see.
Scaling is a fundamental part of ribbon design, not the last step. When designing a tab, specify the different layouts for each group up to three as well as the combinations that can be used together. The ribbon will show the largest valid combination that fits the current window size. Toolbars scale using an overflow button. There is no default ribbon size. The smallest size is a single pop-up group icon. Whenever practical, map your program's commands to these standard tabs, given in their standard order of appearance.
If you have contextual commands related to format, design, and layout, but not enough for multiple tabs, just provide a Format tab. Whenever practical, map your program's commands to these standard groups, which are given within their associated tabs in their standard order of appearance. Take advantage of the discoverability and scalability of ribbons by exposing all the commonly used commands.
When appropriate, move frequently used commands from dialog boxes to the ribbon, especially those that are known to be hard to find. Ideally, users should be able to perform common tasks without using any dialog boxes.
Don't use the scalability of ribbons to justify adding unnecessary complexity. Continue to exercise restraint don't add commands to a ribbon just because you can. Keep the overall command experience simple. The following are ways to simplify the presentation:. Present each command on only one tab. Avoid multiple paths to the same command especially if the command requires many clicks to invoke.
It may seem like a convenience to find a command through multiple paths. But keep in mind that when users find what they are looking for, they stop looking. It is all too easy for users to assume that the first path they find is the only path which is a serious problem if that path is inefficient.
Exception: Contextual tabs may duplicate a few commands from the Home and Insert tabs if doing so prevents changing tabs for common contextual tasks. Within a group, put the commands in their logical order, while giving preference to the most frequently used commands. Overall, the commands should have a logical flow to make them easy to find, while still having the most frequently used commands appear first.
Generally, commands with 32x32 pixel icons appear before commands with 16x16 pixel icons to aid scanning across groups. Avoid placing destructive commands next to frequently used commands. A command is considered destructive if its effect is widespread and either it cannot be easily undone or the effect isn't immediately noticeable. Use separators to indicate strongly related commands, such as a set of mutually exclusive options. Consider using toolbar-style groups for sets of strongly related, well-known commands that don't need labels.
Doing so allows you to present many commands in a compact space without affecting discoverability and ease of learning. To be so well known, such commands are frequently used, instantly recognized, and therefore tend to be on the Home tab. Use 32x32 pixel icons for the most frequently used and important labeled commands. When scaling a group down, make these commands the last to convert to 16x16 pixel icons. Avoid arbitrary command placement. Think carefully about your tab and group design to ensure that users aren't wasting time inspecting every tab to find the command they want.
Avoid marketing-based placement. Marketing objectives around the promotion of new features tend to change over time. Consider future versions of your product and how much frustration a constantly changing organization will cause.
Disable commands that don't apply to the current context, or that would directly result in an error. If helpful, use the enhanced tooltip to explain why the command is disabled. Don't hide such commands because doing so can cause the ribbon layout to change, making the ribbon presentation unstable. Don't update command labels dynamically. Again, doing so might cause the tab layout to change, resulting in an unstable appearance.
Instead, design commands so that they work with constant labels. Prefer direct controls. A command is direct if invoked with a single click that is, without navigating through menus.
However, with the exception of in-ribbon galleries, direct controls don't support Live preview, so the need for Live preview is also a factor. Use Live preview to indicate the effect of the options when a command is among a related set of formatting options, and Live preview is important and practical, especially if users are likely to choose the wrong option otherwise. Expose direct commands using the following controls in the following order of preference. If your ribbon consists mostly of menu buttons when displayed at full size, you might as well use a menu bar.
Prefer immediate commands. A command is immediate if it takes effect immediately that is, without dialog boxes to gather additional input. If a command might require input, consider using a split button, with the immediate command in the button portion, and the commands that require input in the submenu. Provide icons for all ribbon controls except drop-down lists, check boxes, and radio buttons.
Most commands will require both 32x32 and 16x16 pixel icons only 16x16 pixel icons are used by the Quick Access Toolbar. Galleries typically use 16x16, 48x48, or 64x48 pixel icons. Make sure ribbon icons are clearly visible against the ribbon background color. Always evaluate ribbon icons in context and in high-contrast mode. Choose icon designs that clearly communicate their effect, especially for the most frequently used commands.
Well-designed ribbons have self-explanatory icons to help users find and understand commands efficiently.
For example, when a user clicks an image in a document and then clicks the Picture Tools tab, the Picture Styles gallery becomes available. A set of controls that appears in context when an object is selected. A user can use these controls to perform actions upon the object. For example, when a user selects text, the formatting mini toolbar automatically appears above the text. As the mouse pointer moves closer to the mini toolbar, the toolbar becomes more visible. As the mouse pointer moves away from it, the toolbar fades away or disappears altogether.
A ScreenTip is a small window that displays descriptive text when a mouse pointer rests on a command or control. A ScreenTip may include a link to a Help topic. Users can add icons to this toolbar or remove them.
A specific icon that is used within a group to launch a related dialog box. It is located in the lower-right corner of a group. Small keyboard tips that indicate what key to press to access program functionality. The user must press the Alt key to see the KeyTips and then press the indicated number or letter to run the associated command. In the following example, pressing the number 1 saves a Word document.
In Office , Ribbon is capitalized. In Office , ribbon is lowercase. Use on the ribbon, not in the ribbon. On the ribbon, click the appropriate tab or group to display the command that you want to add to the Quick Access Toolbar.
Some tabs display in the ribbon only when they are relevant to the task at hand, such as when formatting a table or an image. To refer to tools, use the following format: Under x on the y tab, in the z group, click zz. On the Home tab, in the Font group, click the Font box down-arrow. On the x tab, in the y group, click z. On the x tab, in the y group, click z , and then click zz. On the Review tab, in the Comments group, click New Comment. On the Home tab, in the Font group, click the arrow next to the Text Highlight Color icon, and then click the color that you want.
Click the Review tab, and then click New Comment in the Comments group. On the Review tab, under Comments , click New. A menu is a group of the main commands of a program arranged by category such as File, Edit, Format, View , and Help. Menus are usually displayed on a menu bar typically located near the top of a window.
Menus contain commands. Do not refer to a menu command as a choice or an option. Also do not refer to a menu command as a menu item , except in content for software developers about the user interface. To describe user interaction with menus and menu commands, use click. Do not use choose, select or pick. If you must refer to the user action of opening a menu, use click. To open a submenu, the user points to a command on the main menu, which causes the submenu to open, and then clicks the appropriate command.
On the View menu, point to Sort by , and then click Date. The following illustration shows elements of menus. In most content, you should not have to refer to user interface elements by their technical names. The usual practice, here as elsewhere in the user interface, is to refer to elements by their labels. In general, refer to unavailable commands as unavailable , not as dimmed, disabled , or grayed unless you are describing their appearance.
In that case, use dimmed , but not grayed or disabled. In content for a technical audience, it is all right to refer to unavailable commands as disabled. If the Paste command is unavailable, first select the text that you want to paste, and then click Cut or Copy.
The following buttons on the Shortcut menu all control how your commands appear although there are subtle differences. Default Style - This restores the default setting which is normally to display the image and text on menus but just the image on toolbars. Text Only Always - The image will not be displayed when on a menu or on a toolbar. Text Only in Menus - The image will not be displayed when on a menu, but will be displayed when on a toolbar.
Image and Text - The text and the image will be displayed when on a menu or on a toolbar. This will display a larger worksheet area which can often make it easier to work. It is possible to obtain a list of all the built-in commands that are available in Word. Select the Commands tab and select "All Commands" in the list box on the left hand side. This option will list all the commands in alphabetical order, making it easy to find the "ListCommand" commands.
You can then drag this command to a menu or toolbar so it is permanently available. Once you have included this command on to an existing menu or toolbar you can close the Customise dialog box.
Selecting this command will display the following dialog box. Current menu and keyboard settings - Creates a new document containing all the built-in menu and keyboard settings. All Word commands - Creates a new document containing all the available built-in commands.
You can move toolbar buttons by holding down the Alt key and dragging the button to a new location. To remove a toolbar button hold down Alt and drag the button onto the document. Remember that the lower your screen resolution the fewer buttons you can see on a toolbar. Do all you can to maximise your screen resolution Any changes you make to your toolbars etc ensure that they are saved in your "Normal.
You can only add a toolbar to a template. Words interface for manipulating built-in shortcut menus is slightly nicer than in Excel, although you can't manually add a shortcut menu and you can't modify a custom toolbar?? If you have an addition drop-down menu at the top however the buttons do not actually do anything then you need to reset your Menu Bar in Normal. There is a big difference between the "FileNew" and the "FileNew In the macros in box, select "Word Commands".
In the list choose List Commands and press Run. It displays commands shortcut keys and the menu they are available from. Be aware that toolbars will overlap when there is not enough room on the screen.
Word's new personalised menus only show commands you frequently use. You can close a toolbar by clicking on the tiny cross in the top right corner. This is only available when the toolbar is floating.
0コメント