I suggest to have at least one next image - without everything what can be safely unloaded. For the next cleaning and shrinking purposes. Of course if you want to have similar sequence of automatically build images like the KernelImage.
-- Pavel On Mon, Nov 3, 2008 at 10:49 AM, Adrian Lienhard <[EMAIL PROTECTED]> wrote: > thanks, I forgot to list the one-click image. I added the plan to > http://code.google.com/p/pharo/wiki/Milestones > > Concerning terminology, I suggest to name the official Pharo image, which > will be packaged as a one-click image, "Pharo-IDE". And the one where the > actual development of Pharo takes place is named Pharo-CORE. Using DEV is > ambiguous because its not clear whether this image is supposed to develop > applications or Pharo itself. > > Adrian > > > On Nov 3, 2008, at 10:15 , Damien Cassou wrote: > > On Sun, Nov 2, 2008 at 1:02 PM, Adrian Lienhard <[EMAIL PROTECTED]> wrote: >> >>> Is there anything important we missed? Any suggestions? >>> >> >> - review pharo-dev images and make comments so that the official Pharo >> image contains some dev tools and pharo-dev becomes useless. >> >> -- >> Damien Cassou >> Peter von der Ahé: «I'm beginning to see why Gilad wished us good >> luck». (http://blogs.sun.com/ahe/entry/override_snafu) >> >> _______________________________________________ >> 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 >
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
