Difference between revisions of "Projects/Usability/HIG/StatusBar"

< Projects‎ | Usability‎ | HIG
Jump to: navigation, search
(Purpose)
(Behavior)
Line 13: Line 13:
 
* 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 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 bar to display advisory messages in place of standard [[Projects/Usability/HIG/Tooltip|tool-tips]].
 
* Do not use the status bar to display advisory messages in place of standard [[Projects/Usability/HIG/Tooltip|tool-tips]].
* Do not make a status bar area interactive in standard applications. because those features are difficult to understand for non-experts.
+
* 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.
 
* Do not hide the status bars by default. If configurable, users should easily be able to make it viewable again.
 
* Do not hide the status bars by default. If configurable, users should easily be able to make it viewable again.
  

Revision as of 14:29, 25 October 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.

Examples

Guidelines

Is this the right control

  • Provide a status bar in the main window of every standard application.
  • Do not display a status bar in secondary or internal windows.

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 tool-tips or a message panel.
  • Do not use the status bar to display advisory messages in place of standard 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.
  • Do not hide the status bars by default. If configurable, users should easily be able to make it viewable again.

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


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal