Hi Ben,
Le 23 mars 2018 à 04:31, Ben Coman <btc@openinworld.com> a écrit :
P.S. I was going to suggest also renaming Pharo.exe to PharoLauncher.exe but with an empty Documents\Pharo\vms I get... "Error: Cannot detect Pharo executable in C:\Temp\MyPharoLauncher\PharoLauncher" in PhLVirtualMachine>>initializeOn: "File @ C:\Temp\MyPharoLauncher\PharoLauncher" since "executables := aFolder allChildrenMatching: self class executableName." is empty since "self class executableName" ==> "Pharo.exe"
It would be nice for that to not be hard coded.
Where would you put this information?
I tried digging further but ran out of time. I am curious it mattered since using "Pharo.exe" the Launcher went on to download a VM anyway.
I use the vm shipped with the launcher when possible (e.g. to determine pharo images version format or run current stable images. If I cannot find the proper vm, then I download it from files.pharo.org.
P.S.2. I believe the best path forward for system-wide PharoLauncher installed under "C:\Program Files" would be to install there only... * the VM * PharoLauncher.ZIP * a tiny non-Pharo wrapper program as the shortcut linked from AllUsers > Start Menu > PharoLauncher that extracts PharoLauncher.ZIP to the user's data area and then starts that user specific PharoLauncher.
Then regardless whether: * they individually download/extract PharoLauncher.ZIP * the system-wide-wrapper extracts PharoLauncher.ZIP its a similar experience for users which should aid reliability by reducing the number of "different " use cases.
I now install PharoLauncher in user LOCALAPPDATA folder on windows. Does it solve the issue for you? Christophe