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

< Projects‎ | Usability‎ | HIG
Jump to: navigation, search
(Purpose)
Line 12: Line 12:
  
 
== Guidelines ==
 
== Guidelines ==
* Make the search result persistent. Users must not need to research after selecting or referencing an item.
+
=== Input ===
 
* Consider to allow iterative search on result lists.
 
* Consider to allow iterative search on result lists.
 
* Do not inherit artificial intelligence from users. Search operations have always be clear and comprehensible to users.
 
* Do not inherit artificial intelligence from users. Search operations have always be clear and comprehensible to users.
* Follow the guidelines on [[Projects/Usability/HIG/ProgressIndicator|delayed operations]] if the search takes longer.
 
* Provide paging/scrolling of results.
 
* Provide auto complete feature to the input based on previous operations.
 
 
* Start the search process via button or when the user pressed enter.
 
* Start the search process via button or when the user pressed enter.
* Show the search pattern at the header of the result list (e.g. "Search results for: <Hello World>")
 
 
* Show hints on how to use the search effectively.
 
* Show hints on how to use the search effectively.
 
* Do case insensitive search, unless its important.
 
* Do case insensitive search, unless its important.
 
* Make the search box large enough to show at least 20 characters (at the moment: KRunner & Kicker = 24, Konqueror = 54, KCM = 33, cf. ).
 
* Make the search box large enough to show at least 20 characters (at the moment: KRunner & Kicker = 24, Konqueror = 54, KCM = 33, cf. ).
 
* Run a combined AND search when two words have been entered unless the term is quoted (e.g. Hello World vs "Hello World")
 
* Run a combined AND search when two words have been entered unless the term is quoted (e.g. Hello World vs "Hello World")
 
+
+ Wildcards
 +
=== Output ===
 +
* Make the search result persistent. Users must not need to research after selecting or referencing an item.
 +
* Follow the guidelines on [[Projects/Usability/HIG/ProgressIndicator|delayed operations]] if the search takes longer.
 +
* Provide paging/scrolling of results.
 +
* Provide auto complete feature to the input based on previous operations.
 +
* Show the search pattern at the header of the result list (e.g. "Search results for: <Hello World>")
 
== Appearance ==
 
== Appearance ==
 +
=== Input ===
 
* Search input consists of an icon, a line input to enter the search pattern, and a button to start the search. (VDG could make a proposal how it looks nice)
 
* Search input consists of an icon, a line input to enter the search pattern, and a button to start the search. (VDG could make a proposal how it looks nice)
 
* ''Placement''
 
* ''Placement''
Line 37: Line 40:
 
** Active the control and focus it on Ctrl+F or when user clicks the icon.
 
** Active the control and focus it on Ctrl+F or when user clicks the icon.
 
** Do not use search icon anywhere else.
 
** Do not use search icon anywhere else.
 +
=== Output ===
 
* ''How to present results'' (Depends on use case?)
 
* ''How to present results'' (Depends on use case?)
 
** Highlight search results (KCM mode).
 
** Highlight search results (KCM mode).

Revision as of 11:12, 26 March 2014

Under construction.png
 
Under Construction
This is a new page, currently under construction!

Ref's:

Purpose

A search function allows to generate a subset out of a big number of items on ground of a user defined pattern. The function is essential to find matching items in case of a extended list or if the position of target(s) is unknown, as well as when bulk operations should be executed to a subset. A search operation interrupts the 'predefined workflow' and bypass core functions to a user-defined data set.

Supplemental to search is the filter function which rather reduces a given number of items than generating an output.

Guidelines

Input

  • Consider to allow iterative search on result lists.
  • Do not inherit artificial intelligence from users. Search operations have always be clear and comprehensible to users.
  • Start the search process via button or when the user pressed enter.
  • Show hints on how to use the search effectively.
  • Do case insensitive search, unless its important.
  • Make the search box large enough to show at least 20 characters (at the moment: KRunner & Kicker = 24, Konqueror = 54, KCM = 33, cf. ).
  • Run a combined AND search when two words have been entered unless the term is quoted (e.g. Hello World vs "Hello World")

+ Wildcards

Output

  • Make the search result persistent. Users must not need to research after selecting or referencing an item.
  • Follow the guidelines on delayed operations if the search takes longer.
  • Provide paging/scrolling of results.
  • Provide auto complete feature to the input based on previous operations.
  • Show the search pattern at the header of the result list (e.g. "Search results for: <Hello World>")

Appearance

Input

  • Search input consists of an icon, a line input to enter the search pattern, and a button to start the search. (VDG could make a proposal how it looks nice)
  • Placement
    • Start search at the upper right area of your dialog (KCM and web style).
    • Start search at the lower left area of your dialog (Kicker and Konqueror style).
    • Show search centered in the upper area of your dialog (Dolphin and KRunner style).
  • To show or not to show:
    • Always show search input. Do not hide the availability from users.
    • Show input control only when users start the search.
    • Hide the control in case the search is not the primary function of the app, but show a small button which indicates clearly the availability of the function.
    • Active the control and focus it on Ctrl+F or when user clicks the icon.
    • Do not use search icon anywhere else.

Output

  • How to present results (Depends on use case?)
    • Highlight search results (KCM mode).
    • Hide non-matching results (Kicker mode).
    • Generate a new list that matches the search pattern (KRunner mode).

Best Practice


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