4
« on: July 19, 2014, 01:24 PM »
That is a good suggestion. However, my main observation is that it can be very valuable to easily assign an optional searchable custom keyword to each alias/action which now cannot be done in FARR. In that way you can search the keywords that only you defined and allowed into your search universe (which keyword could still be the original file name, a shortcut alias version of the name, several keywords together, or any combination). In that way, your searches will be of your customized keyword universe not limited to the original file/folder names. This can be very useful.
Obviously, there are different ways to implement keyword based weighting, e.g., adding a keyword to aliases or the quick and dirty method I used with shortcuts that are placed in a separate folder and that folder is heavily weighted in searches.
Along that shortcut line, it occurred to me that simply adding a menu item to the context menu in search results that creates a shortcut (which you rename to your keyword or keep the original name as is) in a %FARR_Shortcuts% folder also 'implements' a keyword weighting system. You then weight that folder to emphasize the degree of constraint your keyword universe imposes on searches. Constraining sharply limits the "breaking" of searches as files changes and keywords make your searches much more efficient over time as you add them to your "system". I create many such 'aliased' shortcuts to my key autohotkey scripts, folders I use a lot, folders or other items that are currently important to me (e.g., I might call a shortcut 'current project' and change its target as my projects change). I know that currently FARR can accomplish focusing on certain items by scoring but you still have the problem of a search applying to your entire universe of folders and the fixed names assigned to files/folders, as opposed to having your own custom alias/keywords substituting for those fixed file names and your search limited to only the universe you create over time.