Jump to content

Https://community.kde.org/Get Involved/design/HCI/Checklists/Configuration: Difference between revisions

From KDE Community Wiki
← Older edit
*>AnneW
No edit summary
Jucato (talk | contribs)
KDEDevelopers, Bureaucrats, Administrators, trusted
54 edits
 
(6 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Review|1=* The link in the first paragraph appears to be broken}}
{{Proposed_move_to_community|Archive under HIG, old HCI}}


1. Dialog navigation
1. Dialog navigation


* A [http://wiki.openusability.org/guidelines/index.php/Image:Grouping.png paged configuration dialog] should be used when there is more than one category of options.
* A paged configuration dialog should be used when there is more than one category of options.
* Tabs should be used as second-level navigation.
* Tabs should be used as second-level navigation.
* Tree views shouldn't be used in the paged dialog's sidebar.  
* Tree views shouldn't be used in the paged dialog's sidebar.  
Line 25: Line 25:
4. Wording
4. Wording


* Keywords used in page title and the label in the left navigation bar should correspond.  
* Keywords used in page title and the label in the left navigation bar should correspond. <br /><small>(for example, the page title may "Here you can personalize kopete"” while the label is "Behavior". This should be reported and the acceptable change would be Behavior -> "Here you can change the behavior of Kopete" OR Personalize -> "Here you can personalize Kopete")</small>
<small>(In [http://wiki.openusability.org/guidelines/index.php/Image:Grouping.png this example], page title is "Here you can personalize kopete"” while the label is "Behavior". This should be reported and acceptable change would be Behavior -> "Here you can change the behavior of Kopete" OR Personalize -> "Here you can personalize Kopete")</small>


* Obviously technical or otherwise hard to understand wording should be avoided.
* Obviously technical or otherwise hard to understand wording should be avoided.

Latest revision as of 10:11, 16 May 2019

Template:Proposed move to community

1. Dialog navigation

  • A paged configuration dialog should be used when there is more than one category of options.
  • Tabs should be used as second-level navigation.
  • Tree views shouldn't be used in the paged dialog's sidebar.


2. Grouping of options

  • The number of categories (pages) should be between 3 and 6.
  • The number of tabs on a page should be between 2 and 4.
  • The options should be in the visible space so the user doesn't need to scroll. (otherwise it's an indicator that options might be moved to advanced sections or dialogs)
  • There shouldn't be "orphaned options" - options which are not related to any other ones.


3. Dialog layout

  • The dialog should be resizable. (the latter is important for accessibility)
  • The overall size of the dialog shouldn't be bigger than 800x600.
  • The dialog should have scrollbars which appear when not all options are visible.


4. Wording

  • Keywords used in page title and the label in the left navigation bar should correspond.
    (for example, the page title may "Here you can personalize kopete"” while the label is "Behavior". This should be reported and the acceptable change would be Behavior -> "Here you can change the behavior of Kopete" OR Personalize -> "Here you can personalize Kopete")
  • Obviously technical or otherwise hard to understand wording should be avoided.
Retrieved from "https://community.kde.org/index.php?title=Https://community.kde.org/Get_Involved/design/HCI/Checklists/Configuration&oldid=84082"