Currently it's up to the user to install aliases, and the folder in which they should install them in different depending on the OS and the type of alias (should it be editable or not by the user). From the help file:
These .alias files are located in the AliasGroups\ subdirectory of FARR, and are further broken up into AliasGroups\Installed and AliasGroups\MyCustom.
On my Windows 7 64bit machine, the AliasGroups folder is not there but in C:\Users\<username>\Documents\DonationCoder\FindAndRunRobot\AliasGroups
and the MyCustom folder did not exist.
Now when a third party supplies an alias to enable FARR to use the third party tool, the install will have to give instructions for the user for the correct operating system, plus a series of steps to know where the alias is stored after installation and where it should be manually copied to (and extracted, because there are usually icons and other related files).Feature
I'm requesting a feature for FARR (based on discussions in the IRC chatroom) for FARR to install aliases for the user in the correct folder, using commandline switches. Third-party tools, can then simply read the registry key and call farr:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Find and Run Robot_is1\InstallLocation
(32bit - needs confirmation)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Find and Run Robot_is1\InstallLocation
The alias should be zipped but the extension renamed to .AliasZip, (with the extension registered to farr) so that one can install the alias by double clicking.
The Zip file should contain a folder called either MyCustom or Installed, with inside that a folder with the name of the alias (example) containing icons and the alias etc.Example
With the feature FARR will extract the alias in a temporary folder, and then copy it to the right location, and refresh the aliases-list in FARR with the following code:
FindAndRunRobot.exe /installAlias "Path\To\Example.AliasZip"