Projects/Usability/HIG/Tabs Pages: Difference between revisions

From KDE TechBase
< Projects‎ | Usability‎ | HIG
(New page: ==Tabs and Pages in Dialogs== '''General Guidelines''' If a control affects only one tab or page in the dialog, place it on that tab/page. If it affects every tab/page in the dialog, plac...)
 
No edit summary
Line 2: Line 2:


'''General Guidelines'''
'''General Guidelines'''
If a control affects only one tab or page in the dialog, place it on that tab/page. If it affects every tab/page in the dialog, place it outside, for example beside the window's OK and Cancel buttons.
If a control affects only one tab or page in the dialog, place it on that tab/page. If it affects every tab/page in the dialog, place it outside, for example beside the window's OK and Cancel buttons.


Make sure changes on one tab will not change options on another tab.
Make sure changes on one tab will not change options on another tab.


===Tabbed Dialogs===
===Tabbed Dialogs===


'''When to Use'''
'''When to Use'''
Use tabbed dialogs when you have a limited number of tabs (max. 6).
Use tabbed dialogs when you have a limited number of tabs (max. 6).
If you cannot see all the tabs without scrolling or splitting them into multiple rows, you are probably using too many and should use a paged dialog instead.
If you cannot see all the tabs without scrolling or splitting them into multiple rows, you are probably using too many and should use a paged dialog instead.


===Paged Dialogs===
===Paged Dialogs===


'''When to Use'''
'''When to Use'''
Always use paged dialogs for configuration dialogs - assuming that there is more than one section of options to be configured.
Always use paged dialogs for configuration dialogs - assuming that there is more than one section of options to be configured.
For other dialogs, use paged dialogs if there are too many tabs to put them into a tabbed dialog.
For other dialogs, use paged dialogs if there are too many tabs to put them into a tabbed dialog.


===Accessibility===
===Accessibility===
Do not assign accelerator keys to tab and paged dialog labels. Assign an access key to every other control on each page, however.
Do not assign accelerator keys to tab and paged dialog labels. Assign an access key to every other control on each page, however.


=== See Also ===
=== See Also ===
* [[Projects/Usability/HIG/Dialogs|Dialogs]]
* [[Projects/Usability/HIG/Dialogs|Dialogs]]

Revision as of 20:06, 11 August 2008

Tabs and Pages in Dialogs

General Guidelines

If a control affects only one tab or page in the dialog, place it on that tab/page. If it affects every tab/page in the dialog, place it outside, for example beside the window's OK and Cancel buttons.

Make sure changes on one tab will not change options on another tab.

Tabbed Dialogs

When to Use

Use tabbed dialogs when you have a limited number of tabs (max. 6). If you cannot see all the tabs without scrolling or splitting them into multiple rows, you are probably using too many and should use a paged dialog instead.

Paged Dialogs

When to Use

Always use paged dialogs for configuration dialogs - assuming that there is more than one section of options to be configured. For other dialogs, use paged dialogs if there are too many tabs to put them into a tabbed dialog.

Accessibility

Do not assign accelerator keys to tab and paged dialog labels. Assign an access key to every other control on each page, however.

See Also