Releases: pharo-project/pharo-launcher
Pharo Launcher 3.2
Changelog
Pharo Launcher now comes with a command-line version that you can use from a terminal!
You can check the documentation of commands at https://pharo-project.github.io/pharo-launcher/commands-cmd-line/ as well as instructions to make pharo-launcher available on command line: https://pharo-project.github.io/pharo-launcher/installation/.
This nice feature is now available thanks to the contributions of Axel Marlard, David Bajger and I as well as the support of Damien Pollet for the Clap library.
New features:
-
Command Line support
- all commands available in the UI version of Pharo Launcher are supported
- new commands
- create an image from a Pull Request number (from Pharo repository)
- create an image from a build number, a SHA
- create an image and import your code from a repository
- share easily an image (zip file with the Pharo image, the VM to run it and a launch script)
- find easily the Pharo version where a bug was introduced with image bisect algorithm
- launch an image with a script
- list running Pharo processes
-
When creating an image, the image is now launched automatically
-
CI moved to Github Actions
Improvements:
- Better Mac Os system menu
- Do not try to guess anymore the version of a Pharo image if information not available but rather ask the user
- When deleting more than 1 image at a time the message is not clear #594
Bug fixes:
- Pharo 12.0 build list incomplete #667
- Use "Show" when no image is downloaded yet gives error #570 (thanks to @astares)
- Development mode does not close pharoLauncher application #548
- Using "Show in folder" gives DNU #568 (thanks to @astares)
- Launcher cannot launch Pharo-4.0 image #585
You can still use them but the prefered way is to download signed and notarized installers from https://pharo.org/download
Contributors
Assets 7
3.1.1
Warning: Release artefacts below are not signed nor notarized and by consequence, are not recognized as safe by Operating Systems.
You can still use them but the prefered way is to download signed and notarized installers from https://pharo.org/download
Pharo Launcher 3.0.1
Pharo Launcher 3.0
Pharo Launcher 3.0
Changelog
New features:
- Full rewrite of the UI using Spec 2 and Pharo 10
- Pharo Launcher can now run natively on Apple Silicon #544
- Pharo Launcher is now signed with a Mac Os developper account and notarized #529
- Windows "portable" package (only an archive without installer) #534
Improvements:
- While importing image .sources and .version are not moved #543
- recreate the image does not re apply the script if one is provided #536 (thanks to @hogoww)
- Save keybind for scripts #545 (thanks to @hogoww and @Inao0)
Bug fixes:
Contributors
Assets 2
Pharo Launcher 2.3
Pharo Launcher 2.3
Changelog
New features:
- Apple M1 SoC detection to run arm64 Pharo VM when applicable
- Updated VM urls for Pharo 9 and above
- Squeak and GToolKit support (contributed by Sean DeNigris)
Improvements:
- More tests on image importation (contributed by M. Abdi)
Bug fixes:
- restore some missing navigation keys #499
Pharo Launcher v2.2
Pharo Launcher v2.1
Various bug fixes:
https://github.com/pharo-project/pharo-launcher/issues?q=is%3Aissue+is%3Aclosed+closed%3A2020-04-18..2020-07-20
Enhancement:
Use file locators for serialized metadata to ease the move of data
Pharo Launcher v2.0
This new version introduces major changes:
- The UI has been fully rewritten using the new Spec2 framework and the Commander2 library. UI has been revamped to increase usability, especially for newcomers. The main window is now composed of a toolbar and the list of images. The template list is now available when clicking on the new image button.
- Documentation web site : All Pharo Launcher features are now explained in the new documentation available at https://pharo-project.github.io/pharo-launcher. You can contribute easily by clicking the edit on GitHub button.
- You can now have many launch configurations for an image (VM to use, vm and image arguments). It means you can use headless Pharo VM from Pharo Launcher.
- When creating a new image, you can specify an initialisation script that will be run once at the first image launch. It is useful to load your project code in a stock Pharo image for example. See https://pharo-project.github.io/pharo-launcher/create-images/#image-initialization-script
- You can now define your own template sources in addition to official sources (see https://pharo-project.github.io/pharo-launcher/templates/#create-your-own-list-of-template-categories), including authenticated sources.
- Improved image metadata. Pharo Launcher now manages all image metadata in a single STON file (including description, Pharo version).
Big thanks to all contributors, including issue reports. It is also the opportunity to thanks Damien Cassou, the original author of Pharo Launcher.
Changelog:
The list of closed issue is too long (68) to be listed but you can browse it here: https://github.com/pharo-project/pharo-launcher/issues?q=is%3Aissue+is%3Aclosed+closed%3A2019-07-09..2020-04-17
Here are some highlights:
New features:
- Documentation web site
- Image initialisation script
- Launch configurations, headless VM support
- User template file in addition to the official template file
- Jenkins server template now support pipeline projects
- Support of private Jenkins server
- Support of authenticated HTTP server
Improvements:
- Monitoring of image launch failures to give back the error message (if any)
- Newly created image is automatically selected in the image list
- Allow to set image description at creation time
- Better error management (you will have the choice to ignore them or debug them)
- Add a poor version column in image list
- Speedup (especially when image repository has a lot of images)
Bug fixes:
- Fix use of system unzip on Windows
Pharo Launcher v1.9.2
Bug fixes
- #342 Cannot open anymore OS folder
Pharo Launcher v1.9.1
This version now uses OSSubprocess (Linux and OS X) and OSWinSubprocess.
This change is first motivated by problems Windows users encoutered when launching images. Also OSSubprocess is now the preferred library to use to fork processes on Linux-based systems.