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

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
36 messages Options
12
Reply | Threaded
Open this post in threaded view
|

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

Mariano Martinez Peck
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


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

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

Mariano Martinez Peck
Sorry, the link is actually this one:

https://gforge.inria.fr/frs/download.php/26681/Pharo-1.0-10515-rc3dev10.03.1.zip

On Sat, Mar 20, 2010 at 8:40 PM, Mariano Martinez Peck <[hidden email]> wrote:
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



_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

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

csrabak
In reply to this post by Mariano Martinez Peck
I just think the issue #1155 should also be addressed before we could claim 1.0 "done".



Em 20/03/2010 16:40, Mariano Martinez Peck < [hidden email] > escreveu:
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

 

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

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

Stéphane Ducasse
In reply to this post by Mariano Martinez Peck
thanks a lot mariano.
this is cool to have somebody like you helping and pushing pharo that way.

Stef

On Mar 20, 2010, at 8:40 PM, Mariano Martinez Peck wrote:

> 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
>
> _______________________________________________
> 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
Reply | Threaded
Open this post in threaded view
|

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

Stéphane Ducasse
In reply to this post by csrabak
Sorry but this is certainly not a show stopper so this bug will not be integrated.

Stef

> I just think the issue #1155 should also be addressed before we could claim 1.0 "done".
>
>
>
> Em 20/03/2010 16:40, Mariano Martinez Peck < [hidden email] > escreveu:
> 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
>
>
>
> _______________________________________________
> 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
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-users] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

Miguel Cobá
In reply to this post by Mariano Martinez Peck
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.
>
> 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

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


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-users] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

Dale
In reply to this post by Mariano Martinez Peck
That version is copied over to SqueakSource MetacelloRepository...

I also have a comment on the release...when I bring Pharo up on my laptop (running OpenSuse) the lower right corner of the workspace is "off the screen" so I have to move the workspace to see the scroll bar...

Dale
----- "Miguel Enrique Cobá Martinez" <[hidden email]> wrote:

| 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.
| >
| > 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
|
| 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
|
|
| _______________________________________________
| 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
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-users] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

Miguel Cobá
In reply to this post by Mariano Martinez Peck
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


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-users] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

Miguel Cobá
In reply to this post by Dale
El dom, 21-03-2010 a las 10:15 -0700, Dale Henrichs escribió:
> That version is copied over to SqueakSource MetacelloRepository...

Thanks

>
> I also have a comment on the release...when I bring Pharo up on my laptop (running OpenSuse) the lower right corner of the workspace is "off the screen" so I have to move the workspace to see the scroll bar...
>

Mee too. The image windows open in like 800x600 and the workspace is
partially off-screen.

cheers

> Dale
> ----- "Miguel Enrique Cobá Martinez" <[hidden email]> wrote:
>
> | 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.
> | >
> | > 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
> |
> | 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
> |
> |
> | _______________________________________________
> | 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

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


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-users] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

Mariano Martinez Peck
In reply to this post by Miguel Cobá


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
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-users] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

Mariano Martinez Peck
In reply to this post by Miguel Cobá


Mee too. The image windows open in like 800x600 and the workspace is
partially off-screen.


If you see in the definition of the workspace, there are the sized. Can you give me a size that correctly match your needs?

Thanks

Mariano
 
cheers

> Dale
> ----- "Miguel Enrique Cobá Martinez" <[hidden email]> wrote:
>
> | 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.
> | >
> | > 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
> |
> | 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
> |
> |
> | _______________________________________________
> | 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

--
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
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-users] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

Mariano Martinez Peck
In reply to this post by Miguel Cobá


2010/3/21 Miguel Enrique Cobá Martinez <[hidden email]>
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?


I said several times I don't have a screen to test. And I ask several times for help. I won't do everything. I don't know how to do it neither how to test it.
So, or someone do it and test it, or it won't be again.

I only remember this link, but there were more opportunities:

http://n4.nabble.com/Latest-Polymorph-td1468728.html#a1468728

 
- 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.

Sure, no problem. I will do.

 

- 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.


Yes, true. But the problem is that as loadDefualt doesn't exist in the image, with the Shout Workpsace you see that word in red...is not nice.

What do you think ?

Thanks for the feedback.

Mariano
 

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



_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-users] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

Dale
In reply to this post by Mariano Martinez Peck
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
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-users] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

Miguel Cobá
In reply to this post by Mariano Martinez Peck
El dom, 21-03-2010 a las 18:34 +0100, Mariano Martinez Peck escribió:

>
>
> 2010/3/21 Miguel Enrique Cobá Martinez <[hidden email]>
>         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?
>
>
> I said several times I don't have a screen to test. And I ask several
> times for help. I won't do everything. I don't know how to do it
> neither how to test it.
> So, or someone do it and test it, or it won't be again.
>
> I only remember this link, but there were more opportunities:
>
> http://n4.nabble.com/Latest-Polymorph-td1468728.html#a1468728

Well, then for 1.1. No problem then.


>
>  
>         - 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.
>
> Sure, no problem. I will do.
>
>  
>        
>         - 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.
>        
>
> Yes, true. But the problem is that as loadDefualt doesn't exist in the
> image, with the Shout Workpsace you see that word in red...is not
> nice.
>
> What do you think ?

ah, ok, no problem then :)

>
> Thanks for the feedback.
>
> Mariano
>  
>        
>         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
>        
>        
>

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


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-users] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

Miguel Cobá
In reply to this post by Mariano Martinez Peck
El dom, 21-03-2010 a las 18:26 +0100, Mariano Martinez Peck escribió:
>
>
>         Mee too. The image windows open in like 800x600 and the
>         workspace is
>         partially off-screen.
>        
>
> If you see in the definition of the workspace, there are the sized.
> Can you give me a size that correctly match your needs?

For the size the image opens in my machine, this values let see the
Pharo logo and the workspace image is fully enclosed in the image
windows border.

        position: 50@90;
  extent: 800 @ 500;

Can this be used for every workspace (or maybe a little offset for each
different one position: 50@90, position: 60@90, position: 70@90; and so
on)

Cheers

>
> Thanks
>
> Mariano
>  
>         cheers
>        
>        
>         > Dale
>         > ----- "Miguel Enrique Cobá Martinez" <[hidden email]>
>         wrote:
>         >
>         > | 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.
>         > | >
>         > | > 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
>         > |
>         > | 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
>         > |
>         > |
>         > | _______________________________________________
>         > | 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
>        
>        
>         --
>        
>         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

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


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-users] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

Mariano Martinez Peck
In reply to this post by Dale


On Sun, Mar 21, 2010 at 6:36 PM, Dale Henrichs <[hidden email]> wrote:
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.


Thanks Dale. I didn't realise about that.
 

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


No. I take a PharoCore image which is zip, without even the package-cache folder and then I evaluate what you can see in installScript, which is :

Gofer new
    gemsource: 'metacello';
    package: 'ConfigurationOfMetacello';
    load.


((Smalltalk at: #ConfigurationOfMetacello) project version: '1.0-beta.25') perform: #load.

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

((Smalltalk at: #ConfigurationOfPharo) project version: '1.0-rc3.10515') perform: #silently: with: true; perform: #load.
 
I think this is happening because of a recent change in the sorting order for Gofer ...


I have no idea.
 
For the build process you may want to either make sure your package-cache is empty


My package-cache was empty. I even didn't have that folder-
 
or use disablePackageCache in the places where you explicitly load a Configuration or perhaps something else?


How can I do that ? where should I put disablePackageCache ? do you have a example?

Thanks!

Mariano

 
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


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-users] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

Dale
If that's the build process you use, I'm not sure why the repsitory isn't mapped correctly ... maybe it's a metacello bug then...I will do a build and see what I can find out...

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

| On Sun, Mar 21, 2010 at 6:36 PM, Dale Henrichs
| <[hidden email]>wrote:
|
| > 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.
| >
|
|
| Thanks Dale. I didn't realise about that.
|
|
| >
| > I'm assuming this is because they were in your package-cache when
| you did
| > the build.
| >
| >
| No. I take a PharoCore image which is zip, without even the
| package-cache
| folder and then I evaluate what you can see in installScript, which is
| :
|
| Gofer new
|     gemsource: 'metacello';
|     package: 'ConfigurationOfMetacello';
|     load.
|
|
| ((Smalltalk at: #ConfigurationOfMetacello) project version:
| '1.0-beta.25')
| perform: #load.
|
| Gofer new
|     squeaksource: 'MetacelloRepository';
|     package: 'ConfigurationOfPharo';
|     load.
|
| ((Smalltalk at: #ConfigurationOfPharo) project version:
| '1.0-rc3.10515')
| perform: #silently: with: true; perform: #load.
|
|
| > I think this is happening because of a recent change in the sorting
| order
| > for Gofer ...
| >
| >
| I have no idea.
|
|
| > For the build process you may want to either make sure your
| package-cache
| > is empty
|
|
|
| My package-cache was empty. I even didn't have that folder-
|
|
| > or use disablePackageCache in the places where you explicitly load
| a
| > Configuration or perhaps something else?
| >
| >
| How can I do that ? where should I put disablePackageCache ? do you
| have a
| example?
|
| Thanks!
|
| Mariano
|
|
|
| > 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

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-users] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

Mariano Martinez Peck
In reply to this post by Miguel Cobá
Miguel. Good idea. I have just commited the following in http://www.squeaksource.com/ImageForDevelopers

Can you please check and change/commit as necessary ?

Name: ImageForDevelopers-pharo-MarianoMartinezPeck.221
Author: MarianoMartinezPeck
Time: 21 March 2010, 7:55:04 pm
UUID: d30a8535-7609-4bf6-b078-546fd0ea0c1b
Ancestors: ImageForDevelopers-pharo-MarianoMartinezPeck.220

- Changed size of workspaces to fix better in 800*600
- Update Magma documentation


Cheers

Mariano

2010/3/21 Miguel Enrique Cobá Martinez <[hidden email]>
El dom, 21-03-2010 a las 18:26 +0100, Mariano Martinez Peck escribió:
>
>
>         Mee too. The image windows open in like 800x600 and the
>         workspace is
>         partially off-screen.
>
>
> If you see in the definition of the workspace, there are the sized.
> Can you give me a size that correctly match your needs?

For the size the image opens in my machine, this values let see the
Pharo logo and the workspace image is fully enclosed in the image
windows border.

       position: 50@90;
       extent: 800 @ 500;

Can this be used for every workspace (or maybe a little offset for each
different one position: 50@90, position: 60@90, position: 70@90; and so
on)

Cheers
>
> Thanks
>
> Mariano
>
>         cheers
>
>
>         > Dale
>         > ----- "Miguel Enrique Cobá Martinez" <[hidden email]>
>         wrote:
>         >
>         > | 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.
>         > | >
>         > | > 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
>         > |
>         > | 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
>         > |
>         > |
>         > | _______________________________________________
>         > | 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
>
>
>         --
>
>         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

--
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
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-users] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

Dale
In reply to this post by Dale
Yep,

A metacello 1.0-beta.25 bug ... I'll fix it right now (or after breakfast:).

Dale
----- "Dale Henrichs" <[hidden email]> wrote:

| If that's the build process you use, I'm not sure why the repsitory
| isn't mapped correctly ... maybe it's a metacello bug then...I will do
| a build and see what I can find out...
|
| Dale
| ----- "Mariano Martinez Peck" <[hidden email]> wrote:
|
| | On Sun, Mar 21, 2010 at 6:36 PM, Dale Henrichs
| | <[hidden email]>wrote:
| |
| | > 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.
| | >
| |
| |
| | Thanks Dale. I didn't realise about that.
| |
| |
| | >
| | > I'm assuming this is because they were in your package-cache when
| | you did
| | > the build.
| | >
| | >
| | No. I take a PharoCore image which is zip, without even the
| | package-cache
| | folder and then I evaluate what you can see in installScript, which
| is
| | :
| |
| | Gofer new
| |     gemsource: 'metacello';
| |     package: 'ConfigurationOfMetacello';
| |     load.
| |
| |
| | ((Smalltalk at: #ConfigurationOfMetacello) project version:
| | '1.0-beta.25')
| | perform: #load.
| |
| | Gofer new
| |     squeaksource: 'MetacelloRepository';
| |     package: 'ConfigurationOfPharo';
| |     load.
| |
| | ((Smalltalk at: #ConfigurationOfPharo) project version:
| | '1.0-rc3.10515')
| | perform: #silently: with: true; perform: #load.
| |
| |
| | > I think this is happening because of a recent change in the
| sorting
| | order
| | > for Gofer ...
| | >
| | >
| | I have no idea.
| |
| |
| | > For the build process you may want to either make sure your
| | package-cache
| | > is empty
| |
| |
| |
| | My package-cache was empty. I even didn't have that folder-
| |
| |
| | > or use disablePackageCache in the places where you explicitly load
| | a
| | > Configuration or perhaps something else?
| | >
| | >
| | How can I do that ? where should I put disablePackageCache ? do you
| | have a
| | example?
| |
| | Thanks!
| |
| | Mariano
| |
| |
| |
| | > 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
|
| _______________________________________________
| 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
Reply | Threaded
Open this post in threaded view
|

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

Mariano Martinez Peck
In reply to this post by Mariano Martinez Peck


On Sun, Mar 21, 2010 at 11:54 AM, Adrian Lienhard <[hidden email]> wrote:
Hi Mariano,

I wonder why you mentioned O2 issues below because O2 is not in Pharo anymore, isn't it?


Sorry Adrian. I forgot about this email. I answer to the mail as it has an excellent question and my bad :)

I put the O2 issues because:

- I think it is a "official package that works on Pharo" even if we don't know what a official package is.
- I have to create a version of the metacello configuration for O2 and I wanted to put the issues in the "description" of the release
- The O2 issues were submitted in Pharo issue tracking, thus, I wanted to put them as closed and put "integrated in PharoXXX"
- I changed the welcome workspace to load this new version of O2

However, it doesn't mean that O2 is now included in Dev images. Now you made me realize that this can be confusing. So, what should I do ? I am all ears :)

 
Cheers,
Adrian

On Mar 20, 2010, at 20:40 , Mariano Martinez Peck wrote:

> 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
> _______________________________________________
> 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
12