- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Experiment: New Download page based on Pharo Launcher

by Ben Coman

On 26 March 2018 at 22:08, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > Hi Ben, > > Le 23 mars 2018 Ã 19:53, Ben Coman <btc(a)openinworld.com> a Ã©crit : > > Coincidentally I have returned to Windows for a short while so thought I > should > put my money where my mouth is and have a stab at this. After a few hours > trying with NSIS, > I went searching for an alternative and Advanced Installer looked like a > good chance. > https://www.advancedinstaller.com/feats-list.html > The important part of (free) Basic Features is "Windows 10/8/7/Vista and > UAC installs" > Also further down are some CI options. > > > What bothers me is that it is not a free tool. > Its not open source, but its (beer) free for the basic features we need. The msi-installer I created was a 'Simple' project. https://www.advancedinstaller.com/licenses.html says... "The 'Simple' projects use only freeware features ... No license is necessary when using only freeware features in "Simple" projects. Install packages created using these features can be freely redistributed and used both in commercial and non-commercial purpose (subject to EULA)." The EULA (https://www.advancedinstaller.com/eula.html) says... "2.1 Freeware Features License. Caphyon grants you an unlimited license to use the Freeware Features of the Software. The install packages created using only the Freeware Features can be freely redistributed and used both in commercial and non-commercial purpose. and except for Part 11 the rest seems fairly innocuous. > I can see the list of features here: https://www. > advancedinstaller.com/feats-list.html > > > After just the "Simple Installation" tutorial and experimenting a few > hours I ironed out > a potential solution uploaded for testing to http://www.mediafire.com/ > file/3g579bmzqspt8e1/BCPharoLauncher.msi > with the full build tree at http://www.mediafire.com/ > file/5ijiww848lbkk7m/PharoLauncher%20Advanced%20Installer.zip > Links should be live for 30 days. > I've directly attached the much smaller installer-configuration file > "PharoLauncher.aip". > > > PharoLauncher was built with some minor changes from above... > 1. Download/extracted http://files.pharo.org/platform/Pharo6.1-win.zip > > 2. Renamed Pharo6.1 folder to BCPharoLauncher > Renamed Pharo6.1.* files to PharoLauncher1.1.* > > 3. Metacello new > smalltalkhubUser: 'Pharo' > project: 'PharoLauncher'; > configuration: 'PharoLauncher'; > load. > PharoLauncher hardResetPersistanceState: true. > PhLDeploymentScript doAll. > PhLDeploymentScript closeWindowsAndOpenLauncher. > Smalltalk snapshot: true andQuit: true. > > 4. Moved the image & changes files into a subfolder "PerUserFiles" > > 5. Built BCPharoLauncher.msi > > I prefixed my initials to distinguish it from the current official > PharoLauncher installer. > Hopefully this can be adopted as the official installer and they can be > dropped off. > > > Key features: > a. Provides a choice to install for "Everybody" (i.e. C:\Program Files > (x86)\Pharo\BCPharoLauncher\) > or "Only for me" (i.e. C:\Users\Ben\AppData\Local\Programs\Pharo\ > BCPharoLauncher\) > per attached screen snapshot. > > b. Start the install as a Standard User and it escalates only as needed. > > c. The Desktop and Start Menu shortcuts run the following script... > > // File: PharoLauncher.js > // Author: Ben Coman 2018.03.24 > // Purpose: Facilitate each user to run a personal copy of > PharoLauncher.image in their own data area. > > // Locations > basename = "\\PharoLauncher1.1"; > WshShell = WScript.CreateObject("WScript.Shell"); > fso = WScript.CreateObject("Scripting.FileSystemObject"); > systemFolder = fso.GetAbsolutePathName("."); > vmFilename = systemFolder + "\\Pharo.exe" > systemBasename = systemFolder + "\\PerUserFiles" + basename; > userFolder = WshShell.ExpandEnvironmentStrings("% > LOCALAPPDATA%\\Pharo"); > userFolder2 = userFolder + "\\PharoLauncher"; > userBasename = userFolder2 + basename; > > // Ensure user data folder exists for PharoLauncher > if( ! fso.FolderExists(userFolder)) > { fso.CreateFolder(userFolder); > fso.CreateFolder(userFolder2) > } > > // If either image or changes files missing from user folder, > copy from system folder. > if( ! fso.FileExists(userBasename + ".image") || ! > fso.FileExists(userBasename + ".changes")) > { > //WScript.Echo("Setting up user environment"); > fso.CopyFile(systemBasename + ".image", userBasename + > ".image", true); > fso.CopyFile(systemBasename + ".changes", userBasename + > ".changes", true); > } > > // Start personal copy of PharoLauncher > WshShell.Exec(vmFilename + " " + userBasename + ".image Â») > > > UAC support is really nice. > I would like to have the community opinion on using a non-free tool like > advancedinstaller. > If there is no objection, I would consider it seriously for a next Pharo > Launcher version. > Another alternative or subsequent step might be to decompile the msi-installer I supplied into Wix configuration files using dark.exe ( https://support.smartbear.com/viewarticle/10196/) and build the installer using Wix, which is open source ( http://wixtoolset.org/about/license/) Thanks for this work Ben! > Your welcome. Just an itch I had to scratch.... if you can't solve the problem, change the problem ;) cheers -ben

March 26, 2018

Re: [Pharo-dev] Some segfault crashes and freezes when trying to re-run saved pharo 7 images

by Holger Freyther

> On 26. Mar 2018, at 00:00, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi Holger, Hey! > Is the intent of CCallOut with: aBlock to collect and defer deallocations until the block completes? I think it's nice but complex and wonder how general it is. But it seems like it would impact a lot of code and require a lot of effort changing existing code bases. My handle scheme is only intended to fix the issue of images crashing on startup. The problems with crashing on startup being a) one loses one's work and b) the issue is hard to debug. That, for me, motivates something like the simple fix I p[roposed. I'm not standing in the way of something more beautiful, but I do believe that one shouldn't make the perfect the enemy of the good. By all means, let's have a smart pointer! It will be beneficial for freetype and many other places. Nobody likes crashing images (for a mistake made in a previous run). My intent with the CCallOut is inhibit image saving until the code is outside a sequence of (interruptible, hence the backward jump int the example) C calls working with one or more pieces of manually managed memory. But maybe it is best to call it by what it does instead of finding a name of where it is used. I can't come up with a better example right now. But I think a Smartpointer wouldn't be of much help with a sequence of strtok calls. word := CStringAPI strtok: cStringPtr safeBytes separator: '\r'. [word isNil] whileFalse: [ word = 'Foo'... word = 'Bla'... word := CStringAPI strtok: nil separator: '\r' ------------- Image Save happening right here and word is not nil ----- ]. I hope this is more clear. holger

March 26, 2018

Re: [Pharo-dev] Experiment: New Download page based on Pharo Launcher

by Ben Coman

On 26 March 2018 at 21:56, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > Hi Ben, > > Le 23 mars 2018 Ã 04:31, Ben Coman <btc(a)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 was thinking the filter could be broader with a wildcard match " *.exe ". There shouldn't be too many exe files in the folder, and any non-Pharo-exe should just fail to match the VM magic numbers and not affect anything anyway. On the other hand, perhaps this would cause the user's Image to show up in Task Manager as being run by PharoLauncher rather than Pharo, which again blurs the line between the two that I'd like to avoid. So I'll back away from that idea. > > 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 > Using my day-to-day account "Ben" which is a Standard User account, I did the following... 1. Downloaded "pharo-launcher-installer-bleedingEdge-2018.03.23-x86.exe" 2. Double-clicked it and got "Windows Defender SmartScreen prevented an unrecognized app from starting." [1] (btw, I didn't get this with the msi-installer generated from Advanced Installer which I linked above. But maybe that was because the msi-installer was created and installed on the same PC, so it was just trusting itself by default. The msi wasn't signed, so is the experience different on other people's machine?) 3. Clicked "More Info" which allowed me to click "Run Anyway" and got... "To continue, enter admin user name and password" [2] so this is not really suited to students doing a user-level install on locked down lab machines. 4. After entering the password for user "Admin" (i.e. not Administrator, just another account in Administrators group) the install location was (as expected) given as.... "C:\Users\Admin\AppData\Local\PharoLauncher" [3] which again is not friendly to non-admin users. But just for kicks, I changed the install location to... "C:\Users\Ben\AppData\Local\PharoLauncher" and clicking on the PharoLauncher icon in the Start Menu it opened okay, and downloaded a 60539 image and associated VM and that image ran okay. So its a step in the right direction, however... the Start Menu shortcut entry is for All User per its location here... C:\ProgramData\Microsoft\Windows\Start Menu\Programs\PharoLauncher and the target of the shortcut is... C:\Users\Ben\AppData\Local\PharoLauncher\Pharo.exe so it only worked coincidentally because I'm clicking the Start Menu icon as user "Ben" and it would be broken for a second Standard User. >From my reading it will be a struggle to get NSIS working smoothly for multiple use cases at different privilege levels. i.e. both non-admin and admin users. cheers -ben

March 26, 2018

Re: [Pharo-dev] Windows PharoLauncher cannot create "C:\Program Files (x86)\Pharo\Pharo.image"

by Christophe Demarey

> Le 16 mars 2018 Ã 17:05, Ben Coman <btc(a)openinworld.com> a Ã©crit : > > > > On 16 March 2018 at 22:23, Peter UhnÃ¡k <i.uhnak(a)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

March 26, 2018

Re: [Pharo-dev] Experiment: New Download page based on Pharo Launcher

by Christophe Demarey

Hi Ben, > Le 23 mars 2018 Ã 19:53, Ben Coman <btc(a)openinworld.com> a Ã©crit : > > Coincidentally I have returned to Windows for a short while so thought I should > put my money where my mouth is and have a stab at this. After a few hours trying with NSIS, > I went searching for an alternative and Advanced Installer looked like a good chance. > https://www.advancedinstaller.com/feats-list.html <https://www.advancedinstaller.com/feats-list.html> > The important part of (free) Basic Features is "Windows 10/8/7/Vista and UAC installs" > Also further down are some CI options. What bothers me is that it is not a free tool. I can see the list of features here: https://www.advancedinstaller.com/feats-list.html > > After just the "Simple Installation" tutorial and experimenting a few hours I ironed out > a potential solution uploaded for testing to http://www.mediafire.com/file/3g579bmzqspt8e1/BCPharoLauncher.msi <http://www.mediafire.com/file/3g579bmzqspt8e1/BCPharoLauncher.msi> > with the full build tree at http://www.mediafire.com/file/5ijiww848lbkk7m/PharoLauncher%20Advanced%20In… <http://www.mediafire.com/file/5ijiww848lbkk7m/PharoLauncher%20Advanced%20In…> > Links should be live for 30 days. > I've directly attached the much smaller installer-configuration file "PharoLauncher.aip". > > > PharoLauncher was built with some minor changes from above... > 1. Download/extracted http://files.pharo.org/platform/Pharo6.1-win.zip <http://files.pharo.org/platform/Pharo6.1-win.zip> > > 2. Renamed Pharo6.1 folder to BCPharoLauncher > Renamed Pharo6.1.* files to PharoLauncher1.1.* > > 3. Metacello new > smalltalkhubUser: 'Pharo' > project: 'PharoLauncher'; > configuration: 'PharoLauncher'; > load. > PharoLauncher hardResetPersistanceState: true. > PhLDeploymentScript doAll. > PhLDeploymentScript closeWindowsAndOpenLauncher. > Smalltalk snapshot: true andQuit: true. > > 4. Moved the image & changes files into a subfolder "PerUserFiles" > > 5. Built BCPharoLauncher.msi > > I prefixed my initials to distinguish it from the current official PharoLauncher installer. > Hopefully this can be adopted as the official installer and they can be dropped off. > > > Key features: > a. Provides a choice to install for "Everybody" (i.e. C:\Program Files (x86)\Pharo\BCPharoLauncher\) > or "Only for me" (i.e. C:\Users\Ben\AppData\Local\Programs\Pharo\BCPharoLauncher\) > per attached screen snapshot. > > b. Start the install as a Standard User and it escalates only as needed. > > c. The Desktop and Start Menu shortcuts run the following script... > // File: PharoLauncher.js > // Author: Ben Coman 2018.03.24 > // Purpose: Facilitate each user to run a personal copy of PharoLauncher.image in their own data area. > > // Locations > basename = "\\PharoLauncher1.1 <smb://PharoLauncher1.1>"; > WshShell = WScript.CreateObject("WScript.Shell"); > fso = WScript.CreateObject("Scripting.FileSystemObject"); > systemFolder = fso.GetAbsolutePathName("."); > vmFilename = systemFolder + "\\Pharo.exe <smb://Pharo.exe>" > systemBasename = systemFolder + "\\PerUserFiles <smb://PerUserFiles>" + basename; > userFolder = WshShell.ExpandEnvironmentStrings("%LOCALAPPDATA%\\Pharo"); > userFolder2 = userFolder + "\\PharoLauncher <smb://PharoLauncher>"; > userBasename = userFolder2 + basename; > > // Ensure user data folder exists for PharoLauncher > if( ! fso.FolderExists(userFolder)) > { fso.CreateFolder(userFolder); > fso.CreateFolder(userFolder2) > } > > // If either image or changes files missing from user folder, copy from system folder. > if( ! fso.FileExists(userBasename + ".image") || ! fso.FileExists(userBasename + ".changes")) > { > //WScript.Echo("Setting up user environment"); > fso.CopyFile(systemBasename + ".image", userBasename + ".image", true); > fso.CopyFile(systemBasename + ".changes", userBasename + ".changes", true); > } > > // Start personal copy of PharoLauncher > WshShell.Exec(vmFilename + " " + userBasename + ".image Â») UAC support is really nice. I would like to have the community opinion on using a non-free tool like advancedinstaller. If there is no objection, I would consider it seriously for a next Pharo Launcher version. Thanks for this work Ben!

March 26, 2018

Re: [Pharo-dev] Experiment: New Download page based on Pharo Launcher

by Christophe Demarey

Hi Ben, > Le 23 mars 2018 Ã 04:31, Ben Coman <btc(a)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

March 26, 2018

Re: [Pharo-dev] Experiment: New Download page based on Pharo Launcher

by Christophe Demarey

Hi CÃ©drick, You could give a chance to this version (not official): https://ci.inria.fr/pharo-ci-jenkins2/job/PharoLauncher/lastSuccessfulBuild… It does not require anymore admin mode. I think the error below comes from missing write permissions on the file system. Thanks for the feedback, Christophe > Le 22 mars 2018 Ã 22:14, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> a Ã©crit : > > Hi, > > I just saw students and they still have some problem on windows with the launcher. > > First, the launcher has to be run in admin mode. > > Then, the image download starts but there is an error when uncompressing. Here is the stack. > > Any idea on how to fix that ? > > > > FileHandle>>streamError > FileHandle>>writeStream > FileSystem>>writeStreamOn: > FileReference>>writeStream > FileReference(AbstractFileReference)>>writeStreamDo: > ZipFileMember(ZipArchiveMember)>>extractInDirectory:overwrite: > [ :entry | > | response | > entry isDirectory > ifFalse: [ bar ifNotNil: [ bar label: 'Extracting ' , entry fileName ]. > response := entry > extractInDirectory: aDirectory > overwrite: overwriteAll. > response == #retryWithOverwrite > ifTrue: [ overwriteAll := true. > response := entry > extractInDirectory: aDirectory > overwrite: overwriteAll ]. > response == #abort > ifTrue: [ ^ self ]. > response == #failed > ifTrue: [ (self confirm: 'Failed to extract ' , entry fileName , '. Proceed?') > ifFalse: [ ^ self ] ] ] ] in ZipArchive>>extractAllTo:informing:overwrite: in Block: [ :entry | ... > OrderedCollection>>do: > ZipArchive>>extractAllTo:informing:overwrite: > ZipArchive>>extractAllTo:informing: > [ :bar | self extractAllTo: aDirectory informing: bar ] in ZipArchive>>extractAllTo: in Block: [ :bar | self extractAllTo: aDirectory informing: ...etc... > [ :bar | aBlock value: bar ] in MorphicUIManager>>informUserDuring: in Block: [ :bar | aBlock value: bar ] > BlockClosure>>cull: > [ ^ block cull: self ] in [ self prepareForRunning. > CurrentJob value: self during: [ ^ block cull: self ] ] in Job>>run in Block: [ ^ block cull: self ] > [ activeProcess psValueAt: index put: anObject. > aBlock value ] in CurrentJob(DynamicVariable)>>value:during: in Block: [ activeProcess psValueAt: index put: anObject.... > BlockClosure>>ensure: > CurrentJob(DynamicVariable)>>value:during: > CurrentJob class(DynamicVariable class)>>value:during: > [ self prepareForRunning. > CurrentJob value: self during: [ ^ block cull: self ] ] in Job>>run in Block: [ self prepareForRunning.... > BlockClosure>>ensure: > Job>>run > MorphicUIManager(UIManager)>>displayProgress:from:to:during: > MorphicUIManager>>informUserDuring: > ZipArchive>>extractAllTo: > PhLRemoteTemplate(PhLAbstractTemplate)>>extractZipArchive:to: > PhLRemoteTemplate(PhLAbstractTemplate)>>extractTo:named: > PhLDirectoryBasedImageRepository>>extractTemplate:to: > PhLCreateImageFromTemplateCommand>>execute > PhLCreateImageFromTemplateCommand(PhLCommand)>>executeIfApplicable > PhLCommandButton>>performAction > > > > Thanks > > CÃ©drick

March 26, 2018

Re: [Pharo-dev] Experiment: New Download page based on Pharo Launcher

by Christophe Demarey

Hi Peter, > Le 17 mars 2018 Ã 19:00, Peter UhnÃ¡k <i.uhnak(a)gmail.com> a Ã©crit : > > > Runs fine - creates images and vms but when you try to > > run them nothing happens. It fails to start the selected image. It just > > fails to run the vm at all as far as I can see. > > I am also experiencing this... > > With ProcessWrapper the image launches maybe 1 out of 10 times... > So I hacked for myself a solution based on Torsten's OS-Window (which uses WinAPI) ... but even then the launch success rate is below 90%... > > I guess Pharo really doesn't like talking to Windowsâ¦ It looks like Windows OS integration is not the top priority of the community. We have to do with the current situation before hoping a better support. Could you test this version and tell me if the situation goes better? https://ci.inria.fr/pharo-ci-jenkins2/job/PharoLauncher/lastSuccessfulBuild… Thanks, Christophe

March 26, 2018

Re: [Pharo-dev] Experiment: New Download page based on Pharo Launcher

by Christophe Demarey

Hi Alexandre, Yes, Pharo Launcher is maintained. But if maintainer(s) is not aware that there are issues, they will never be fixed. So please, open issues at https://github.com/pharo-project/pharo-launcher/issues with details as mentioned by Sean. Thanks, Christophe > Le 17 mars 2018 Ã 17:42, Sean P. DeNigris <sean(a)clipperadams.com> a Ã©crit : > > abergel wrote >> Yesterday we also experienced many problem when using Launcher on OSX :-( > > Hmm, I've been using exclusively daily for many months with minimal > glitches. Please post OS, Pharo system report, download method and any other > relevant details. The major "gotchas" of the past were: 1) The app has to be > in the "Applications" folder 2) the first time it was started you needed to > work around a signing issue e.g. via [right click]->Open->[Confirm dialog]. > The app will not open, but from now on you can just open in the normal way > (e.g. double clicking the .app). HTH > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

March 26, 2018

Re: [Pharo-dev] Experiment: New Download page based on Pharo Launcher

by Christophe Demarey

Hi Ben, > Le 17 mars 2018 Ã 14:26, Ben Coman <btc(a)openinworld.com> a Ã©crit : > > > > On 17 March 2018 at 19:57, kmo <voxkmp(a)gmail.com <mailto:voxkmp@gmail.com>> wrote: > I tried the default download of Pharo Launcher on my Windows 7 (32 bit) PC at > work. It installs. Runs fine - creates images and vms but when you try to > run them nothing happens. It fails to start the selected image. It just > fails to run the vm at all as far as I can see. > > I tried it on my Windows 10 (32 bit) laptop and got exactly the same result. > > This is not important for me as I use pharo on Linux - but I thought I'd > point it out. If having the launcher as the default download causes more > problems than the traditional vm and image download then perhaps it should > be reconsidered. A pity since I love the launcher. > > We've seen before when features are promoted in visibility (e.g. each GT tool) > they come under more scrutiny and bump a wider set of environments > that cause hiccups. Ultimately this feedback is beneficial to the tool. > So I don't think there is any need to panic into a reversal. > Lets give a chance to work through the issues. Yes, that is the idea. Testing on all OS, different versions is just not possible. Nevertheless, it looks that there are some common bugs that I did not encountered when testing. So, please test PharoLauncher and if you have issues, report them with the maximum information because it is hard to reproduce: https://github.com/pharo-project/pharo-launcher/issues > (but it might be good for the older links to be also available further down the page > while Launcher issues are sorted out) > > cheers -ben

March 26, 2018