Le 16 mars 2018 à 17:05, Ben Coman <btc@openinworld.com> a écrit :
On 16 March 2018 at 22:23, Peter Uhnák <i.uhnak@gmail.com <mailto:i.uhnak@gmail.com>> wrote:
For now, if you are admin, you could install PharoLauncher under « Program Files » but then, you also need to be admin to run it. If you are not admin, you should install PharoLauncher elsewhere.
As I see this recommendation for the Nth time, maybe it is time the default location to C:\Pharo (or C:\PharoLauncher) ...
other languages don't seem to have any problem with that whatsoever (I see in my dir C:\Python27, C:\Ruby24-x64, cygwin, msys, mingw, ...)
If the installer cannot escalate on its own, it shouldn't try in the first place. Otherwise it's just bad experience in literally the first step people will take with Pharo.
Interestingly Python 3 has installed itself in %APPDATA%\Local\Programs\Python\Python36-32 ... so maybe that's also a location to consider which doesn't require admin rights.
Peter
I think Python 3 has it right. Its also where GitForWindows installs itself.
Alternatively the parent %APPDATA%\Local\ (equivalently %LOCALAPPDATA% which can be typed into Windows Explorer) is where many apps seem to put their main executable. On my system I discover... %LOCALAPPDATA% \ Discord \ app-0.0.298 \ Discord.exe %LOCALAPPDATA% \ Atom \ atom.exe %LOCALAPPDATA% \ GitHubDesktop \ GitHubDesktop.exe %LOCALAPPDATA% \ slack \ slack.exe %LOCALAPPDATA% \ Roblox \ Versions \ RobloxStudioLauncherBeta.exe
Very good idea. I updated Pharo Launcher to use LOCALAPPDATA. Thanks Ben