On Sun, Jan 10, 2010 at 5:58 PM, Tudor Girba <tudor.girba@gmail.com> wrote:
Hi,

It looks like Metacello-Platform and Ocompletion are dirty. Any reason
for why the changes are not in the Monticello repository?

Thanks Doru for the report. For Metacello-Platform, it is correct it is dirty. I am having some problems with the progress bar when running Pharo from comman d line and build the images. We are trying to fix this with Dale but for the moment (as I needed to build Pharo image) I disable the posgress bar in that way.

Regarding OCompletion, I have no idea at all. I cc Romain to see if he can help us.

Cheers

Mariano

Cheers,
Doru

On 9 Jan 2010, at 18:13, Mariano Martinez Peck wrote:

> Hi Folks/Beta-Testers!
>
> I have prepare a new PharoDev image. This image, has same
> differences with the previous ones that you should know:
>
> 1) This is the first Dev image I ever prepare. I adapt to Mac OS
> Damien's bash scripts to build them and I also cleanup all the
> Squeak stuff from those bash scripts. So, maybe there are some
> problems. Forgive me if this is the case. I would like you to check,
> not only the Image in itself but also the zip. The package.txt,
> changelog, the fonts, etc.
>
> 2) This image puts TrueType fonts again. We won't put StrikeFonts or
> DejaVu package until there is big bug with them. We know those fonts
> are faster, but still a bit buggy. If you fix those issues, cool!
>
> 3) This image DOES NOT include O2. I know there are a lot of people
> who use it (mostly in Moose), but unfortunately, this was a decision
> taken. O2 depends and overrides OB making this more unstable
> sometimes. The same as the TrueType, we will put O2 again when this
> can be perfectly load in a PharoCore image without anything about OB.
> Sorry, but we rather affect only O2 users and not all. If you want
> packages support, then help in O2 development.
>
> 4) In previous Dev images only tests from PharoCore were included.
> Now, it also includes the tests from the external packages loaded.
>
> 5) This image was build using Metacello configurations. If you want,
> compare the installScript.st from this image to the previous one.
>
> 6) There is no Web image this time. If you want to install Seaside
> 2.8.4 evaluate:
>
> Gofer new
> � � squeaksource: 'MetacelloRepository';
> � � package: 'ConfigurationOfSeaside28';
> � � load.
>
> (Smalltalk at: #ConfigurationOfSeaside28) load
>
> And if you want Seaside 3.0 evaluate:
>
> Gofer new
> � � squeaksource: 'MetacelloRepository';
> � � package: 'ConfigurationOfSeaside30';
> � � load.
>
> (Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion
>
> However, I am not sure if this is perfectly working in Pharo.
>
>
>
> Ok .... Here is the link: �https://gforge.inria.fr/frs/download.php/25156/pharo1.0-10505-rc1dev10.01.1.zip
>
> I will wait a couple of days now and I will also start to use this
> image for my development. If there are issues, report them. If we
> have big issues, this image is not release. On the other hand, if it
> works well, we release it.
> _______________________________________________
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

--
www.tudorgirba.com

"Every thing has its own flow."




_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project