On Thu, Jan 18, 2018 at 5:16 PM, Stephane Ducasse <stepharo.s...@gmail.com> wrote:
> supe super coooool > Christophe? do have I just to replace the previous version and use > this one and I will get everything as before > but with the new version? > > I did that and it worked for me > Stef > > On Tue, Jan 16, 2018 at 9:46 PM, Christophe Demarey > <christophe.dema...@inria.fr> wrote: > > Hi all, > > > > I just released PharoLauncher 1.1. There are now 64-bits versions for Mac > > and Linux. Jenkins build is now managed through a Jenkins file. > > > > Here is the changelog (details on > > https://github.com/pharo-project/pharo-launcher/issues): > > New features: > > #66 new command: import an image into the launcher default image folder > > #65 new command: remove a template from "Downloaded templates" > > #64 new command: create a local template from an image and remove the > image > > #57 new option: run an image from a login shell to inherit from shell > > startup scripts to set up environment variables. > > #54 It is now possible to run an image anywhere on your file system if > you > > click "launch" and no image is selected > > #23 Pharo Launcher now has an "about" box giving its description, version > > and a link to the bug tracker. > > Improvements: > > #62 Pharo Launcher should not load default Pharo settings > > #51 Pharo Launcher now sets the current directory to the directory > > containing the image (was the VM directory). Avoid confusions in Pharo 7 > > images. > > Bux fixes: > > #60 hardReset option causes troubles to PharoLauncher > > #56 #, was sent to nil > > #55 Display name of Pharo 7 images unusable > > #52 Cannot open a Pharo 2 image > > #47 Cannot run pharo 50 pre-Spur images > > > > You can get platform bundles from files.pharo.org: > > http://files.pharo.org/pharo-launcher/1.1/ > > > > Regards, > > Christophe. > > -- Mariano http://marianopeck.wordpress.com
