Hi Jimmie, Thank you for your feedback. Could you open a feature request on https://github.com/pharo-project/pharo-launcher/issues <https://github.com/pharo-project/pharo-launcher/issues> ?
Regards, Christophe > Le 29 avr. 2022 à 11:23, Jimmie Houchin <jlhouc...@gmail.com> a écrit : > > Hello, > > Thanks for all your work. I have only recently started using Pharo Launcher. > I have been using Pharo a long time and was very accustomed to managing my > own images. So I am still learning. It is nice to work with and it is nice to > easily have whichever vm or image you are wanting to start with. > > However I would like one thing if possible. The advantage I had when managing > my own and I can do a combination. Is that I always started a new terminal > and then opened up Pharo and whichever image I wanted. This makes it neat and > clean when running multiple images like I do, to have clean messaging and > clean stdio when I write to stdio. With Pharo Launcher all stdio goes to its > terminal and from whichever image has been started. I don't know how > difficult this would be. But it would be nice if they were an option for > Pharo Launcher to startup the new image from its own new terminal. Just an > idea. > > Again. Thanks for all the work you do. > > Jimmie > > > > On 4/14/22 07:26, Christophe Demarey wrote: >> Hi all, >> >> Pharo Launcher 3.0 has just been released! It is available from >> http://pharo.org/download <http://pharo.org/download>. >> It is based on latest Spec2 and Pharo 10 image. >> It now comes with a native Apple Silicon version and Mac OS packages are >> notarized. >> Big thanks to all contributors, including issue reports. >> >> Here is the changelog: >> Pharo Launcher v3.0 >> New features: >> >> Full rewrite of the UI using Spec 2 and Pharo 10 >> Pharo Launcher can now run natively on Apple Silicon #544 >> <https://github.com/pharo-project/pharo-launcher/issues/544> >> Pharo Launcher is now signed with a Mac Os developper account and notarized >> #529 <https://github.com/pharo-project/pharo-launcher/issues/529> >> Windows "portable" package (only an archive without installer) #534 >> <https://github.com/pharo-project/pharo-launcher/issues/534> >> Improvements: >> >> While importing image .sources and .version are not moved #543 >> <https://github.com/pharo-project/pharo-launcher/issues/543> >> recreate the image does not re apply the script if one is provided #536 >> <https://github.com/pharo-project/pharo-launcher/issues/536> (thanks to >> @hogoww <https://github.com/hogoww>) >> Save keybind for scripts #545 >> <https://github.com/pharo-project/pharo-launcher/pull/545> (thanks to >> @hogoww <https://github.com/hogoww> and @Inao0 <https://github.com/Inao0>) >> Bug fixes: >> >> GitHub releases artefacts download were not always working #535 >> <https://github.com/pharo-project/pharo-launcher/issues/535> >> "Basic launch" does not do its job in Pharo 10 #540 >> <https://github.com/pharo-project/pharo-launcher/issues/540> >> Proxy settings not applied through settings screen #541 >> <https://github.com/pharo-project/pharo-launcher/issues/541> >> >> Regards, >> The Pharo team.
