Projects/Usability/HIG/StatusBar: Difference between revisions

From KDE TechBase
< Projects‎ | Usability‎ | HIG
No edit summary
Line 2: Line 2:


== Purpose ==
== Purpose ==
A ''status bar'' is an area at the bottom of a primary window that displays information about the current window's state, background tasks, or other contextual information.
A ''status bar'' is an area at the bottom of a primary window that displays information about the current window's state, background tasks, or other contextual information. The status bar ‘frames’ the form and, thereby, has a white-space function which is part of the operating system or desktop environment branding. Because secondary forms like dialog boxes must not use a status bar it denotes a form as primary window too.  


The status bar ‘frames’ the form and, thereby, has a white-space function which is part of the operating system or desktop environment branding . Because secondary forms like dialog boxes must not use a status bar it denotes a form as primary window too.
KDE applications should not use a conventional status bar by default to maximize the space for content <ref>http://user-prompt.com/what-is-a-status-bar-good-for/</ref>.


== Examples ==
== Examples ==
Line 10: Line 10:
== Guidelines ==
== Guidelines ==
=== Is this the right control ===
=== Is this the right control ===
* Provide a status bar in the main window of every standard application.
* Omit the status bar in the main window to maximize vertical space for content.
** Do not show meaningless information like 'Ready'.
** Use a floating panel or [[Projects/Usability/HIG/Tooltip| tool-tips]] for short-term status information like full length text of links.
** Move controls to the toolbar.
* Do not display a status bar in secondary or internal windows.
* Do not display a status bar in secondary or internal windows.
* If a status bar is really necessary in your application consider to use a [[Projects/Usability/HIG/Toolbar| toolbar]] with all customization features.
===  Behavior ===
===  Behavior ===
* Do not use status bars for crucial information. Users should never have to know what is in the status bar. Otherwise consider to use [[Projects/Usability/HIG/Tooltip| tool-tips]] or a [[Projects/Usability/HIG/MessageWidget|message panel]].
* Do not use the status bars or any kind of replacement for crucial information. Users should never have to know what is in the status bar.
* Do not use the status bar to display advisory messages in place of standard [[Projects/Usability/HIG/Tooltip|tool-tips]].
* Do not use the status bar or any kind of replacement to display advisory messages in place of standard [[Projects/Usability/HIG/Tooltip|tool-tips]].
* Consider to make status bar areas interactive, e.g. with a slider to zoom content. The interaction with controls placed within the status bar is a convenience feature and must not be the only way to execute an action.
* Keep the status information plain; e.g. do not add icons.
* Do not hide the status bars by default. If configurable, users should easily be able to make it viewable again.
===  Appearance ===


===  Appearance ===
* When different information are shown the content of a status bar should be structured in panels.
* Keep the status bar plain; do not add icons.
==  Implementation ==
==  Implementation ==
==  References ==
<references>


[[Category:Usability]][[Category:Behavior]][[Category:Viewing_and_Navigation]][[Category:Access_functions]]
[[Category:Usability]][[Category:Behavior]][[Category:Viewing_and_Navigation]][[Category:Access_functions]]

Revision as of 11:04, 4 November 2013


Purpose

A status bar is an area at the bottom of a primary window that displays information about the current window's state, background tasks, or other contextual information. The status bar ‘frames’ the form and, thereby, has a white-space function which is part of the operating system or desktop environment branding. Because secondary forms like dialog boxes must not use a status bar it denotes a form as primary window too.

KDE applications should not use a conventional status bar by default to maximize the space for content [1].

Examples

Guidelines

Is this the right control

  • Omit the status bar in the main window to maximize vertical space for content.
    • Do not show meaningless information like 'Ready'.
    • Use a floating panel or tool-tips for short-term status information like full length text of links.
    • Move controls to the toolbar.
  • Do not display a status bar in secondary or internal windows.
  • If a status bar is really necessary in your application consider to use a toolbar with all customization features.

Behavior

  • Do not use the status bars or any kind of replacement for crucial information. Users should never have to know what is in the status bar.
  • Do not use the status bar or any kind of replacement to display advisory messages in place of standard tool-tips.
  • Keep the status information plain; e.g. do not add icons.

Appearance

Implementation

References

<references>