[ANN] PharoLauncher v1.1 released!
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/>: http://files.pharo.org/pharo-launcher/1.1/ Regards, Christophe.
Thank you Christophe for this wonderful work ! On Tue, Jan 16, 2018 at 9:46 PM, Christophe Demarey < christophe.demarey@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.
-- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC/UY1) "Programs must be written for people to read, and only incidentally for machines to execute."http://www.doesnotunderstand.org/
Thank you a lot Christophe! I really enjoy using PharoLauncher. Juraj
On Jan 16, 2018, at 17:46, Christophe Demarey <Christophe.Demarey@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 <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/>: http://files.pharo.org/pharo-launcher/1.1/ <http://files.pharo.org/pharo-launcher/1.1/> Regards, Christophe.
Thanks Christophe!! This is very cool! On Wed, Jan 17, 2018 at 10:03 AM, Juraj Kubelka <juraj.kubelka@icloud.com> wrote:
Thank you a lot Christophe! I really enjoy using PharoLauncher.
Juraj
On Jan 16, 2018, at 17:46, Christophe Demarey <Christophe.Demarey@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
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? Stef On Tue, Jan 16, 2018 at 9:46 PM, Christophe Demarey <christophe.demarey@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.
On Thu, Jan 18, 2018 at 5:16 PM, Stephane Ducasse <stepharo.self@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.demarey@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
Le 18 janv. 2018 à 21:16, Stephane Ducasse <stepharo.self@gmail.com> a écrit :
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?
yes. Only settings directory is different but it did not work very well before. So, if you had settings that were no defaults settings, you will need to store your settings with the new launcher.
tx! On Thu, Jan 18, 2018 at 9:28 PM, Christophe Demarey <christophe.demarey@inria.fr> wrote:
Le 18 janv. 2018 à 21:16, Stephane Ducasse <stepharo.self@gmail.com> a écrit :
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?
yes. Only settings directory is different but it did not work very well before. So, if you had settings that were no defaults settings, you will need to store your settings with the new launcher.
Hi Christoph, One issue I am having is that the Launch without settings is actually running the settings anyway... (it was not the case before). Do you see this as well? On Fri, Jan 19, 2018 at 9:04 AM, Stephane Ducasse <stepharo.self@gmail.com> wrote:
tx!
On Thu, Jan 18, 2018 at 9:28 PM, Christophe Demarey <christophe.demarey@inria.fr> wrote:
Le 18 janv. 2018 Ã 21:16, Stephane Ducasse <stepharo.self@gmail.com> a
écrit :
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?
yes. Only settings directory is different but it did not work very well before. So, if you had settings that were no defaults settings, you will need to store your settings with the new launcher.
-- Mariano http://marianopeck.wordpress.com
Hi Mariano,
Le 25 janv. 2018 à 12:33, Mariano Martinez Peck <marianopeck@gmail.com> a écrit :
Hi Christoph,
One issue I am having is that the Launch without settings is actually running the settings anyway... (it was not the case before).
Do you see this as well?
Hum, yes Iâm able to reproduce that. Could you open a bug entry for this problem (https://github.com/pharo-project/pharo-launcher/issues)? I will take a look at it ASAP. Thanks, Christophe
Le 25 janv. 2018 à 13:54, Christophe Demarey <christophe.demarey@inria.fr> a écrit :
Hi Mariano,
Le 25 janv. 2018 à 12:33, Mariano Martinez Peck <marianopeck@gmail.com> a écrit :
Hi Christoph,
One issue I am having is that the Launch without settings is actually running the settings anyway... (it was not the case before).
Do you see this as well?
Hum, yes Iâm able to reproduce that. Could you open a bug entry for this problem (https://github.com/pharo-project/pharo-launcher/issues)? I will take a look at it ASAP.
Was easy to fix: Name: PharoLauncher-Core-ChristopheDemarey.173 Author: ChristopheDemarey Time: 25 January 2018, 2:22:42.742766 pm UUID: 975f6569-fb1f-0d00-89b5-97830cafd288 Ancestors: PharoLauncher-Core-ChristopheDemarey.172 fixes 2 bugs: - OS detection tu run image for a shell was wrong for OS X - no default preferences option was lost when running image from a shell
Thanks Christophe, Is there a way to update my existing Launcher image or should I wait until you release a future binary (no problem, I can wait). Thanks! On Thu, Jan 25, 2018 at 10:23 AM, Christophe Demarey < christophe.demarey@inria.fr> wrote:
Le 25 janv. 2018 à 13:54, Christophe Demarey < christophe.demarey@inria.fr> a écrit :
Hi Mariano,
Le 25 janv. 2018 à 12:33, Mariano Martinez Peck <marianopeck@gmail.com> a écrit :
Hi Christoph,
One issue I am having is that the Launch without settings is actually running the settings anyway... (it was not the case before).
Do you see this as well?
Hum, yes Iâm able to reproduce that. Could you open a bug entry for this problem (https://github.com/pharo- project/pharo-launcher/issues)? I will take a look at it ASAP.
Was easy to fix:
Name: PharoLauncher-Core-ChristopheDemarey.173 Author: ChristopheDemarey Time: 25 January 2018, 2:22:42.742766 pm UUID: 975f6569-fb1f-0d00-89b5-97830cafd288 Ancestors: PharoLauncher-Core-ChristopheDemarey.172
fixes 2 bugs: - OS detection tu run image for a shell was wrong for OS X - no default preferences option was lost when running image from a shell
-- Mariano http://marianopeck.wordpress.com
Le 25 janv. 2018 à 14:46, Mariano Martinez Peck <marianopeck@gmail.com> a écrit :
Thanks Christophe,
Is there a way to update my existing Launcher image or should I wait until you release a future binary (no problem, I can wait).
Thanks!
On Thu, Jan 25, 2018 at 10:23 AM, Christophe Demarey <christophe.demarey@inria.fr <mailto:christophe.demarey@inria.fr>> wrote:
Le 25 janv. 2018 à 13:54, Christophe Demarey <christophe.demarey@inria.fr <mailto:christophe.demarey@inria.fr>> a écrit :
Hi Mariano,
Le 25 janv. 2018 à 12:33, Mariano Martinez Peck <marianopeck@gmail.com <mailto:marianopeck@gmail.com>> a écrit :
Hi Christoph,
One issue I am having is that the Launch without settings is actually running the settings anyway... (it was not the case before).
Do you see this as well?
Hum, yes Iâm able to reproduce that. Could you open a bug entry for this problem (https://github.com/pharo-project/pharo-launcher/issues <https://github.com/pharo-project/pharo-launcher/issues>)? I will take a look at it ASAP.
Was easy to fix:
Name: PharoLauncher-Core-ChristopheDemarey.173 Author: ChristopheDemarey Time: 25 January 2018, 2:22:42.742766 pm UUID: 975f6569-fb1f-0d00-89b5-97830cafd288 Ancestors: PharoLauncher-Core-ChristopheDemarey.172
fixes 2 bugs: - OS detection tu run image for a shell was wrong for OS X - no default preferences option was lost when running image from a shell
The fastest thing for you would be to open Pharo Launcher, then press cmd + p to open monticello browser. Here, just load PharoLauncher-Core-ChristopheDemarey.172 and it will do the job. PharoLauncher bleedingEdge is also available here: http://files.pharo.org/pharo-launcher/bleedingEdge/ but is not always up to date because the build process also build 64-bits images and loading code in 64-bits image fails at least 4 times / 5 tries, so resulting artifacts are not published. I wonder if I should remove 64-bits build for now.
participants (5)
-
Christophe Demarey -
Juraj Kubelka -
Mariano Martinez Peck -
Serge Stinckwich -
Stephane Ducasse