Messages - jukla [ switch to compact view ]

Pages: prev1 [2]
6
nitrix-ud,

Both your examples seem to involve narrowing FARR's search to only look for a specific type of file and/or in a specific folder. That's what I meant by filters above (and wanted to snap on/off through hotkeys). So in fact we agree that that'd be a good feature!  :Thmbsup:

But Mouser's Case Two explicitly involved a user having an action, rather than a file of a certain type, in mind. But maybe I'm just getting stuck in the semantics here - maybe he was really thinking of something similar to your examples. In that case we ALL agree.   8)

Cheers

7
Mouser,
All my FARR-use so far falls under Case One. I don't even understand when Case Two would apply. Can you give an example of such a case?

(The only thing I can think of would be a case where a user is not sure what exactly he's looking for, thus choosing for example only action "edit image" which then filters the search to only include editable images. But that could be had more directly through a filter for image file types.)

I find that 99% of the target files for my searches are for one of these file type categories (in the order given):
text (txt, pdf, doc ...)
application/script (exe, bat, vbs ...)
image (png, jpg, gif ...)
music (mp3...)

If many other users use of FARR also fall into a few categories like that, then filters of the kind I described above would be ideal.

BTW, It would be interesting with a poll on what kinds of searches FARR-users actually do!


8
jukla i hope you will stick around for the v2 discussions..
Will do!  :Thmbsup:

[...] and i'm understanding some but not all

He he, I guess I got a bit carried away. If you point out what you find most incomprehensible I'll try to clarify (I might also just worsen things though!  :D

I combined three ideas - filters, actions and the L shaped Hotkey help in the GUI - but I guess they could be used separately (or combined with some other solutions) too.

The more I think about it (not that much but anyway...), the more convinced I become that something like the idea of the the L shaped hotkey help would solve a major problem with many small applications: users forgetting what all the hotkeys are and what they do.

9
Hi,
Thanks for the welcoming!  :) And for refs to FARR v2 threads. I guess I mostly rehashed thoughts already discussed.  :-[ Anyway, browsing through the threads on actions and filters stimulated me (well that and the fact that I immediately liked FARR's simplicity a whole lot) to elaborate my suggestion a bit more. So here's req 3 & 4 revisited.

My aim was a solution for users that only need 1-3 special filters and (mostly) 1-3 special actions for each file category.

STRUCTURE & SETTINGS -------------------
Shift, Ctrl & Alt are MODKEYS (not changeable)

On some settings page, let users set
- CATEGORIES = files/folders grouped through some property (basic: file extension(s), max/min size, older/newer than date x, folder. Advanced: combos of properties, arrays of (different) combos ...)
- 1-3 FILTERS (defined via categories)
- ACTIONS = copy path; kill; edit; do checksum ...

- Let users tie each FILTER to a MODKEY
- Let users tie 1-3 ACTIONS to each CATEGORY (advanced: even more actions)

- For alternative 1 (below): also tie MODKEY 1-3 to ACTION 1-3 for each CATEGORY

(Presets/templates would simplify all these settings of course.)


OPERATION -------------------

When focus is on search field
[input]      >>> [result]         
--------------------------------------------------------------------------------
type text      >>> do default search
enter/F2/F3...   >>> do default action on result1/2/3...                 
tab/arrow down   >>> stop search & focus result1      


hold modkey1/2/3 (during/after type)  >>> run filtered search 1/2/3                             
release modkey                             >>> snap back and do default search           
modkey + tab/arrow down                 >>>  stop search & focus result1                     
      

When focus is on results list
[input]      >>> [result]         
--------------------------------------------------------------------------------
release modkey   >>> DO NOT snap back to default search (only snap back when search field has focus)

arrows up/down    >>> navigate list
enter/F2/F3...   >>> default action on result1/2/3...

Alternative 1:
hold modkey1/2/3 + enter       >>> Action1/2/3 on selected
press+release modkey1/2/3    >>> Action1/2/3 on selected
hold modkey1/2/3 + F2/F3...   >>> Action1/2/3 on result2/3...

Alternative 2:
press CTRL + enter       >>> context menu list with Action1/2/3 and more as options
arrows up/down       >>> navigate list
release CTRL or enter again    >>> do action selected in list
(Advanced: instead of list, use 3x3 cell matrix. Hold up & right to  select upper right cell. And so on.)

To help remember filters & actions and their modkeys, add three small boxes forming an L shape somewhere in the GUI. The tags on the boxes describes available modkey filters/actions and correspond to the relative placement of the shift, ctrl and alt keys on standard keyboards. When holding a modkey, its box is colored/highlighted.

http://img157.imageshack.us/img157/7360/farrmodkey8on.png



10
Great program!!!    :Thmbsup:

Suggestions:

1. Let mousewheel = scroll hits list up/down edit2 even when search field has focus

2. Tweaks for page up/down & home/end buttons:
- a. when focus in search field, "page down" = one page down in results.
- b. when focus in search field, "end" = to end of results.
- c. when focus in results, "page up"/"home" should work as now BUT when getting to topmost result item, let NEXT "page up"/"home" keypress jump to "search field"  edit: ok, just noticed that TAB jumps between search/results so 2c could be scrapped.

3. Add content filters. Let user specify groups of file name filters (for example TXT = .txt, .doc etc) and apply filter modes via hotkeys, for example ALT, CTRL and SHIFT. When focus in search field, let default mode "snap back" after hotkey release. After moving focus to results, keep filter on. Also, add noticeable interface change to signal current mode (change main title bar color, text and/or color dot in task bar etc)

4. Add action modifiers. Let user specify what action to do when pressing Enter + modifier (CTRL/SHIFT/ALT/WIN). Many of the context menu actions could be used (copy path, explore here...)
As above, add noticeable interface change to signal current mode.

5. When in auto resize mode AND having horizontal scroll bar, the last hit in the list (for example hit 5 out of 5) is partly covered by the scroll bar.

6. Add minimize/maximize buttons.

7. Let two taps on CTRL launch/exit FARR

edit2 ok, two more:
8. Add options for more minimal interface: no column header row, no title bar, smaller scrollbars

9. Disallow executing results on ALT + F-key (for example, ALT+F4)


Pages: prev1 [2]
Go to full version