[kde-guidelines] HIG for search needed (?)

[Heiko Tietze]

On Thursday 06 March 2014, 15:23:06 Thomas Pfeiffer wrote:
> Do you guys agree that such an HIG is necessary? If so, I think we
> should first decide whether KDE should stick to always visible search
> fields or switch to hidden ones, then I can start writing the guideline
> (unless Heiko would like to step up to do it ;) ).
Yes, of course it is part of the HIG. Actually there are some placeholders 
below organizational model yet: Central configuration, Notification mechanism, 
Minimize to tray, Processing of passwords.

I would call this "search" a filter because the result list is completely known 
and becomes limited by the operation. I use "search" in case of generating a 
potentially huge list on ground of some strings or the like. 

Visible or not can be extended to "highlighted" (as in the KCM), and sorted or 
separated or selected, to be creative, Personally, I like the highlighting, 
but it works not well for trees and hidden stuff like menus. Dolphin search 
works like kickoff and switches from standard view to some result list, kmail 
and konqueror selects the first occurrence on search. So an answer is not that 
easy.