Messages - Amadawn [ switch to compact view ]

Pages: prev1 2 3 4 [5] 6 7 8 9 10 ... 18next
If the main problem shown by this thread is how to distinguish between the "main case" where FARR must do a regular search and the "5%" case, in which we must provide FARR with a "verb" (or command), why can't you just select a "escape character" that must be used for commands?

For instance, maybe we could use ">" which is not allowed in any Windows filename. If ">" is the first character on the command line, assume that it is followed by a command (like "define", for instance). Otherwise, assume that we are in "normal" mode.

Of course, while in normal mode, you could still be able to stack "commands" as it has been discussed above (QuickSilver style).

Does this make sense?


ContextMenu Commander / Re: ContextMenu Commander
« on: February 04, 2006, 06:55 PM »
There are 2 things that I'd love to add to my explorer context menu:

- A folders submenu with all my favorite folders that would allow me to navigate to them with a simple right click (and it should be able to reuse any open explorer window if I want it to)
- A "Create folder" button (as the windows "New>" submenu is sooo slow!!!).

A tool that adds those two (and perhaps "command promt here" although there is already a Microsoft PowerToy that does that) woul be perfect!


P.S.- When is the first release of this program expected?
The thing that I'd like the most wou

OK. I really think that allowing both would be better, as it works for most cases (when you are searching for a program or file). I also think that we should allow more complex actions (like filename email address or filename copy foldername, etc).

Man, this is becoming a very ambitious project, mouser!!! :)

i think its impossible to do what we want and have subject first.
the only choices are always verb first, or combined verb+subject first.

why cant you do subject firt? well because we want to support things like being able to say:
"email [email protected]"
"define subjunctive"
"google happiness"

ie after you type the verb only then does it know how to interpret what you type.

but we could stick with the approach we have now which combines the two and tried to guess what you want.

requiring a verb first (which would default to "launch" if you hit space or tab) would make life a lot cleaner.

the main problem is it makes the 95% case more troublesome.

OK, I understand the issue. However, I still believe that there must be a way to cover all cases and keep everybody happy.

As you say, the cases in which we absolutely need the verb to come first correspond to perhaps 5% of the functionality of FARR. Those, I believe, can be covered as "special cases" where the user can define "keywords" that when selected would require some additional parameter.

But if the user types/selects any other item, it could then simply type the name of one of the actions linked to that action, and perhaps follow by another parameter.

For instance:

Type: tax<tab>(finds "tax plan.doc") em<tab>(finds "email to")[email protected]<ENTER> (eventually FARR could even search in the addres book, but that's another issue). This sends "tax plan.doc" by email to "[email protected]".

But you could also type:
define<tab>(finds "action define:", stops searching for stuff)rose<ENTER> which fires the default web browser and looks for the definition of "rose".

I think that this method has the advantage of being very intuitive, covering all cases and requiring very little keypresses. Of course if at any point there is some ambiguity (like for instance if there were both a "tax plan.doc" and a "taxi address.txt" the user would need to use the keyboard arrows or the Ctrl+number technique to select the one that he wants. Same thing for actions, where instead of typing "em" you could simply use the arrows to select "email", "copy" or whatever other actions supported by that file type.

I agree however that this might be complicated to code, but hey, you are the wizard coder and the one that seemed eager to solve a complex UI puzzle! :)

Wow! This is an interesting thread!

mouser, you talk about having the first word be always a verb. In my opinion that causes a problem because most of the time what you want to do with FARR (or at least that is what I want) is to find SOMETHING. So why not do as QuickSilver does, and require always to have first a "SUBJECT" (i.e. what we are going to work with), then a verb (what we are going to do with it, which by default would be launch) and finally an object (if the VERB requires another parameter, like where to copy a file for instance).

I think that would solve the problem because you would get the current, default behaviour (which is what you normally want) but can still add modifiers to the task at will. Also it does not limit you to actions that work on a single file.


Pages: prev1 2 3 4 [5] 6 7 8 9 10 ... 18next
Go to full version