Hi I love the PharoLauncher. It helps me to manage my parallel development and projects. We should put a link on the Pharo web site because http://files.pharo.org/platform/launcher/ is arcane. Stef
Stephane Ducasse wrote:
Hi
I love the PharoLauncher.
Pardon my question, I have downloaded it and looked at it, but I don't get it. What does it do / what are the use cases (honest question)? Thanks, Herby
It helps me to manage my parallel development and projects.
We should put a link on the Pharo web site because
http://files.pharo.org/platform/launcher/
is arcane.
Stef
I select the pharo image I want either from jenkins or from the file server and I click and it selects the correct vm download it and then I can keep the 1000 images I have ordered and in a single user interface and I can manage all my images. To me this is really a pain killer. It makes me super efficient and I like that. Stef On Thu, Nov 23, 2017 at 12:56 PM, Herby VojÄÃk <herby@mailbox.sk> wrote:
Stephane Ducasse wrote:
Hi
I love the PharoLauncher.
Pardon my question, I have downloaded it and looked at it, but I don't get it. What does it do / what are the use cases (honest question)?
Thanks, Herby
It helps me to manage my parallel development and projects.
We should put a link on the Pharo web site because
http://files.pharo.org/platform/launcher/
is arcane.
Stef
Every time I investigate an issue from the tracker, I start with a new fresh image. Often its useful to track down which build introduced a bug, so I need to bisect the last 500 builds or so. I select a build version from the "Template" side and create an image named "CaseCCCCC-BBBBB" where CCCCC is the issue number and BBBBB is the build number. I'll quickly end up with a dozen images then delete all but the two either side of where the bug was introduced, to examine the differences between them, and develop a fix for the later build, then testing that fix in the latest build. Also when someone announces a new library, I can quickly create a new image "SomeProject-BBBBB" which I can dip my toes into as I get time available. Nowadays the matching VM is automatically downloaded, which makes it easier to keep up with the latest VM+Image. cheers -ben On 23 November 2017 at 19:56, Herby VojÄÃk <herby@mailbox.sk> wrote:
Stephane Ducasse wrote:
Hi
I love the PharoLauncher.
Pardon my question, I have downloaded it and looked at it, but I don't get it. What does it do / what are the use cases (honest question)?
Thanks, Herby
It helps me to manage my parallel development and projects.
We should put a link on the Pharo web site because
http://files.pharo.org/platform/launcher/
is arcane.
Stef
Hi Herby, normally people use different images for their different projects, different versions, trying things, etc. Which means we end up with many locations on disk, and it can be hard to track. So PharoLauncher is a nice tool where you can download fresh image just by clicking, and you see the list of your local images and can launch them, etc. Peter On Thu, Nov 23, 2017 at 12:56 PM, Herby VojÄÃk <herby@mailbox.sk> wrote:
Stephane Ducasse wrote:
Hi
I love the PharoLauncher.
Pardon my question, I have downloaded it and looked at it, but I don't get it. What does it do / what are the use cases (honest question)?
Thanks, Herby
It helps me to manage my parallel development and projects.
We should put a link on the Pharo web site because
http://files.pharo.org/platform/launcher/
is arcane.
Stef
Thank you all, now I understand it better. Good for lots of "branches". However, I wonder how does it work with the rule I read somewhere: "start each day [of work on a project] with a new image", which means I should not reuse clean new image (as it needs populating from VCSes etc.) nor reuse existing image (I should start with the new one). Or does it combine with some startup-magic described in one of the recent Steph's booklets, the "one start per [new] image" case (but again, one should discriminate projects from each other)? Thanks, Herby Peter Uhnák wrote:
Hi Herby,
normally people use different images for their different projects, different versions, trying things, etc. Which means we end up with many locations on disk, and it can be hard to track. So PharoLauncher is a nice tool where you can download fresh image just by clicking, and you see the list of your local images and can launch them, etc.
Peter
On Thu, Nov 23, 2017 at 12:56 PM, Herby VojÄÃk <herby@mailbox.sk <mailto:herby@mailbox.sk>> wrote:
Stephane Ducasse wrote:
Hi
I love the PharoLauncher.
Pardon my question, I have downloaded it and looked at it, but I don't get it. What does it do / what are the use cases (honest question)?
Thanks, Herby
It helps me to manage my parallel development and projects.
We should put a link on the Pharo web site because
http://files.pharo.org/platform/launcher/ <http://files.pharo.org/platform/launcher/>
is arcane.
Stef
Why don't you try? It does not bite. For me it works in all scenario. I have projects that i manage over several weeks and others I drop day to day. And I have also startup script per versions. Stef On Fri, Nov 24, 2017 at 3:10 PM, Herby VojÄÃk <herby@mailbox.sk> wrote:
Thank you all, now I understand it better. Good for lots of "branches".
However, I wonder how does it work with the rule I read somewhere: "start each day [of work on a project] with a new image", which means I should not reuse clean new image (as it needs populating from VCSes etc.) nor reuse existing image (I should start with the new one). Or does it combine with some startup-magic described in one of the recent Steph's booklets, the "one start per [new] image" case (but again, one should discriminate projects from each other)?
Thanks, Herby
Peter Uhnák wrote:
Hi Herby,
normally people use different images for their different projects, different versions, trying things, etc. Which means we end up with many locations on disk, and it can be hard to track. So PharoLauncher is a nice tool where you can download fresh image just by clicking, and you see the list of your local images and can launch them, etc.
Peter
On Thu, Nov 23, 2017 at 12:56 PM, Herby VojÄÃk <herby@mailbox.sk <mailto:herby@mailbox.sk>> wrote:
Stephane Ducasse wrote:
Hi
I love the PharoLauncher.
Pardon my question, I have downloaded it and looked at it, but I don't get it. What does it do / what are the use cases (honest question)?
Thanks, Herby
It helps me to manage my parallel development and projects.
We should put a link on the Pharo web site because
http://files.pharo.org/platform/launcher/ <http://files.pharo.org/platform/launcher/>
is arcane.
Stef
Stephane Ducasse wrote:
Why don't you try? It does not bite.
For me it works in all scenario. I have projects that i manage over several weeks and others I drop day to day. And I have also startup script per versions.
Maybe I will. The main problem was I didn't what it's good about at all - load image for a version, runs it - what's the "wow it's great" about? Missed part was it loads correct vm; plus makes sense when you have hundreds (I don't). Now it must be combined with the startup script magic to work with long-time projects, but those are also new to me - did not know of them until your booklet, not using them at all yet. Herby
Stef
On Fri, Nov 24, 2017 at 3:10 PM, Herby VojÄÃk<herby@mailbox.sk> wrote:
Thank you all, now I understand it better. Good for lots of "branches".
However, I wonder how does it work with the rule I read somewhere: "start each day [of work on a project] with a new image", which means I should not reuse clean new image (as it needs populating from VCSes etc.) nor reuse existing image (I should start with the new one). Or does it combine with some startup-magic described in one of the recent Steph's booklets, the "one start per [new] image" case (but again, one should discriminate projects from each other)?
Thanks, Herby
Peter Uhnák wrote:
Hi Herby,
normally people use different images for their different projects, different versions, trying things, etc. Which means we end up with many locations on disk, and it can be hard to track. So PharoLauncher is a nice tool where you can download fresh image just by clicking, and you see the list of your local images and can launch them, etc.
Peter
On Thu, Nov 23, 2017 at 12:56 PM, Herby VojÄÃk<herby@mailbox.sk <mailto:herby@mailbox.sk>> wrote:
Stephane Ducasse wrote:
Hi
I love the PharoLauncher.
Pardon my question, I have downloaded it and looked at it, but I don't get it. What does it do / what are the use cases (honest question)?
Thanks, Herby
It helps me to manage my parallel development and projects.
We should put a link on the Pharo web site because
http://files.pharo.org/platform/launcher/ <http://files.pharo.org/platform/launcher/>
is arcane.
Stef
Then do not try :) like that you will never get a chance to know :) Stef On Sun, Nov 26, 2017 at 1:48 PM, Herby VojÄÃk <herby@mailbox.sk> wrote:
Stephane Ducasse wrote:
Why don't you try? It does not bite.
For me it works in all scenario. I have projects that i manage over several weeks and others I drop day to day. And I have also startup script per versions.
Maybe I will. The main problem was I didn't what it's good about at all - load image for a version, runs it - what's the "wow it's great" about? Missed part was it loads correct vm; plus makes sense when you have hundreds (I don't). Now it must be combined with the startup script magic to work with long-time projects, but those are also new to me - did not know of them until your booklet, not using them at all yet.
Herby
Stef
On Fri, Nov 24, 2017 at 3:10 PM, Herby VojÄÃk<herby@mailbox.sk> wrote:
Thank you all, now I understand it better. Good for lots of "branches".
However, I wonder how does it work with the rule I read somewhere: "start each day [of work on a project] with a new image", which means I should not reuse clean new image (as it needs populating from VCSes etc.) nor reuse existing image (I should start with the new one). Or does it combine with some startup-magic described in one of the recent Steph's booklets, the "one start per [new] image" case (but again, one should discriminate projects from each other)?
Thanks, Herby
Peter Uhnák wrote:
Hi Herby,
normally people use different images for their different projects, different versions, trying things, etc. Which means we end up with many locations on disk, and it can be hard to track. So PharoLauncher is a nice tool where you can download fresh image just by clicking, and you see the list of your local images and can launch them, etc.
Peter
On Thu, Nov 23, 2017 at 12:56 PM, Herby VojÄÃk<herby@mailbox.sk <mailto:herby@mailbox.sk>> wrote:
Stephane Ducasse wrote:
Hi
I love the PharoLauncher.
Pardon my question, I have downloaded it and looked at it, but I don't get it. What does it do / what are the use cases (honest question)?
Thanks, Herby
It helps me to manage my parallel development and projects.
We should put a link on the Pharo web site because
http://files.pharo.org/platform/launcher/ <http://files.pharo.org/platform/launcher/>
is arcane.
Stef
Stephane Ducasse wrote:
Then do not try :) like that you will never get a chance to know :)
Could you please explain? I understood your sentence has high dose of homour which I cannot decipher since I lack certain abilities for that. Thanks, Herby
Stef
On Sun, Nov 26, 2017 at 1:48 PM, Herby VojÄÃk<herby@mailbox.sk> wrote:
Stephane Ducasse wrote:
Why don't you try? It does not bite.
For me it works in all scenario. I have projects that i manage over several weeks and others I drop day to day. And I have also startup script per versions.
Maybe I will. The main problem was I didn't what it's good about at all - load image for a version, runs it - what's the "wow it's great" about? Missed part was it loads correct vm; plus makes sense when you have hundreds (I don't). Now it must be combined with the startup script magic to work with long-time projects, but those are also new to me - did not know of them until your booklet, not using them at all yet.
Herby
Stef
On Fri, Nov 24, 2017 at 3:10 PM, Herby VojÄÃk<herby@mailbox.sk> wrote:
Thank you all, now I understand it better. Good for lots of "branches".
However, I wonder how does it work with the rule I read somewhere: "start each day [of work on a project] with a new image", which means I should not reuse clean new image (as it needs populating from VCSes etc.) nor reuse existing image (I should start with the new one). Or does it combine with some startup-magic described in one of the recent Steph's booklets, the "one start per [new] image" case (but again, one should discriminate projects from each other)?
Thanks, Herby
Peter Uhnák wrote:
Hi Herby,
normally people use different images for their different projects, different versions, trying things, etc. Which means we end up with many locations on disk, and it can be hard to track. So PharoLauncher is a nice tool where you can download fresh image just by clicking, and you see the list of your local images and can launch them, etc.
Peter
On Thu, Nov 23, 2017 at 12:56 PM, Herby VojÄÃk<herby@mailbox.sk <mailto:herby@mailbox.sk>> wrote:
Stephane Ducasse wrote:
Hi
I love the PharoLauncher.
Pardon my question, I have downloaded it and looked at it, but I don't get it. What does it do / what are the use cases (honest question)?
Thanks, Herby
It helps me to manage my parallel development and projects.
We should put a link on the Pharo web site because
http://files.pharo.org/platform/launcher/ <http://files.pharo.org/platform/launcher/>
is arcane.
Stef
If you don't try you will not understand what you miss. On Sun, Nov 26, 2017 at 2:10 PM, Herby VojÄÃk <herby@mailbox.sk> wrote:
Stephane Ducasse wrote:
Then do not try :) like that you will never get a chance to know :)
Could you please explain? I understood your sentence has high dose of homour which I cannot decipher since I lack certain abilities for that.
Thanks, Herby
Stef
On Sun, Nov 26, 2017 at 1:48 PM, Herby VojÄÃk<herby@mailbox.sk> wrote:
Stephane Ducasse wrote:
Why don't you try? It does not bite.
For me it works in all scenario. I have projects that i manage over several weeks and others I drop day to day. And I have also startup script per versions.
Maybe I will. The main problem was I didn't what it's good about at all - load image for a version, runs it - what's the "wow it's great" about? Missed part was it loads correct vm; plus makes sense when you have hundreds (I don't). Now it must be combined with the startup script magic to work with long-time projects, but those are also new to me - did not know of them until your booklet, not using them at all yet.
Herby
Stef
On Fri, Nov 24, 2017 at 3:10 PM, Herby VojÄÃk<herby@mailbox.sk> wrote:
Thank you all, now I understand it better. Good for lots of "branches".
However, I wonder how does it work with the rule I read somewhere: "start each day [of work on a project] with a new image", which means I should not reuse clean new image (as it needs populating from VCSes etc.) nor reuse existing image (I should start with the new one). Or does it combine with some startup-magic described in one of the recent Steph's booklets, the "one start per [new] image" case (but again, one should discriminate projects from each other)?
Thanks, Herby
Peter Uhnák wrote:
Hi Herby,
normally people use different images for their different projects, different versions, trying things, etc. Which means we end up with many locations on disk, and it can be hard to track. So PharoLauncher is a nice tool where you can download fresh image just by clicking, and you see the list of your local images and can launch them, etc.
Peter
On Thu, Nov 23, 2017 at 12:56 PM, Herby VojÄÃk<herby@mailbox.sk <mailto:herby@mailbox.sk>> wrote:
Stephane Ducasse wrote:
Hi
I love the PharoLauncher.
Pardon my question, I have downloaded it and looked at it, but I don't get it. What does it do / what are the use cases (honest question)?
Thanks, Herby
It helps me to manage my parallel development and projects.
We should put a link on the Pharo web site because
http://files.pharo.org/platform/launcher/ <http://files.pharo.org/platform/launcher/>
is arcane.
Stef
So, I try it on my CentOS 7 64 bit and... as there is no 64 bit version of the launcher... pharo6-64-ui PharoLauncher.image This interpreter (vers. 68021) cannot read image file (vers. 6521). Press CR to quit... How is one using the launcher for 64 bit stuff? Phil On Sun, Nov 26, 2017 at 9:45 PM, Stephane Ducasse <stepharo.self@gmail.com> wrote:
If you don't try you will not understand what you miss.
On Sun, Nov 26, 2017 at 2:10 PM, Herby VojÄÃk <herby@mailbox.sk> wrote:
Stephane Ducasse wrote:
Then do not try :) like that you will never get a chance to know :)
Could you please explain? I understood your sentence has high dose of homour which I cannot decipher since I lack certain abilities for that.
Thanks, Herby
Stef
On Sun, Nov 26, 2017 at 1:48 PM, Herby VojÄÃk<herby@mailbox.sk> wrote:
Stephane Ducasse wrote:
Why don't you try? It does not bite.
For me it works in all scenario. I have projects that i manage over several weeks and others I drop day to day. And I have also startup script per versions.
Maybe I will. The main problem was I didn't what it's good about at
all -
load image for a version, runs it - what's the "wow it's great" about? Missed part was it loads correct vm; plus makes sense when you have hundreds (I don't). Now it must be combined with the startup script magic to work with long-time projects, but those are also new to me - did not know of them until your booklet, not using them at all yet.
Herby
Stef
On Fri, Nov 24, 2017 at 3:10 PM, Herby VojÄÃk<herby@mailbox.sk> wrote:
Thank you all, now I understand it better. Good for lots of
"branches".
However, I wonder how does it work with the rule I read somewhere: "start each day [of work on a project] with a new image", which means I
should
not reuse clean new image (as it needs populating from VCSes etc.) nor reuse existing image (I should start with the new one). Or does it combine with some startup-magic described in one of the recent Steph's booklets, the "one start per [new] image" case (but again, one should discriminate projects from each other)?
Thanks, Herby
Peter Uhnák wrote:
Hi Herby,
normally people use different images for their different projects, different versions, trying things, etc. Which means we end up with many locations on disk, and it can be hard to track. So PharoLauncher is a nice tool where you can download fresh image just by clicking, and you see the list of your local images and can
launch
them, etc.
Peter
On Thu, Nov 23, 2017 at 12:56 PM, Herby VojÄÃk<herby@mailbox.sk <mailto:herby@mailbox.sk>> wrote:
Stephane Ducasse wrote:
Hi
I love the PharoLauncher.
Pardon my question, I have downloaded it and looked at it, but I don't get it. What does it do / what are the use cases (honest question)?
Thanks, Herby
It helps me to manage my parallel development and projects.
We should put a link on the Pharo web site because
http://files.pharo.org/platform/launcher/ <http://files.pharo.org/platform/launcher/>
is arcane.
Stef
On 27 November 2017 at 05:25, phil@highoctane.be <phil@highoctane.be> wrote:
So, I try it on my CentOS 7 64 bit and... as there is no 64 bit version of the launcher...
pharo6-64-ui PharoLauncher.image This interpreter (vers. 68021) cannot read image file (vers. 6521). Press CR to quit...
How is one using the launcher for 64 bit stuff?
Starting with a fresh 64-bit image, install from the Catalog or Monticello repository. http://smalltalkhub.com/#!/~Pharo/PharoLauncher cheers -ben
Phil
On Sun, Nov 26, 2017 at 9:45 PM, Stephane Ducasse <stepharo.self@gmail.com
wrote:
If you don't try you will not understand what you miss.
On Sun, Nov 26, 2017 at 2:10 PM, Herby VojÄÃk <herby@mailbox.sk> wrote:
Stephane Ducasse wrote:
Then do not try :) like that you will never get a chance to know :)
Could you please explain? I understood your sentence has high dose of homour which I cannot decipher since I lack certain abilities for that.
Thanks, Herby
Stef
On Sun, Nov 26, 2017 at 1:48 PM, Herby VojÄÃk<herby@mailbox.sk> wrote:
Stephane Ducasse wrote:
Why don't you try? It does not bite.
For me it works in all scenario. I have projects that i manage over several weeks and others I drop day to day. And I have also startup script per versions.
Maybe I will. The main problem was I didn't what it's good about at
all -
load image for a version, runs it - what's the "wow it's great" about? Missed part was it loads correct vm; plus makes sense when you have hundreds (I don't). Now it must be combined with the startup script magic to work with long-time projects, but those are also new to me - did not know of them until your booklet, not using them at all yet.
Herby
Stef
On Fri, Nov 24, 2017 at 3:10 PM, Herby VojÄÃk<herby@mailbox.sk> wrote:
Thank you all, now I understand it better. Good for lots of
"branches".
However, I wonder how does it work with the rule I read somewhere: "start each day [of work on a project] with a new image", which means I
should
not reuse clean new image (as it needs populating from VCSes etc.) nor reuse existing image (I should start with the new one). Or does it combine with some startup-magic described in one of the recent Steph's booklets, the "one start per [new] image" case (but again, one should discriminate projects from each other)?
Thanks, Herby
Peter Uhnák wrote:
Hi Herby,
normally people use different images for their different projects, different versions, trying things, etc. Which means we end up with many locations on disk, and it can be hard to track. So PharoLauncher is a nice tool where you can download fresh image just by clicking, and you see the list of your local images and can
launch
them, etc.
Peter
On Thu, Nov 23, 2017 at 12:56 PM, Herby VojÄÃk<herby@mailbox.sk <mailto:herby@mailbox.sk>> wrote:
Stephane Ducasse wrote:
Hi
I love the PharoLauncher.
Pardon my question, I have downloaded it and looked at it, but I don't get it. What does it do / what are the use cases (honest question)?
Thanks, Herby
It helps me to manage my parallel development and projects.
We should put a link on the Pharo web site because
http://files.pharo.org/platform/launcher/ <http://files.pharo.org/platform/launcher/>
is arcane.
Stef
Hi Phil,
Le 26 nov. 2017 à 22:25, phil@highoctane.be a écrit :
So, I try it on my CentOS 7 64 bit and... as there is no 64 bit version of the launcherâ¦
Right. Canât you use the 32 bit version? Anyway, I think it would be good to have a 64 bit version. Could you open an issue for that please?
pharo6-64-ui PharoLauncher.image This interpreter (vers. 68021) cannot read image file (vers. 6521). Press CR to quit...
How is one using the launcher for 64 bit stuff?
Phil
On Sun, Nov 26, 2017 at 9:45 PM, Stephane Ducasse <stepharo.self@gmail.com <mailto:stepharo.self@gmail.com>> wrote: If you don't try you will not understand what you miss.
On Sun, Nov 26, 2017 at 2:10 PM, Herby VojÄÃk <herby@mailbox.sk <mailto:herby@mailbox.sk>> wrote:
Stephane Ducasse wrote:
Then do not try :) like that you will never get a chance to know :)
Could you please explain? I understood your sentence has high dose of homour which I cannot decipher since I lack certain abilities for that.
Thanks, Herby
Stef
On Sun, Nov 26, 2017 at 1:48 PM, Herby VojÄÃk<herby@mailbox.sk <mailto:herby@mailbox.sk>> wrote:
Stephane Ducasse wrote:
Why don't you try? It does not bite.
For me it works in all scenario. I have projects that i manage over several weeks and others I drop day to day. And I have also startup script per versions.
Maybe I will. The main problem was I didn't what it's good about at all - load image for a version, runs it - what's the "wow it's great" about? Missed part was it loads correct vm; plus makes sense when you have hundreds (I don't). Now it must be combined with the startup script magic to work with long-time projects, but those are also new to me - did not know of them until your booklet, not using them at all yet.
Herby
Stef
On Fri, Nov 24, 2017 at 3:10 PM, Herby VojÄÃk<herby@mailbox.sk <mailto:herby@mailbox.sk>> wrote:
Thank you all, now I understand it better. Good for lots of "branches".
However, I wonder how does it work with the rule I read somewhere: "start each day [of work on a project] with a new image", which means I should not reuse clean new image (as it needs populating from VCSes etc.) nor reuse existing image (I should start with the new one). Or does it combine with some startup-magic described in one of the recent Steph's booklets, the "one start per [new] image" case (but again, one should discriminate projects from each other)?
Thanks, Herby
Peter Uhnák wrote:
Hi Herby,
normally people use different images for their different projects, different versions, trying things, etc. Which means we end up with many locations on disk, and it can be hard to track. So PharoLauncher is a nice tool where you can download fresh image just by clicking, and you see the list of your local images and can launch them, etc.
Peter
On Thu, Nov 23, 2017 at 12:56 PM, Herby VojÄÃk<herby@mailbox.sk <mailto:herby@mailbox.sk> <mailto:herby@mailbox.sk <mailto:herby@mailbox.sk>>> wrote:
Stephane Ducasse wrote:
Hi
I love the PharoLauncher.
Pardon my question, I have downloaded it and looked at it, but I don't get it. What does it do / what are the use cases (honest question)?
Thanks, Herby
It helps me to manage my parallel development and projects.
We should put a link on the Pharo web site because
http://files.pharo.org/platform/launcher/ <http://files.pharo.org/platform/launcher/> <http://files.pharo.org/platform/launcher/ <http://files.pharo.org/platform/launcher/>>
is arcane.
Stef
Christophe I think that we should remove the blessed folder. Setf On Tue, Nov 28, 2017 at 5:36 PM, Christophe Demarey <christophe.demarey@inria.fr> wrote:
Hi Phil,
Le 26 nov. 2017 à 22:25, phil@highoctane.be a écrit :
So, I try it on my CentOS 7 64 bit and... as there is no 64 bit version of the launcherâ¦
Right. Canât you use the 32 bit version? Anyway, I think it would be good to have a 64 bit version. Could you open an issue for that please?
pharo6-64-ui PharoLauncher.image This interpreter (vers. 68021) cannot read image file (vers. 6521). Press CR to quit...
How is one using the launcher for 64 bit stuff?
Phil
On Sun, Nov 26, 2017 at 9:45 PM, Stephane Ducasse <stepharo.self@gmail.com> wrote:
If you don't try you will not understand what you miss.
On Sun, Nov 26, 2017 at 2:10 PM, Herby VojÄÃk <herby@mailbox.sk> wrote:
Stephane Ducasse wrote:
Then do not try :) like that you will never get a chance to know :)
Could you please explain? I understood your sentence has high dose of homour which I cannot decipher since I lack certain abilities for that.
Thanks, Herby
Stef
On Sun, Nov 26, 2017 at 1:48 PM, Herby VojÄÃk<herby@mailbox.sk> wrote:
Stephane Ducasse wrote:
Why don't you try? It does not bite.
For me it works in all scenario. I have projects that i manage over several weeks and others I drop day to day. And I have also startup script per versions.
Maybe I will. The main problem was I didn't what it's good about at all - load image for a version, runs it - what's the "wow it's great" about? Missed part was it loads correct vm; plus makes sense when you have hundreds (I don't). Now it must be combined with the startup script magic to work with long-time projects, but those are also new to me - did not know of them until your booklet, not using them at all yet.
Herby
Stef
On Fri, Nov 24, 2017 at 3:10 PM, Herby VojÄÃk<herby@mailbox.sk> wrote:
Thank you all, now I understand it better. Good for lots of "branches".
However, I wonder how does it work with the rule I read somewhere: "start each day [of work on a project] with a new image", which means I should not reuse clean new image (as it needs populating from VCSes etc.) nor reuse existing image (I should start with the new one). Or does it combine with some startup-magic described in one of the recent Steph's booklets, the "one start per [new] image" case (but again, one should discriminate projects from each other)?
Thanks, Herby
Peter Uhnák wrote:
Hi Herby,
normally people use different images for their different projects, different versions, trying things, etc. Which means we end up with many locations on disk, and it can be hard to track. So PharoLauncher is a nice tool where you can download fresh image just by clicking, and you see the list of your local images and can launch them, etc.
Peter
On Thu, Nov 23, 2017 at 12:56 PM, Herby VojÄÃk<herby@mailbox.sk <mailto:herby@mailbox.sk>> wrote:
Stephane Ducasse wrote:
Hi
I love the PharoLauncher.
Pardon my question, I have downloaded it and looked at it, but I don't get it. What does it do / what are the use cases (honest question)?
Thanks, Herby
It helps me to manage my parallel development and projects.
We should put a link on the Pharo web site because
http://files.pharo.org/platform/launcher/ <http://files.pharo.org/platform/launcher/>
is arcane.
Stef
Le 28 nov. 2017 à 22:00, Stephane Ducasse <stepharo.self@gmail.com> a écrit :
Christophe
I think that we should remove the blessed folder.
After we moved the file-server, I will do a big cleanup of pharo launcher files. I think I will only publish OS-packages (win,linux, OS X) and create a pharo-luacher folder at the root of the file-server. It will be more clear.
On 23 Nov 2017, at 12:56 , Herby VojÄÃk <herby@mailbox.sk> wrote:
Pardon my question, I have downloaded it and looked at it, but I don't get it. What does it do / what are the use cases (honest question)?
I also was completely confused by what the launcher was for. And when I tried it, it did not seem to load. Now that I know what it is for, it is very useful. So I will try to explain the basics. The launcher is not a project that you load into your Pharo image. It is stand-alone command line tool that you use for creating and managing your images. It lets you quickly and easily: download the latest pre-built Pharo image and create your own copy. you can choose from Pharo 6.1 stable or Pharo 7 development You can choose 64 or 32 bit manage multiple images on your computer Launch (with the right VM), with and without your personal settings, Delete old images run multiple images in parallel The âSave as ...â command in Pharo is unfortunately not at this time compatible with the launcher, so if you create a new image using Save As ..., it will not show up in the launcher. You should be able to launch the launcher by double-clicking on it from your OS. In MacOS, I have it in the dock. Perhaps someone can put some text like what I have written above on the web page? We often assume that people know ... well, they mostly donât! Andrew
On 29-11-17 11:39, Prof. Andrew P. Black wrote:
The âSave as ...â command in Pharo is unfortunately /not /at this time compatible with the launcher, so if you create a new image using Save As ..., it will not show up in the launcher.
PharoLauncher however can copy a saved image and create a new one from it. That is not exactly the same, as you need to start by creating a copy if you want to be able to snapshot and go back to the original version. Copying the image with PharoLauncher also provides you with a new, empty, packageCache (unless you selected you share that). Having the snapshots of an image show up in the launcher would actually be a pretty useful feature. The interaction with different git branches gets interesting then. Stephan
Unless we talk about a diffident launcher I am not aware of. Pharo launcher is both a GUI last time I checked and loadable inside any image. So technically speaking you donât need neither the GUI nor the command line. You can fully integrate it and automate it with your own project and then publish that project to Package Browser so that downloads and installs from inside the image with a single click. Itâs just regular Pharo code like anything else. On Wed, 29 Nov 2017 at 12:41, Prof. Andrew P. Black <black@cs.pdx.edu> wrote:
On 23 Nov 2017, at 12:56 , Herby VojÄÃk <herby@mailbox.sk> wrote:
Pardon my question, I have downloaded it and looked at it, but I don't get it. What does it do / what are the use cases (honest question)?
I also was completely confused by what the launcher was for. And when I tried it, it did not seem to load. Now that I know what it is for, it is very useful. So I will try to explain the basics.
The launcher is *not* a project that you load into your Pharo image. It is stand-alone command line tool that you use for creating and managing your images. It lets you quickly and easily:
- download the latest pre-built Pharo image and create your own copy. - you can choose from Pharo 6.1 stable or Pharo 7 development - You can choose 64 or 32 bit - manage multiple images on your computer - Launch (with the right VM), with and without your personal settings, - Delete old images - run multiple images in parallel
The âSave as ...â command in Pharo is unfortunately *not *at this time compatible with the launcher, so if you create a new image using Save As ..., it will not show up in the launcher.
You should be able to launch the launcher by double-clicking on it from your OS. In MacOS, I have it in the dock.
Perhaps someone can put some text like what I have written above on the web page? We often assume that people know ... well, they mostly donât!
Andrew
Your email made me try Pharo Launcher. I love it too! It replaces all my scripts to download the VM and the last images. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Nov 23, 2017, at 5:51 AM, Stephane Ducasse <stepharo.self@gmail.com> wrote:
Hi
I love the PharoLauncher. It helps me to manage my parallel development and projects.
We should put a link on the Pharo web site because
http://files.pharo.org/platform/launcher/
is arcane.
Stef
participants (10)
-
Alexandre Bergel -
Ben Coman -
Christophe Demarey -
Dimitris Chloupis -
Herby VojÄÃk -
Peter Uhnák -
phil＠highoctane.be -
Prof. Andrew P. Black -
stephan -
Stephane Ducasse