[ANN] Pharo Launcher v1.2 release

Le 20 juin 2018 à 10:48, Serge Stinckwich <[hidden email]> a écrit :

On Wed, Jun 20, 2018 at 9:04 AM Christophe Demarey <[hidden email]> wrote:

Le 19 juin 2018 à 16:28, Serge Stinckwich <[hidden email]> a écrit :

I dl the 64 bits VM for macOS. Everytime I run a 32 bits image, I have a warning that using a 32 bits images, require a 32 bits VM.

And then when I select yes, everything works. Why having this warning everytime ?

I added this warning so that people are aware that they use 32-bit images on a 64-bit system. We are moving to mostly 64-bit images.

The biggest concern for this warning was raised by a Linux user: he installed a 64-bit Pharo Launcher and was surprised to not be able to launch 32-bit images. Indeed, on linux, you need additional set up (i.e. install 32-bit libraries) to be able to launch 32-bit images.

I understand thi warning could be annoying. Maybe I should add a setting to ignore these warnings? Would it be enough? Or should I only warn on Linux where it is really important? But in this case, people could may not be aware of using 32 or 64 bits images.

​Yes maybe only have the warnings on Linux made more sense. ​

Could you open an issue for that?

​Ok done here:

​ ​

​https://github.com/pharo-project/pharo-launcher/issues/129

Le 19 juin 2018 à 15:55, Christophe Demarey <[hidden email]> a écrit :

Hi all,

I just released PharoLauncher 1.2. It includes a new windows installer that you can use without administrator privileges as well as binary signing for OS X and Windows. Also, Pharo Launcher is not anymore identified as ‘Pharo’ application and comes with its own icon.

Here is the changelog (details on https://github.com/pharo-project/pharo-launcher/issues):

New features:

#21 Bless the DMG

#46 sign pharo launcher app for windows

#103 No way to rename a local template

#107 Unable to add a description for the image using the Launcher UI

#121 You can't see/sort images by last modified date

Improvements:

#69 Import command should also import pharo-local directory

#70 Import command should delete origin folder if empty

#73 Managers of Download of VMs and images should be in their own packages

#76 Use https instead of http to requests the pharo file server

#82 Official Distributions loads 32bit versions on 64bit System (i.e. provide better information on templates architecture)

#86 Sort Existing Images Case-Insensitive

#98 Copy and subfolders problem (contents no copied)

#101 Templates from a local image are listed in "downloaded". "local" would be a better name

#102 Template Cleared at Startup setting is enabled, making it weird when trying to use the template feature

#106 Import could work if we select the parent folder of an image

#109 Use latest pre-Spur VM to determine the image version

#122 The Run without settings icon looks like a funny grey/which blob (missing alpha correction)

Bux fixes:

#41 #selectedMorphList was sent to nil

#67 bash is not a command usable under windows

#68 Does not launch images on Windows

#85 Double click on an existing image open a file selector

#88 Pharo Launcher on Windows > Failing

#104 GUI bug makes Launcher unusable

#110 Image launch not reliable on Windows

#119 MessageNotUnderstood exception on launch

#123 The status bar of the Launcher is broken, so can't easily show image descriptions 

Big thanks to all contributors: code, issues report, comments, advices.

You can get platform bundles from pharo download page or files.pharo.org: http://files.pharo.org/pharo-launcher/1.2/

Regards,

Christophe.