Projects/Usability/HIG/Dialogs: Difference between revisions

Revision as of 16:17, 19 June 2013

Reduce the dialog flood

Do not nest dialogs more than two levels deep.
For example "Configuration dialog > Advanced dialog" is ok, "Configuration dialog > Advanced dialog > Further settings dialog" is too deep.
Avoid dialogs that contain only one or two options. If possible, use inline-editing instead.
Do not use dialogs to display non-critical messages which do not require any further user interaction (typically dialogs with a single "OK" or "Close" button). Use info panels instead.

Position of dialogs

Always keep dialogs on top of their parent.
This is usually taken care of by the window manager. But in composed applications, focus problems may occur. Check carefully in this case.
If reference in the parent window is required, make sure your dialog does not cover relevant parts.
For example a find dialog should neither be centered, nor cover a search result.

Interaction

Avoid modal dialogs

Use modal dialogs only if allowing interaction with other parts of the application while the window is opened could cause data loss or some other serious problem.
Provide a clear way of leaving the modal dialog, such as a Cancel button.

Dialogs should not be bigger than 800x600 pixels and should always be resizable
Make sure there is at least one third white space, do not overload the panel.
The reading direction in dialogs is left to right, top to bottom.
Dialogs are grouped in meaningful sections. The actions are grouped along their context of use, not along technical relations.
Each section has a title.
Labels are right-aligned, input widgets are left aligned.
Provide one or two major vertical axis in your dialog that guide the user's attention.
The vertical line where the right aligned labels and the left aligned input widgets meet is one such example.
Widgets which are subordinate to another widget are indented. If their enabled state depends on the parent widget, create an appropriate slot.

Otherwise, follow the guidelines described in Form: Label Alignment

@@ Line 4: / Line 4: @@
 * Avoid dialogs that contain only one or two options. If possible, use [[Design_and_Layout:Interaction:Input#Inline Editing|inline-editing]] instead.
 * Do not use dialogs to display non-critical messages which do not require any further user interaction (typically dialogs with a single "OK" or "Close" button). Use [[Guidelines:Info Panel|info panels]] instead.
 '''Position of dialogs'''
 * Always keep dialogs on top of their parent. <br><small>This is usually taken care of by the window manager. But in composed applications, focus problems may occur. Check carefully in this case.</small>
 * If reference in the parent window is required, make sure your dialog does not cover relevant parts. <br><small>For example a find dialog should neither be centered, nor cover a search result.</small>
 '''Interaction'''
 * Set input focus on confirmation button.
+'''Avoid modal dialogs'''
-'''Only use modal dialogs when''':
+* Use modal dialogs only if allowing interaction with other parts of the application while the window is opened could cause data loss or some other serious problem.
-* Use modal dialogs only if allowing interaction with other parts of the application while the window is open could cause data loss or some other serious problem.
+* Provide a clear way of leaving the modal dialog, such as a Cancel button.
-Provide a clear way of leaving the modal dialog, such as a Cancel button in an alert.
 == Dialog Layout ==