Good ideas overall. Some insights:
2. Index registry "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths" so Launchy acts exactly as Win+R
You are very correct. it is really illogical that even though FARR is installed you STILL have to use Win+R. The basic idea should be that FARR by default does everything Win+R does and builds over it. Why force someone to use 2 different utilities? Here is a simple list of the things I can't just write in FARR (without extensive aliasing, which is obviously not an option):
- notepad c:\file.txt
You can argue that instead of "winword" I could write "word" in FARR in just let it search my Start Menu but for many people it became a common practice to type exactly that. Beside that, "winword" will work on any (windows) computer, FARR or not and it always best to work with the standards.
The author idea are sure to solve some of these issues (if fixed) but more needs to be done. FARR should work just as if is Win+R. I thought to write a plugin like that but it would be a lot better if it was in the core of FARR.
7. When a exact file/folder matches, support drag & drop operations compatible with Explorer. e.g. I type
Well, as you know there is such an option (and thus the striking). However, I wish there was a hotkey to access the explorer shell (e.g shift+right click).
Another issue that wasn't mentioned is the search-as-you-type. The problem occurs especially with the Locate32 plugin - FARR sends what you write immediately to all the plugins. While this can be solved on the plugin level, it might be better if FARR didn't "send as you type" but instead give it a few milliseconds for you to finish the search query (or even better, make the delay customizable).