On Wed, Mar 17, 2010 at 3:30 PM, Esteban Lorenzano <[email protected]>wrote:
> Hi Adrian, > > > On 2010-03-17 11:15:10 -0300, Adrian Lienhard <[email protected]> said: > > Hi Esteban >> >> Looks cool! I haven't had time to test it out in depth yet, but here three >> questions: >> >> - does it keep memory of which projects are loaded? Is this what you refer >> to as "managed projects"? >> > > Yes, it keeps a list of "managed projects" (with itself as the first one) > so it can check for new versions, etc. For 1.1 would be cool to include, maybe, to implement the cleanUp method...regarding the latests integrations. There you can flush all managed projects. > > - would it make sense to integrate it into Gofer? >> > > I don't know... this is a "mixer" between Gofer and Metacello. If we > integrate it with Gofer core, suddenly we wil be creating a new dependence > package to add to core (Metacello)... of course, Metacello can be loaded "at > first project load" just like now "at first configuration loaded", but I > don't know if this is desirable... your choice more than mine :) > What will be cool is to include the gofer project loader into PharoDev > distributions. > > -1 to put it in Gofer. In my opinion, it is perfect as it is. +9999 to put it in PharoDev, but not in 1.0. We can put it when we start building PharoDev 1.1 > > > > Cheers, > Esteban > > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
