|
Ampa
|
 |
« on: September 03, 2009, 09:02:18 AM » |
|
Have been learning a lot from the 30 more days of screencasts and had a thought or two...
1. the +sall keyword is actually quite long! (5 whole extra characters) Maybe there is a shorter alternative?
++ came to mind as it is short, simply uses the same key twice, and has nice incremental associations. But the + key is slightly off the beaten track for those of us whose touch typing is a little erratic. Tab is handily placed but probably breaks alsorts of GUI traditions, so is probably not the solution.
2. user defined keywords also tend to be long (so that they are memorable) so perhaps they could auto-complete?
I hit the + key and then start by typing "m" and FARR scans the list of keywords, finds "+music" so suggests it. I can then hit tab or enter to accept it - what ever the usual method of acceptance is with such things!
Thoughts?
|
|
|
|
|
Logged
|
|
|
|
|
Josh
|
|
« Reply #1 on: September 03, 2009, 09:11:55 AM » |
|
The ++ modifier is a great idea. That gets +1 vote from me
|
|
|
|
|
Logged
|
Strength in Knowledge
|
|
|
|
|
|
|
skajfes
|
|
« Reply #3 on: September 03, 2009, 09:23:09 AM » |
|
The ++ modifier is a great idea. That gets +1 vote from me
Except that the ++ modifier is used to pass arguments to the resuts... |
|
|
|
|
Logged
|
It is impossible to make anything foolproof because fools are so ingenious.
|
|
|
|
phitsc
|
|
« Reply #4 on: September 03, 2009, 09:34:57 AM » |
|
I'd prefer a solution that does not change the FARR input box to switch between normal / extended result list like for example a keyboard shortcut. And use up/down to scroll through the results as was once suggested by justice. |
|
|
|
|
Logged
|
|
|
|
|
skajfes
|
|
« Reply #5 on: September 03, 2009, 04:08:40 PM » |
|
I'd prefer a solution that does not change the FARR input box to switch between normal / extended result list like for example a keyboard shortcut. And use up/down to scroll through the results as was once suggested by justice. That was a great idea. I wonder what happened with that? |
|
|
|
|
Logged
|
It is impossible to make anything foolproof because fools are so ingenious.
|
|
|
|
Ampa
|
|
« Reply #6 on: September 03, 2009, 04:13:31 PM » |
|
+1 for Justice's idea!
Anybody got any comments about the auto-completion of keywords suggestion?
|
|
|
|
|
Logged
|
|
|
|
|
Nod5
|
|
« Reply #7 on: September 04, 2009, 05:59:45 AM » |
|
Ampa: I for one have no need for that. I just use short keywords/aliases instead. m for music, b for books and so on.
In Justice's thread Mouser considers adding one more result that when clicked expands to show all. If made, I hope it becomes optional. It wastes screen space since the number of matches is enough indication. If the list looks "full" then there's probably more results to be had through "+sall", if the lists is short then there isn't.
I have no problem with expanding when pressing "down" at the bottom of the list but the hotkey alternative is still much quicker, isn't it?
|
|
|
|
« Last Edit: September 04, 2009, 06:04:01 AM by Nod5 »
|
Logged
|
|
|
|
|
mouser
|
|
« Reply #8 on: September 04, 2009, 08:33:26 AM » |
|
i agree that we need a faster way to show all. ++ would have made the most sense until i made it be the way you specify commandline arguements  maybe if we did it like this: pgdn in result view will show all, and then subsequent presses will page through the multiple-pages of results? |
|
|
|
|
Logged
|
|
|
|
|
phitsc
|
|
« Reply #9 on: September 04, 2009, 09:24:12 AM » |
|
i agree that we need a faster way to show all. ++ would have made the most sense until i made it be the way you specify commandline arguements maybe if we did it like this: pgdn in result view will show all, and then subsequent presses will page through the multiple-pages of results? I just want to state again that I think it would be better to have a way to switch to extended result list that doesn't change the input box. Changing the input box triggers a re-search (I'm thinking plugins by the way). |
|
|
|
|
Logged
|
|
|
|
|
nitrix-ud
|
|
« Reply #10 on: September 04, 2009, 09:36:41 AM » |
|
pgdn in result view will show all, and then subsequent presses will page through the multiple-pages of results?
that would be perfect |
|
|
|
|
Logged
|
|
|
|
|
Ampa
|
|
« Reply #11 on: September 04, 2009, 10:43:03 AM » |
|
PageDown sounds good to me - is quick, doesn't mean entering anything in the search box, and perhaps could be prompted in the status bar ("Press Page Down to see more results…")
|
|
|
|
|
Logged
|
|
|
|
|
Nod5
|
|
« Reply #12 on: September 04, 2009, 12:12:52 PM » |
|
pgdn in result view will show all, and then subsequent presses will page through the multiple-pages of results?
pgdn already has a function in result view: it jumps to the last item. How about keeping that and show all only on pgdn/down while at the last item? Also, Pgdn presently lacks a use in the inputbox. Why not then let pgdn in the inputbox trigger show all? That's one step, compared to two (down + pgdn) or three (down + pgdn + pgdn). |
|
|
|
|
Logged
|
|
|
|
|
mouser
|
|
« Reply #13 on: September 04, 2009, 01:21:35 PM » |
|
Why not then let pgdn in the inputbox trigger show all? sorry -- that is what i meant. and then as you say we can make down arrow and pgdown when on the last item and in the result area, do showall. |
|
|
|
|
Logged
|
|
|
|
|
