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

< Projects‎ | Usability‎ | HIG
Jump to: navigation, search
(Guidelines)
m ([http://qt-project.org/doc/qt-4.8/qradiobutton.html QRadioButton] → {{qt|QRadioButton}})
(15 intermediate revisions by 3 users not shown)
Line 2: Line 2:
  
 
== Purpose ==
 
== Purpose ==
A list view is basically used to show some items. It offers orientation thereby and allows navigation without the need of other controls. Additionally, a list view may be used for single selection (users select one item from a list of mutually exclusive values) or multiple selection (selections in combination with the Shift key or Control key). However, because there is no common visual clue whether a list box’ mode is single or multiple and since other controls are more efficient for single selection, a list box should be used for single selection only.  
+
A ''list view'' is basically used to show some items. It offers orientation thereby and allows navigation without the need of other controls. Additionally, a list view may be used for single selection (users select one item from a list of mutually exclusive values) or multiple selection (selections in combination with the Shift key or Control key). However, because there is no common visual clue whether a list box’ mode is single or multiple and since other controls are more efficient for single selection, a list box should be used for single selection only.  
<span style="color:blue">HT: Recommendation should be checked</span>
+
== Example ==
 
+
 
== Guidelines ==
 
== Guidelines ==
=== Usage ===
+
=== Is this the right control ===
 
* Prefer a list view to show items that belong together and in case of sufficient space.  
 
* Prefer a list view to show items that belong together and in case of sufficient space.  
=== Appearance ===
 
* Alternate row color (use theme settings). Use different keys (e.g. page up/down) when more lists should be accessible.
 
* Enable browsing through list by cursor up/down.
 
* Do not have blank list items; use meta-options, e.g. (None) instead.
 
* Place options that represent general options (e.g. All, None) at the beginning of the list.
 
* Sort list items in a logical order. Make sure sorting fits translation.
 
* For lists with more than one column view headers and enable sorting by clicking the header. Show sort order in header.
 
 
=== Selection ===
 
<span style="color:blue">Check the following against recommendation</span>
 
 
* Use the list view for selection if it is easy for users to know which items are checked at any given time, for one or more of these reasons:
 
* Use the list view for selection if it is easy for users to know which items are checked at any given time, for one or more of these reasons:
 
** There are no more than twice the number of options then are visible at a time
 
** There are no more than twice the number of options then are visible at a time
 
** The options are well-known (for example months of a year or days of a week)
 
** The options are well-known (for example months of a year or days of a week)
 
** Usually the selected options are close to each other in the list
 
** Usually the selected options are close to each other in the list
<span style="color:blue">Choose a) or b)</span>
+
* Do ''not'' provide extended multiple selection with Shift+Click or Ctrl+Click to select groups of contiguous or non-adjacent values, respectively. Instead, use the [[Projects/Usability/HIG/DualList| dual-list pattern]] if multiple items have to be selected, because it allows users to easily see which items are selected at any point, without having to scroll through the available options, and it can be used with only the mouse. (Once the list view is being revised this guideline is subject of change.)
a) * In any other case, use the dual-list pattern because it allows users to easily see which items are selected at any point, without having to scroll through the available options
+
 
b) * Use a list box for multiple selections with more than five options.
+
=== Behavior ===
* Provide extended multiple selection with Shift+Click or Ctrl+Click to select groups of contiguous or non-adjacent values, respectively.
+
* Do not have blank list items; use meta-options, e.g. (None) instead.
<span style="color:blue">Make sure that KCB is feasonable</span>
+
* Place options that represent general options (e.g. All, None) at the beginning of the list.
 +
* Sort list items in a logical order. Make sure sorting fits translation.
 +
* For lists with more than one column view, show headers and enable sorting by clicking the header. Show sort order in header.
 +
 
 +
===  Appearance ===
 +
* Alternate row color (use theme settings). Use different keys (e.g. page up/down) when more lists should be accessible.
 +
* Make the list control large enough that it can show at least four items at a time without scrolling.
 +
* If the list appears in a dialog or utility window, consider making the window and the list within it resizeable so that the user can choose how many list items are visible at a time without scrolling. Each time the user opens this dialog, set its dimensions to those that the user last resized it to.
 +
* If activating a choice affects the appearance or the enabled state of other controls, place them next to the list view.
 +
* If certain controls in a dialog are only relevant if a certain item is selected (i.e. they are dependent controls), disable them instead of hiding.
 +
* Label the list view with a descriptive caption to the top left (cf. [[Projects/Usability/HIG/Alignment| alignment]]).
 +
* Create a buddy relation so access keys are assigned.
 +
* Do not use ending punctuation (neither dot nor colon) for caption.
 +
* Use [[Projects/Usability/HIG/Capitalization|sentence style capitalization]] for list view items.
  
* Add 'KCheckBoxes' to list items.  
+
== Implementation ==
- KCB are flat (no frame, no shadow, no bevel) for clear differentiation from normal check boxes.
+
* {{qt|QListView}}, for single-column lists.
- KCB are hidden by default, that means when no list item is selected.
+
* {{qt|QTreeView}}, for multi-column lists. Be sure to set the [http://qt-project.org/doc/qt-4.8/qtreeview.html#rootIsDecorated-prop rootIsDecorated property] to false if the items in your list do not have children.
- KCB have a fade-in effect on mouse over to introduce themselves to users.
+
- KCB are transparent and therby clearly part of the list item.
+
- Legacy keyboard use applies to KCB as well. Thus, the whole item can be clicked to toggle option.
+
  
== Code snippets ==
+
[[Category:Usability]][[Category:Behavior]][[Category:Editing_and_Manipulation]][[Category:Selection]]

Revision as of 22:05, 3 August 2013


Purpose

A list view is basically used to show some items. It offers orientation thereby and allows navigation without the need of other controls. Additionally, a list view may be used for single selection (users select one item from a list of mutually exclusive values) or multiple selection (selections in combination with the Shift key or Control key). However, because there is no common visual clue whether a list box’ mode is single or multiple and since other controls are more efficient for single selection, a list box should be used for single selection only.

Example

Guidelines

Is this the right control

  • Prefer a list view to show items that belong together and in case of sufficient space.
  • Use the list view for selection if it is easy for users to know which items are checked at any given time, for one or more of these reasons:
    • There are no more than twice the number of options then are visible at a time
    • The options are well-known (for example months of a year or days of a week)
    • Usually the selected options are close to each other in the list
  • Do not provide extended multiple selection with Shift+Click or Ctrl+Click to select groups of contiguous or non-adjacent values, respectively. Instead, use the dual-list pattern if multiple items have to be selected, because it allows users to easily see which items are selected at any point, without having to scroll through the available options, and it can be used with only the mouse. (Once the list view is being revised this guideline is subject of change.)

Behavior

  • Do not have blank list items; use meta-options, e.g. (None) instead.
  • Place options that represent general options (e.g. All, None) at the beginning of the list.
  • Sort list items in a logical order. Make sure sorting fits translation.
  • For lists with more than one column view, show headers and enable sorting by clicking the header. Show sort order in header.

Appearance

  • Alternate row color (use theme settings). Use different keys (e.g. page up/down) when more lists should be accessible.
  • Make the list control large enough that it can show at least four items at a time without scrolling.
  • If the list appears in a dialog or utility window, consider making the window and the list within it resizeable so that the user can choose how many list items are visible at a time without scrolling. Each time the user opens this dialog, set its dimensions to those that the user last resized it to.
  • If activating a choice affects the appearance or the enabled state of other controls, place them next to the list view.
  • If certain controls in a dialog are only relevant if a certain item is selected (i.e. they are dependent controls), disable them instead of hiding.
  • Label the list view with a descriptive caption to the top left (cf. alignment).
  • Create a buddy relation so access keys are assigned.
  • Do not use ending punctuation (neither dot nor colon) for caption.
  • Use sentence style capitalization for list view items.

Implementation


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal