Editing Legacy Maemo 5 Documentation/Human Interface Guidelines/Dialogs

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1: Line 1:
-
{{Legacy documentation}}
+
=Dialogs=
 +
Although derived from GtkDialog, Hildon dialogs behave differently than in a traditional desktop environment. To make them more usable, dialogs are placed at the bottom of the screen, with their buttons on the right side. Dialogs can be closed by pressing on the dimmed desktop background outside of the dialog itself.
-
{{main|Legacy Maemo 5 Documentation/Graphical UI Tutorial/Windows and dialogs#Dialogs}}
+
The number of dialog buttons should be kept to a minimum. Dialogs should not have a "close" or "cancel" button, since that task is accomplished by pressing the dimmed area outside of the dialog.
-
Although still created with a <code>GtkDialog</code>, Hildon dialogs are really different from the ones in a desktop environment. For a better usage, they are placed in the bottom of the screen and their buttons are placed on the right side. Dialogs can be closed by pressing the dimmed area that remains as the desktop background.
+
Dialogs should be used for quick tasks. For example, a dialog is appropriate for asking for a category name when creating a new category in an email application. In this example, there should be a Text Entry Field for users to enter the category name and a single button, "Create."
-
Keep the number of dialog buttons low. Dialogs should not have a cancel button, that task is accomplished by pressing the dimmed area.
+
[[Image:dialog.png|400px]]
-
Dialogs should be used for small tasks, for example, asking for a category name when creating a new category in an email client application. In this example, there should be an entry for the user to enter the category name and a button "Create".
+
''Figure 6: A dialog''
-
[[Image:dialog.png|frame|center|alt=Screenshot of a dialog|Figure 6: A dialog]]
 
-
For bigger tasks like managing an email account folder like "Inbox" (browsing through the messages, deleting, editing them, and so on), use a view, not a simple dialog.
+
For other tasks such as browsing through email messages, deleting or editing them, or managing an email account folder, a sub view should be used instead of a dialog.  
 +
 
==Wizard Dialogs==
==Wizard Dialogs==
 +
A Wizard is a dialog that divides a task into sequential steps. With this special-case dialog, a complex operation can be presented more simply to users. Therefore, do not use a Wizard unless you are sure it will simplify an action for the user. For example, in a situation where users must set a simple preference, a normal dialog should be enough. But, if users must complete a number of settings which are dependent on sequential input before the application will function properly, then the use of a Wizard is appropriate.
-
A wizard is a dialog that divides a certain task in sequential steps. With this special dialog, you can present a complex operation to the user in an easier and simpler way.
+
The first page of a Wizard is a "welcome page." Its title should be the Wizard's name followed by, "Welcome." Similarly, the title of the Wizard's last page is a the Wizard's name combined with, "Finished." The titles of intermediate pages should be a combination of the Wizard's name and the action to be completed on the page. The page's action is set in the Wizard's assigned Notebook.  
-
The first page of the wizard is a welcome page and its title is the wizard's name followed by "Welcome". Similarly, the title of the wizard's last page is the wizard's name combined with "Finished". The in-between pages' titles are a result of the combination of the wizard's name and that page's title in wizard's assigned notebook.
+
[[Image:wizard.png|400px]]
-
[[Image:Example wizard dialog.png|frame|center|alt=Screenshot of a wizard dialog|Figure 7: A wizard dialog]]
+
''Figure 7: An wizard dialog''
-
Wizards contain three buttons - Finish, Previous and Next - which are dimmed or undimmed automatically according to the current page of the wizard.
 
-
Because the first page is the welcome page, it should not have widgets that require user input (apart from the buttons) but instead tell the user what the wizard is there for. That information must suggest what to expect from the wizard's steps as well as what will happen when the wizard finishes. The last page must resume important choices made by the users along the pages and recall what will happen when they press the "Finish" button. Widgets that express important choices must not be added to the last page although simple choices, like showing a README file, can be added. The in-between pages are the ones where users should be asked to enter information or choose important/main choices. For these pages, explain by providing labels and captions what each requested information or choice is about.
+
Wizard dialogs contain three buttons: Finish, Previous, and Next. These buttons are automatically dimmed or undimmed according to the current page of the Wizard.
-
Remember, a wizard is supposed to make a task simpler, not the opposite. Hence, you should not use it unless you are sure you will simplify things for the user. For example, if the task is just to present some information and a couple of checkboxes for the user to set some preferences, use a normal dialog, not a wizard. On the other hand, if the user is requested to set a number of settings dependent on each other in a sequential way, use a wizard.
+
Since the first page is the welcome page, it should not require any user input, other than navigation buttons. Instead the page should tell the user what the Wizard is for. This information should describe what to expect from the Wizard, the steps that will follow, as well as what will happen once the Wizard is complete. The last page should summarise important choices made by the user as well as describe what will happen when the "Finish" button is pressed. Avoid asking for important choices on the last page of a Wizard (although simple choices, such as showing a README file, may be included). All important choices to be made, including data that users are required to enter, should be requested on the intermediate pages of the Wizard. Likewise, always explain (via labels and captions) the reason for the requested information or choices.

Learn more about Contributing to the wiki.


Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!


Cancel | Editing help (opens in new window)

Templates used on this page:

Retrieved from "http://wiki.maemo.org/Legacy_Maemo_5_Documentation/Human_Interface_Guidelines/Dialogs"