[BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

Hi folks. We are proud to announce the (hopefully) last RC3 for Pharo 1.0.

This image is based in PharoCore-1.0-10515rc3. The image also contain lot of fixes and improvements of external packages:

These, are the fixed issues of the external tools:

OB:  Issues 1891, 1748, 1670, 1667, 1705, 1667

O2: issues 1887, 1312, 1429, 1886, 2073

New Inspector:  issues 1783, 1499

Refactoring Browser:  issue 2108

The link is: https://gforge.inria.fr/frs/download.php/26680/Pharo-1.0-10515-rc3dev10.03.1.zip

Cheers

Mariano

I see that the installScript uses ConfigurationOfMetacello from
gemsource metacello repository instead of Metacello repository. Given
that this will be the final release of 1.0, shouldn't we copy
ConfigurationOfMetacello to squeaksource/MetacelloRepository so that the
package registered in monticello is this instead of the gemstone one.
This repo for ConfigurationOfMetacello overrides the one of PharoCore
that points to squeaksource.

Dale, can you put this version in squeaksource. The release is very
close and anyway it will be shipped in Pharo dev 1.0, so will reach a
lot of people, even if not on squeaksource

Cheers
>
> Mariano
>
> _______________________________________________
> Pharo-users mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users

--
Miguel Cobá
http://miguel.leugim.com.mx

El sáb, 20-03-2010 a las 20:40 +0100, Mariano Martinez Peck escribió:

> Hi folks. We are proud to announce the (hopefully) last RC3 for Pharo
> 1.0.

- What happened to the background image?

- The text on: DEVImageWorkspaces openExternalProjectWorkspace at the
end says:

"If you want an object database, you can install Magma
(http://wiki.squeak.org/squeak/2665).
For the installation instuctions check the method: ConfigurationOfMagma
>> workspace    "

Can we change this to:

"Magma is an object oriented database for Smalltalk. It supports
replication, high-availability fault-tolerance and multiuser
capabilities (http://wiki.squeak.org/squeak/2665). You can install it
with:

Gofer new
 squeaksource: 'MetacelloRepository';
 package: 'ConfigurationOfMagma';
 load.

((Smalltalk at: #ConfigurationOfMagma) project latestVersion) load

"You can also review the method ConfigurationOfMagma>>workspace for
alternative installation methods for Magma.

- Also, in the same workspace:
       Gofer new
               squeaksource: 'Moose';
               package: 'ConfigurationOfMoose';
       load.

       (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault.

Should be:
       Gofer new
               squeaksource: 'Moose';
               package: 'ConfigurationOfMoose';
       load.

       (Smalltalk at: #ConfigurationOfMoose) loadDefault

As the other examples use the methods directly and not the perform
indirection.

Cheers

>
> _______________________________________________
> Pharo-users mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users

--
Miguel Cobá
http://miguel.leugim.com.mx

Mariano,

I am seriously considering releasing 1.0-beta.25 today ... I have smacked the heck out Metacello over the last three days without issues so I'm thinking I can let this puppy out the door:)...Especially if it will clean up the release process...

One other point I have noticed is that the following configurations aren't pointing to the correct repository:

 ConfigurationOfOmniBrowser
 ConfigurationOfRefactoringBrowser
 ConfigurationOfOCompletion
 ConfigurationOfShout
 ConfigurationOfProfStef

They all reference the package-cache instead of SqueakSource MetacelloRepository.

I'm assuming this is because they were in your package-cache when you did the build.

I think this is happening because of a recent change in the sorting order for Gofer ...

For the build process you may want to either make sure your package-cache is empty

or use disablePackageCache in the places where you explicitly load a Configuration or perhaps something else?

Dale

----- "Mariano Martinez Peck" <[hidden email]> wrote:

| >
| > I see that the installScript uses ConfigurationOfMetacello from
| > gemsource metacello repository instead of Metacello repository.
| Given
| > that this will be the final release of 1.0, shouldn't we copy
| > ConfigurationOfMetacello to squeaksource/MetacelloRepository so that
| the
| > package registered in monticello is this instead of the gemstone
| one.
| > This repo for ConfigurationOfMetacello overrides the one of
| PharoCore
| > that points to squeaksource.
| >
| > Dale, can you put this version in squeaksource. The release is very
| > close and anyway it will be shipped in Pharo dev 1.0, so will reach
| a
| > lot of people, even if not on squeaksource
| >
| >

| Yes. This is because I added the ImageForDevelopers in the group. With
| that,
| when running headless I have the problem with the progress Bar.
| Then, i needed to use the silntly method, which is in Metacello
| beta.25
| which is not released yet. That's why I have to put the other one.
|
| Don't worry that beta.25 will be then correctly uploaded and released.
| After
| that, the installScript will be even simpler as I won't need to
| install
| Metacello manually, but with the ensureMetacello ;)
|
| Cheers
|
| Mariano
|
|
|
| > Cheers
| > >
| > > Mariano
| > >
| > > _______________________________________________

| > > Pharo-users mailing list
| > > [hidden email]
| > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users
| >
| > --
| > Miguel Cobá
| > http://miguel.leugim.com.mx
| >
| >
|

| _______________________________________________
| Pharo-project mailing list
| [hidden email]
| http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list

[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project