GNOME Human Interface Guidelines (GNOME 2). Available Versions: · .3 · · · · · · Same documents, formatted as a. GNOME Human Interface Guidelines. Goals; Resources and Planning; Draft Content; Redundant Content. The primary role of the HIG is to. GNOME Human Interface Guidelines · Controls. A frame is a box with a title that you can draw around controls to organise them into functional groups.
| Author: | Taugor Danos |
| Country: | Sierra Leone |
| Language: | English (Spanish) |
| Genre: | History |
| Published (Last): | 28 February 2009 |
| Pages: | 346 |
| PDF File Size: | 3.45 Mb |
| ePub File Size: | 7.32 Mb |
| ISBN: | 391-9-74947-685-2 |
| Downloads: | 24031 |
| Price: | Free* [*Free Regsitration Required] |
| Uploader: | Jujora |
Rather than using bordered frames, use frames without borders, bold labels to guidelinew the categories stand out, and indented contents. Responding to User Requests 7. Only use statusbars to display non-critical information.
GNOME Human Interface Guidelines 2.2.3
A frame inteerface a box with a title that you can draw around controls to organise them into functional iinterface. Hosted by Red Hat. This white space will make it easier for the user to find the information they need.
Progress Bars Frames and Separators. Hosted by Red Hat. Design for People 1. As such, these guidelines do not cover every possible design that is possible. Found the instructions unclear? About Users Administrators Developers. Go to page content Go to main menu Go to the search field. Hosted by Red Hat.
GNOME Human Interface Guidelines
Pointer and touch input Mouse, touchpad and touchscreen interaction. The user may therefore never see anything you display there, unless they know when and where to look for it. For example, current connection status in a network application, or the size of the current document in a text editor. Types of Menu 4. Do not use them in dialogs, alerts or other secondary windows. As the labels are all similar in length, they should be left-aligned. Patterns and user interface elements form the core of the HIG.
This website is available in many languages Switch Language. Pointer and touch input. Acceptable Response Times 7. When there is no interesting status to report, leave a status bar panel blank rather than displaying something uninformative like “Ready”. Provide a drag handle in the bottom right corner of the status bar of resizeable windows.
Try to keep components consonant with each other in terms of size and alignment. Types of Visual Feedback 7. In Figurethe appearance indicates that the left area would respond to a double click perhaps by saving the documentand the progress indicator on the right is non-interactive.
Use spacing and bold headers instead. If most of the labels in a group greatly differ in length, right-align them instead, so that the controls do not end up too far away from their corresponding labels. This is advantageous because it physically separates dissimilar controls, and also avoids repetition of the frame’s label in individual member control labels. For example, while using the selection tool in a drawing application, “Hold Shift to extend the selection” progress of a background operation.
Patterns – design patterns make up the core of the HIG. Mapping Document Types to Applications 2.
GNOME Human Interface Guidelines (GNOME 2) – GNOME Developer Center
About This Document What’s new? For information on laying out Alerts, see Section 3. A clean layout is crucial to creating a smooth visual flow of information for the user.
Appearance and Content 5. Don’t Limit Your User Base 1. They cover design principles for GNOME 3, common guidelines such as how to write text and use images and icons, as well as a library of design patterns which you can use in your application.
Parts of Windows and System Interaction 3. Structure of the HIG. They have three main sections: Designing Effective Icons 9. Choosing Appropriate Feedback 7. If you are new to the HIG, it is recommended that you start with the page on design principles and then browse the patterns, before going on to other material.
Together, they are the building blocks for application design. Use statusbars only in application or document windows. Inlaid appearance for areas that respond to a double guidelinss Flat appearance for areas that are not interactive. User interface elements Guidelines on common elements, such as buttons, progress bars and popovers.