< Projects | Usability Revision as of 09:21, 8 July 2013 (view source)Htietze (talk | contribs) (→User-driven information)← Older edit Revision as of 10:08, 8 July 2013 (view source) Htietze (talk | contribs) (→System triggered notification)Newer edit → Line 69: Line 69: === System triggered notification === === System triggered notification === −* [[Projects/Usability/HIG/Notifications|Notification]] is a system-triggered message used to acknowledge about events out of the current context.+* Provide a [[Projects/Usability/HIG/MessageWidget| message panel]] to inform users about non-critical problems. +* Use a [[Projects/Usability/HIG/Notifications|notification]] as system-triggered message to acknowledge about events out of the current context. * Progress indicator * Progress indicator Revision as of 10:08, 8 July 2013 Contents 1 Structure 1.1 Conceptual Model 1.2 Task Flow 1.3 Organizational Model 2 Behaviour 2.1 Viewing and Navigation 2.1.1 General navigation 2.1.2 Access functions 2.1.3 Grouping 2.1.4 Complex views 2.2 Editing and Manipulation 2.2.1 Selection 2.2.2 Unconstrained input 2.2.3 Constrained input 2.3 User Assistance 2.3.1 User-driven information 2.3.2 System triggered notification 2.3.3 Disruptive messages 2.3.4 Help system 3 Presentation 3.1 Layout 3.2 Style 3.3 Text 4 Contributing 5 Index Structure Conceptual Model The conceptual model is the most fundamental aspect of the interface, describing the relationship between the interface and the outside world. The purpose of the conceptual model is to draw on the user’s past experiences so they can readily understand basic operations and accurately predict functionality. Real World, Vision Task Flow The task flow is concerned with the manner in which users’ complete specific operations with the system. In contrast to the conceptual model, the task flow is largely dependent on the product’s technical environment. Core usability goals, Use cases / User requirements, Task aggregation Personas, Scenarios, Usability criteria, Feature list Organizational Model The organizational model describes how the system’s content and functionality are ordered and categorized. Also known as the information architecture, the organizational model encompasses both the classification scheme as well as the model of association, hierarchy versus index for example. Terminology Information architecture, Interface management, Window style, Basic arrangement, Screen design, Design Pattern central configuration (content tbd.) Notification mechanism (content tbd.) Minimize to tray (perhaps at behaviour>navigation) Behaviour All HIGs assume that the controls referenced in the following "Implementation" sections are used. Therefore they only contain guidelines for aspects which can be changed by the developer, to keep them as concise as possible. If you feel your application needs something which the referenced standard KDE or Qt widget does not provide, do not create you own custom replacement, because it might violate best practice which is implemented in the standard widget. Instead, ask the KDE HIG team for advice on how to solve your specific problem. Viewing and Navigation The Viewing and Navigation layer encompasses the wide variety of behaviors and operations that allow users to navigate the interface and effect its presentation. General navigation Dialogs Accordion Tabs and Pages in Dialogs Toolbar Status bar Paging Access functions Menu Bar Buttons Toggle Buttons Links Keyboard Access Keyboard Accelerators Keyboard Shortcuts Grouping Group box, Panel Splitter Complex views Use a List View to show some items out of one category. Tree view Grids Editing and Manipulation The Editing and Manipulation layer contains the behaviors that result in permanent changes to user’s stored information. … Behaviors in this layer can often be recognized by the following traits: they result in permanent, stored changes; they require an implicit or explicit save operation; and they typically require validation of the input data. Selection Use a radio button for 1 of a few n selections. Use one or more check boxes for clear options or n of a few m selections. Use a list view for one or a few n of some m selections. Use a drop-down list for 1 of some n selection and a combo box if users should be able to add items. Use the dual list pattern for n of m selections. Unconstrained input To enter one line of text use a line edit and for multiple lines of texts a text edit. Consider to provide inline editing with complex views. Constrained input Use a Spin Box for numerical input within a range and with fix steps. Use a Slider for arbitrary changes within a defined range. (Under construction): Numeric input with both large changes and precise control: Slider and Spin Box Use Date and Time Pickers for formatted input of datum, time of day, or periods etc. User Assistance Interface elements that inform users of the application’s activity and status, as well as elements dedicated to user education, are all contained in the User Assistance layer. This includes online help, error alerts, and status alerts. User-driven information Provide tool-tips for user driven information. System triggered notification Provide a message panel to inform users about non-critical problems. Use a notification as system-triggered message to acknowledge about events out of the current context. Progress indicator Disruptive messages Message dialogs Help system KDE Help Presentation Layout The various design decisions governing the placement and ordering of onscreen elements are expressed in the Layout layer. In addition to providing an ordered visual flow, the Layout layer also supports the Behavior tier by arranging elements in a manner that helps communicate behavior, importance, and usage. Resizing Default and minimal size Spacing Alignment & Placement Forms: Label Alignment Color Icons Style Like many forms of visual design, the Style layer is concerned with emotion, tone, and visual vocabulary. Because it is the most visible and concrete aspect of an interface, it typically accounts for people’s first impression of a product. Paradoxically however, the ultimate effect of style on overall usability or user satisfaction is minimal. Text Contained within the Text layer are all the written, language-based elements of the interface. This includes the labels used to represent the organizational model, the names of the input and navigational controls contained in the Viewing and Navigation layer, and the alert messages and help text used by the User Assistance layer. Language localizations Static text Control Labels KNewStuff Button Labels Wording Ellipsis Capitalization Contractions (don't, there's, etc.) Exclamation Points See also: HIG for Plasma Active HIG for Plasma Netbook Contributing Didn't find what you were looking for? Our Human Interface Guidelines are a work in progress and we need your help. Visit the Contributing page to report problems or get involved. Index B Buttons C Capitalization Contractions (don't, there's, etc.) Check Box Combo Box D Date and Time Pickers Dialogs E Ellipsis Exclamation Points F Forms: Label Alignment K KNewStuff Button Labels Keyboard Accelerators Keyboard Shortcuts L Labels List Views M Menu Bar Messages R Radio Buttons S Slider Slider and Spin Box Spin Box T Tabs and Pages in Dialogs Toggle Buttons W Wording Legacy Stuff List Views Please add any guidelines questions or requests to the HIG Questions page. Also see the Season of Usability HIG & Design Patterns Workspace. Retrieved from "https://techbase.kde.org/index.php?title=Projects/Usability/HIG&oldid=80370" Category: Usability Content is available under Creative Commons License SA 4.0 unless otherwise noted.