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 ==

== Viewing and Navigation ==

<cite>The Viewing and Navigation layer encompasses the wide variety of behaviors and operations that allow users to navigate the interface and effect its presentation. </cite>

<cite>The Viewing and Navigation layer encompasses the wide variety of behaviors and operations that allow users to navigate the interface and effect its presentation. </cite>

Line 36:

Line 40:

* Splitter

* Splitter

=== Complex views ===

=== Complex views ===

−

* [[Projects/Usability/HIG/Lists_Rich_Lists|List Views]]

+

* Use a [[Projects/Usability/HIG/ListView| List View]] to show some items out of one category.

* Tree view

* Tree view

* Grids

* Grids

+

* If you really need to create your own widget follow the guidelines for [[Projects/Usability/HIG/CustomControls| custom controls]].

+

== Editing and Manipulation ==

== Editing and Manipulation ==

<cite>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. </cite>

<cite>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. </cite>

Line 45:

Line 51:

* Use one or more [[Projects/Usability/HIG/Check_Box|check boxes]] for clear options or n of a few m selections.

* Use one or more [[Projects/Usability/HIG/Check_Box|check boxes]] for clear options or n of a few m selections.

* Use a [[Projects/Usability/HIG/ListView|list view]] for one or a few n of some m selections.

* Use a [[Projects/Usability/HIG/ListView|list view]] for one or a few n of some m selections.

* Use a [[Projects/Usability/HIG/Slider|Slider]] for arbitrary changes within a defined range.

−

* [[Projects/Usability/HIG/Date_Time|Date- and Time-Picker]]

+

* (Under construction): Numeric input with both large changes and precise control: [[Projects/Usability/HIG/Slider_and_Spin_Box|Slider and Spin Box]]

+

* Use [[Projects/Usability/HIG/Date_Time_Pickers|Date and Time Pickers]] for formatted input of datum, time of day, or periods etc.

+

== User Assistance ==

== User Assistance ==

<cite>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. </cite>

<cite>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. </cite>

* Do not use [[Projects/Usability/HIG/Color| color]] as primary method of communication.

* Icons

* Icons

+

== Style ==

== Style ==

<cite>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.</cite>

<cite>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.</cite>

Line 103:

Line 114:

Didn't find what you were looking for?

Didn't find what you were looking for?

−

Our Human Interface Guidelines are a work in progress and we need your help. If you found an area that was unclear or is not even covered in our HIG, tell us about it. You'll find everything you need on our mailing list: [mailto:kde-guidelines@kde.org kde-guidelines@kde.org] or in [http://techbase.kde.org/Projects/Usability/HIG/UI_Files our little tutorial].

+

Our Human Interface Guidelines are a work in progress and we need your help. Visit the [[Projects/Usability/HIG/Contributing|Contributing page]] to report problems or get involved.

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.

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.

Grouping

Complex views

If you really need to create your own widget follow the guidelines for custom controls.

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.

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.

Disruptive messages

Help system

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.

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.