I agree on those points.
The console client is more aimed at corporate folders, people who deploy onto other mass networked systems, linux server users that have no x or gui available, and anyone else who has no need for FAHControl.
It would be better to have it on a seperate page, like the old High Performance clients were.
calxalot wrote:If stand alone client means no installer, just FAHClient, FAHCoreWrapper, and some doc files, I suppose so.
But I would put these on a separate download page, without friendly terms like "no-nonsense", and with a warning making it clear that you must use the command line to use them.
The client also needs to be smart enough to not use the current working directory if the user just double clicks the exe, as that would probably be their home directory.
It should use the exe directory, or some default under the user's home.
This problem really only occurs for Windows.
For Linux and Macs the setup process is a little different and a bit harder. In general their is no such thing as double clicking the .exe (unless you are running something via Wine).
Also i agree at losing the no-nonsense. Maybe we can have Pro Console Only Client?
(But it will probably just be console client).