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

< Projects‎ | Usability‎ | HIG
Jump to: navigation, search
(Implementation: added link to api docu)
 
(4 intermediate revisions by 2 users not shown)
Line 2: Line 2:
  
 
== Purpose ==
 
== Purpose ==
A ''balloon'' is a small pop-up window that informs users of a non-critical problem or special condition in a control. Balloons have an icon, a title, and body text, all of which are optional. Balloons are usually used with text boxes, or controls that use text boxes for changing values, such as combo boxes, list views, and tree views. Other kinds of controls are sufficiently well constrained, and don't need the additional feedback balloons afford.
+
A ''message panel'' is a small pop-up panel shown at top of the current form that informs users of a non-critical problem or special condition. The panel shows information on four levels indicated by different colors and icons, and provides standard action that users might want to initiate.
  
 
== Examples ==
 
== Examples ==
[[File:Balloon.png]]
 
  
 
== Guidelines ==
 
== Guidelines ==
* Use balloon in cases of non-critical problems that user can solve.
+
* Use message panel in cases of non-critical problems that user can solve.
 +
** Use ''positive feedback'' to notify about user-initiated processes, e.g. to indicate completion of background tasks
 +
** Use ''negative feedback''  (aka error) as a secondary indicator of failure, e.g. if a transaction was not completed successfully
 +
** in discussion: <font color="blue">Show the information on a warning level in case of relevant information that do not concern the current workflow, e.g. No Internet connection available.</font>
 +
** Use ''opportunistic interaction'' (aka notification) to acknowledge the user about options that he or she might be interested in, e.g. Remember password?
 
* Display the information immediately.
 
* Display the information immediately.
* Display only one balloon at a time.
+
*  Auto remove a message when the problem is resolved or special condition is removed.
(Auto-) Remove a balloon when  
+
* Do not auto remove the panel if users can't continue until the problem is resolved.
** the problem is resolved or special condition is removed,
+
* When users dismiss the panel, do not display any other UI or start any other side effect.
** the user enters valid data,
+
* Do not add additional controls to the message panel.
** it times out (by default after 10 seconds).
+
* Consider to show a [[Projects/Usability/HIG/Notifications|notification]] if Information does not concern the actual workflow.
* Remove the timeout if users can't continue until the problem is resolved.
+
* Display balloons below their owner control
+
* When users click a balloon, just dismiss the balloon without displaying any other UI or having any other side effect.
+
* Do not add additional controls to balloons.
+
  
 
== Implementation ==
 
== Implementation ==
 +
[http://api.kde.org/frameworks-api/frameworks5-apidocs/kwidgetsaddons/html/classKMessageWidget.html KMessageWidget]
 +
 +
cf. http://community.kde.org/Sprints/UX2011/KMessageWidget

Latest revision as of 08:41, 18 April 2014


[edit] Purpose

A message panel is a small pop-up panel shown at top of the current form that informs users of a non-critical problem or special condition. The panel shows information on four levels indicated by different colors and icons, and provides standard action that users might want to initiate.

[edit] Examples

[edit] Guidelines

  • Use message panel in cases of non-critical problems that user can solve.
    • Use positive feedback to notify about user-initiated processes, e.g. to indicate completion of background tasks
    • Use negative feedback (aka error) as a secondary indicator of failure, e.g. if a transaction was not completed successfully
    • in discussion: Show the information on a warning level in case of relevant information that do not concern the current workflow, e.g. No Internet connection available.
    • Use opportunistic interaction (aka notification) to acknowledge the user about options that he or she might be interested in, e.g. Remember password?
  • Display the information immediately.
  • Auto remove a message when the problem is resolved or special condition is removed.
  • Do not auto remove the panel if users can't continue until the problem is resolved.
  • When users dismiss the panel, do not display any other UI or start any other side effect.
  • Do not add additional controls to the message panel.
  • Consider to show a notification if Information does not concern the actual workflow.

[edit] Implementation

KMessageWidget

cf. http://community.kde.org/Sprints/UX2011/KMessageWidget


This page was last modified on 18 April 2014, at 08:41. This page has been accessed 1,690 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