User Details
- User Since
- Sep 11 2015, 6:01 PM (505 w, 6 d)
- Availability
- Available
Mar 17 2016
The options are:
- Colored background (somewhat awkward)
- Colored frame (very common but maybe not obtrusively enough)
- Speech bubble (UX recommendation in the MS world)
- Notification/message panel (default for KDE but not in respect to a particular control)
Mar 16 2016
Despite from the phrasing the task meets the expectations. As I suggested in the other thread it makes sense to adjust the required number of characters to how many items the dropdown would have. Given a large list of email with
sender from AAA... to ZZZ and you type A it is of no use to show all senders.
And I suppose your dropdown list reduces further when it is open with every entered charcter (e.g. "receiver is F" ... "receiver is Franci"). Also it has to be possible to navigate through the list with cursor keys as well as home/end and to select an item with the mouse.
I would make the autocompletion dependent to the number of potential results. The dropdown must not contain of hunderts of items so you get it only when the target might be easy to find. In the example it's good with the first letter, but in case of more than 20 options (to name an arbitrary number) it's better to expand only when two or more charcters are entered (and to have an explicite way to show the list of options by pressing F2, for example), and finally for the AND/OR/NOT combinations you could expand immediately.
I'm not so sure if multiple ways to enter values support learnability. I mean when "John's emails from last two weeks" (cf. #T1453) or "John 08/15" and "Sender=John AND time>08/15" is all the same how are users supposed to learn it?
About this particular item, I wonder how to update the proposal later from for instance "Date>2016..." to ""Date<2016...".
And the idea to offer all operators might also lead to an usuable state. Take the example "receiver John Date 2016/03/18" and add more criteria to increase the complexity.
Feb 4 2016
Target: Query parser
Target: Query parser/Query generator dialog
Target: Query parser/Query generator dialog
Target: Query parser
Target: Query generator dialog
Target: Query generator dialog
Target: Query generator dialog
Target: Application (sidebar)
Target: Application