On Sun, Jun 19, 2011 at 7:27 AM, Pavel Krivanek <[email protected]>wrote:
> Hi, > > I think that the best idea is to have one image for the system developers > and end-users (for example, I almost never used full Pharo so it lost one > tester). On the other hand we should continue with the modularization to > allow to generate headless kernel image, gopher image, basic morphic image > etc. on the request with bootstrapping. To have smallest possible image is > not the main goal of the effort around PharoKernel. The main goal is to have > beauty modular system where all dependencies all described well and packages > can be easily loaded and unloaded. The buildserver can generate all the set > of images for special purposes so it will be more natural then now when we > have two main images. > > +1 > -- Pavel > > > > 18.6.2011 v 22:29, Guillermo Polito <[email protected]>: > > Hi Stef! > > do you mean integrating all them in the Core? Or maybe follow Markus' idea > of having just one image? Maybe that's an important discussion to have too > :). > I can give a hand for the repository stuff. Should we replicate > repositories + metacello configs in order to be able to freeze them, isn't > it? > > Guille > > On Sat, Jun 18, 2011 at 9:59 AM, Stéphane Ducasse <<[email protected]> > [email protected]> wrote: > >> Hi guys >> >> here is a kind of dump of roadmap for 1.4 first level is to make sure that >> we have only one single image. >> >> - load FileSystem >> -> so that we can start to integrate and improve the fileSystem API >> >> - Load shout, Ocompletion, RBEngine (not OB) so that we can change what >> should be changed for RPackage to work >> >> - Ring >> -> so that we can start to integrate it >> >> - Fuel >> -> so that we can deprecate SmartRefStream (there may be a problem >> with mcz (not sure)). >> >> - I want Opal in 1.4 too. >> >> - continue to remove StringHolder hierarchy >> >> - Morphic improvements >> >> Comments are welcomed. >> >> Stef >> >> >> > -- Mariano http://marianopeck.wordpress.com
