Indeed I'm all in favor to have ConfigurationOf in the image because they are metaData of the packages and projects!!! I do not understand why UI concerns show up into structure of the system. I do not see why having a long list is a problem: there is a search behavior there is a smart group So it would be good not to mix systematically this issue. I'm quite sure that we can open Nautilus on an empty RBBrowserEnvironment and it will work so? Let us move on. I spent time rebuilding from scratch some configurations and I will continue because I want to create a Pharo image from a set of projects and I must have configuration for doing so. Stef
I agree with this. In particular, the configuration classes offer extra information that can be used by smart browsers. We need them.
Cheers, Doru
On Fri, Oct 25, 2013 at 3:18 PM, Christophe Demarey <Christophe.Demarey@inria.fr> wrote: Why do we need to remove configurations of projects loaded into the image? I would say the opposite: all projects in the image should have their configuration loaded. It is part of the project.
Le 25 oct. 2013 à 14:00, GitHub a écrit :
12005 unload BaselineOfFileTree, BaselineOfMetacello https://pharo.fogbugz.com/f/cases/12005
-- www.tudorgirba.com
"Every thing has its own flow"