Updated the download page

http://www.pharo-project.org/pharo-download

Instead of 1.4 and 2.0 it now lists 2.0 and 3.0

2013/3/22 Marcus Denker <[hidden email]>:
>
> http://www.pharo-project.org/pharo-download
> Instead of 1.4 and 2.0 it now lists 2.0 and 3.0

Markus, it should say there the 3.0 is Alpha.

If somebody goes straight to that URI, unless they look at the sidebar
(which is unlikely) they may end up downloading an unstable version.

Regards!

On Mar 22, 2013, at 3:34 PM, Esteban A. Maringolo <[hidden email]> wrote:

Done

        Marcus

Hi all,

I migrated my project to Pharo 2.0 and made configurations to make it work. This project uses the following configurations, that are not yet in the "verified" repository:
        SeasideRest
        Seaside 3.1 (Welcome + Zinc)
        Magritte 3.0
        PetitParser
        Grease

> PetitParser was not updated to the latest version. I added a version 1.6.1 and made it the stable version for pharo 2.0.
> I updated Grease to the latest version.

> I adapted Magritte 3.0 and Seaside Rest, so that it now uses Seaside 3.1.

> I adapted Seaside 3.1, so that it loads the latest version of today, and fixed some dependencies. I did not test this configuration fully, as I only tested the parts that were needed for my project. I know that there are some dependencies to untested parts as well. There is some unfinished work here, I posted more details on the Seaside dev list.

Since the configuration of Seaside 3.1 is still unfinished: contact me if you would like to have this configuration, or SeasideRest and/or Magritte, as they depend on Seaside 3.1.

The configurations of Grease and PetitParser are done and load properly. I included them here. Can I put them in the verified repository or does someone wants to check them and upload them here?



Cheers,
Diego

2013/3/22 Diego Lont <[hidden email]>:
> Hi all,
>
> I migrated my project to Pharo 2.0 and made configurations to make it work. This project uses the following configurations, that are not yet in the "verified" repository:
>         SeasideRest
>         Seaside 3.1 (Welcome + Zinc)
>         Magritte 3.0
>         PetitParser
>         Grease

Can you share a workspace with the statements to load those?

I tried to do that in the 2.0 and failed successfully :), so I stuck
with 1.4 until I have more time to read and understand the
differences.


Esteban A. Maringolo

On Mar 22, 2013, at 4:11 PM, Esteban A. Maringolo wrote:

ConfigurationOfMyProject project bleedingEdge load

I downloaded the Pharo 2.0 one click.
Then I manually load the configurations I adapted first from my local disk. Load the two I send before and these 4. So you have 6 manual configurations.




Then do "ConfigurationOfMyProject project bleedingEdge load", and it should load Seaside-Welcome.

If you get an error: cannot resolve configuration, you forgot to load a configuration.

Cheers,
Diego

>>
>
> Since the configuration of Seaside 3.1 is still unfinished: contact me if you would like to have this configuration, or SeasideRest and/or Magritte, as they depend on Seaside 3.1.
>
> The configurations of Grease and PetitParser are done and load properly. I included them here. Can I put them in the verified repository or does someone wants to check them and upload them here?
> <ConfigurationOfGrease-DiegoLont.189.mcz><ConfigurationOfPetitParser-DiegoLont.30.mcz>

We migrated the configurationOfPetitParser to its new home. So what is the difference?



>
> Cheers,
> Diego
>

On Mar 22, 2013, at 9:36 PM, stephane ducasse wrote:

>>>
>>
>> Since the configuration of Seaside 3.1 is still unfinished: contact me if you would like to have this configuration, or SeasideRest and/or Magritte, as they depend on Seaside 3.1.
>>
>> The configurations of Grease and PetitParser are done and load properly. I included them here. Can I put them in the verified repository or does someone wants to check them and upload them here?
>> <ConfigurationOfGrease-DiegoLont.189.mcz><ConfigurationOfPetitParser-DiegoLont.30.mcz>
>
> We migrated the configurationOfPetitParser to its new home. So what is the difference?
>
The versions of PetitParser were not yet updated in the latest version, causing the stable version to break that "BlockClosure asParser" could not be loaded. So I updated the versions, and adding to stable that for Pharo 2.0 is the stable version is 1.6.1