Nice (it is also a single configuration load). BTW, there is something broken with the browser/non-browser detection of the Shared Smalltalk Workspaces server, to force HTML rendering and proper syntax coloring, you can use: http://ws.stfx.eu/41W9PEFII4UW?format=html On 18 Mar 2014, at 11:13, Damien Cassou <damien.cassou@gmail.com> wrote:

On Tue, Mar 18, 2014 at 11:08 AM, Pharo4Stef <pharo4Stef@free.fr> wrote: Does any of you implement such behavior? Else I will do it.

Martin wrote a nice script for Epicea that he describes as:

""" You can create a file with this content in your preferences directory*. This (cute) script installs Epicea after 3 seconds after opening a fresh image; during that time, a big centered "cancel" button is displayed to help you in a eventual case in which you don't want Epicea to be loaded.

*: the preferences directory is a mechanism of Pharo offers for personal scripts. You can know your preferences directory by evaluating this code: FileLocator preferences asFileReference.

"""

http://smalltalkhub.com/#!/~MartinDias/Epicea

-- Damien Cassou http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

yes but my projects are often not related. I will try to add a menu in the configurationBrowser to generate nice information such as Gofer it smalltalkhubUser: 'MartinDias' project: 'Epicea'; configuration; loadStable. Gofer it smalltalkhubUser: 'DamienCassou' project: 'Pier-Gutemberg'; package: 'ConfigurationOfCatalog'; load. Stef On 18 Mar 2014, at 11:14, Sven Van Caekenberghe <sven@stfx.eu> wrote:

One way to do this (restore all your own stuff in a new image) is to use a single configuration ...

On 18 Mar 2014, at 11:08, Pharo4Stef <pharo4Stef@free.fr> wrote:

...

Hi guys

I’m starting to get bored to always reload my projects in new images. I would like to have a simple button to say Save script to reload on a project

Does any of you implement such behavior? Else I will do it.

Stef

On Tue, Mar 18, 2014 at 11:46 AM, Sven Van Caekenberghe <sven@stfx.eu>wrote:

On 18 Mar 2014, at 11:42, Pharo4Stef <pharo4Stef@free.fr> wrote:

...

yes but my projects are often not related.

What I mean is: make a meta Metacello configuration, ConfigurationOfStef, that loads everything you need by dependency.

Once, Mariano convinced me to do it this way and it was fine. Additionally, Metacello groups can be used to define multiple unrelated "working environments". Currently, I like to use .st startup scripts to define automatic small actions, and trigger Metacello for more complex actions. Martín

Le 18/03/2014 15:10, Ben Coman a écrit :

Maybe the Configuration Browser could tag configurations to be loaded in every new image. If the Startup scripts set a shared global package cache directory [1], that information could be stored there.

Hum, then this means that if you work on multiple projects in separate images, all of them will load the same configurations?

btw, How common is it to have a shared global package cache directory. Should that be default? What would detract from that?

I don't know but it seems that recent Pharo3 build have a tendency to create (or to share) a common cache. Or does that happens when you export settings? Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95