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
