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

< Projects‎ | Usability‎ | HIG
Jump to: navigation, search
(Created page with "__NOTOC__ == Purpose == A ''status bar'' is an area at the bottom of a primary window that displays information about the current window's state (such as what is being viewed...")
 
(Is this the right control)
 
(7 intermediate revisions by one user not shown)
Line 1: Line 1:
 +
{{Construction}}
 
__NOTOC__
 
__NOTOC__
  
 
== Purpose ==
 
== Purpose ==
A ''status bar'' is an area at the bottom of a primary window that displays information about the current window's state (such as what is being viewed and how), background tasks (such as printing, scanning, and formatting), or other contextual information (e.g. selection, keyboard state, etc.).
+
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.  
 +
 
 +
KDE applications should not use a conventional status bar by default in favor of maximized space for content <ref>http://user-prompt.com/what-is-a-status-bar-good-for/</ref>.
  
 
== Examples ==
 
== Examples ==
Line 8: Line 11:
 
== 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.
 +
** If you cannot find good replacements for status bar functions, please ask the [mailto:kde-usability@kde.org usability team] for support.
 
* 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.
+
* 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]].
* Do not make a status bar area interactive in standard applications. because those features are difficult to understand for non-experts.
+
* Keep the status information plain; e.g. do not add icons.
 
===  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]]

Latest revision as of 15:23, 6 November 2013

Under construction.png
 
Under Construction
This is a new page, currently under construction!


[edit] 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.

KDE applications should not use a conventional status bar by default in favor of maximized space for content [1].

[edit] Examples

[edit] Guidelines

[edit] 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.
    • If you cannot find good replacements for status bar functions, please ask the usability team for support.
  • 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.

[edit] 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.

[edit] Appearance

[edit] Implementation

[edit] References

  1. http://user-prompt.com/what-is-a-status-bar-good-for/

This page was last modified on 6 November 2013, at 15:23. This page has been accessed 895 times. Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2.
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal