"@Kilon:
�� Integrating PharoLauncher in the standard image would not make sense. Then I use PharoLauncher to download
�� an image with a prepackaged PharoLauncher, ...
��
�� If you mean that it should be the default tool to download when getting Pharo 4.0 or Pharo 3.0 from the
�� download page or from zeroconf then I would agree. Maybe some more help is needed for Pharo newbees then."

Actually it makes perfect sense, think about it. We have configuration browser. Now go to your pharolauncher and enable development mode, open world menu and bingo pharolauncher is there as a tool and i think thats great already. So you have 2 tools in your image 1) Configuration Browser that allows you to install pharo libraries / apps 2) PharoLauncher that allows you to download images . Both accessed in world menu and this functionality is already provided by PharoLauncher.

"

I don't think Kilon was referring to PhaoLauncher, but to "World > System > Software update"

cheers -ben"

Yeap correct Ben I was referring to Software Update, as a matter of fact I loved PharoLauncher so much I became a contributor and added documentation about it in the new PBE.

On Tue, Mar 24, 2015 at 4:43 PM, Norbert Hartl <norbert@hartl.name> wrote:

> Am 24.03.2015 um 13:02 schrieb Sean P. DeNigris <sean@clipperadams.com>:
>
> NorbertHartl wrote
>> What would be better using PharoLauncher?
>
> I was a hold out, but I've finally started using it and it's really nice.
> For things that don't have an automated build process, it's much better than
> downloading from file.pharo.org by hand. You can set the folder to which the
> images get saved, and choose to make new images from e.g. Pharo 4, 3, 2,
> moose, anything on the contribution CI server, and a few others.
>
> I really like Peter's idea to act from a startup script based on the image
> name. That sounds like a powerful combination.
>

Oh, I didn't know that you can choose the folder where the images live. I might take another peek at it. But then I'm using something like that for a very long time.

- make a folder projects in you home directory
- in that folder create symlink to any of your smalltalk project directory that you are working at the moment
- drop that folder in the dock
- you click the icon on the dock, a list of projects pops up, you select one and you get the contents of that the directory. You click on an image and it starts

So I'm not sure I'll gain something but I will try again.

Norbert