January 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by John M McIntosh

Ok, I had spend a couple of hours with Michael Rueger on the mac menu bug. But I'm not sure if he got around to sending out any changes before he took some time off. If someone can test this I can offer up some change sets for review. I've never been able to recreate this here so someone else has to try. On 2010-01-24, at 12:05 PM, StÃ©phane Ducasse wrote: > Michael > > We have 1.0 (on final release cycle) and 1.1-unstable and for both we have core and dev images. > > 1.0 is on release period for too long now mainly because of a vicious bug due to mac menu > that duplicated events. -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

Jan. 25, 2010

Re: [Pharo-project] [update] #10507

by Miguel Enrique CobÃ¡ Martinez

El dom, 24-01-2010 a las 21:58 +0100, Marcus Denker escribiÃ³: > On Jan 24, 2010, at 9:52 PM, Marcus Denker wrote: > > > > > On Jan 24, 2010, at 9:51 PM, Mariano Martinez Peck wrote: > >> > >> > >> Adrian: shouldn't we update http://www.pharo-project.org/home because it says "Current status: 1.0 RC1" > >> > > yes, and we need to link it on the download page... there are quite some downloads per day. > > > > I will do that. > > > Done: > > http://www.pharo-project.org/home It is necessary to put a sources file download link in the pharo download page. The dev image zip already contains it. I think that it should be in the PharoCore section that it doesn't contains it. Cheers > http://www.pharo-project.org/pharo-download > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Jan. 25, 2010

Re: [Pharo-project] RBSpelling errors when class has Pool Dictionary - Re: [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by Lukas Renggli

> Wiiiii :)Â Â Â Only one expected failire! Yeah, I don't know how to fix that one. And it probably won't be in the near future. Maybe at some point somebody understands why it is broken. > Thanks Lukas!!Â Next Pharo image will use RB 1.2. RB 1.2 ? Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 24, 2010

Re: [Pharo-project] [update] #10507

by Stefan Marr

> So to explain: waiting two days until making the link on the download page: ok. We did that. Not announcing it yet. Ok, > we will announce when it's clear it's stable. But having people download an old image without the bug-fixes by default? > No. > > We are already in Beta. Clearly marked. There is no need for a private, more secret special beta. What is a Release Candidate meant for? Well, I think, it is meant to be downloaded and tested. After all, it is a RC, if it blows up in your face, then it is something you will report. At least that is the way it is done in the world of PHP. Several iterations, going from beta (for early adopters only, people living on the edge), to RCs with several iterations, where basically every one out there with a large code base is asked to test it extensively to get to a point where only minor issues remain. The last RC where no critical issues have been found will then be labeled as final x.y.0 release. And that only works, if RCs are actually tested by a large group of people. Best Stefan > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 3956 Fax: +32 2 629 3525

Jan. 24, 2010

Re: [Pharo-project] RBSpelling errors when class has Pool Dictionary - Re: [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by Mariano Martinez Peck

On Sun, Jan 24, 2010 at 10:24 PM, Lukas Renggli <renggli(a)gmail.com> wrote: > >> Go to "Apple Mail" and type the word "Refactoring". It should be > >> highlighted with the spell-checker. Click on "Add to Dictionary". Then > >> the tests should pass. > >> > >> No, sorry. I have to fix the tests. Wait. > > > > hahahahha no problem. I am not hurry at all :) > > I think I fixed it. > > Wiiiii :) Only one expected failire! 351 run, 350 green :) Thanks Lukas!! Next Pharo image will use RB 1.2. Cheers Mariano > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 24, 2010

Re: [Pharo-project] [update] #10507

by Mariano Martinez Peck

On Sun, Jan 24, 2010 at 10:29 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On Jan 24, 2010, at 10:26 PM, Marcus Denker wrote: > > > > > On Jan 24, 2010, at 10:15 PM, Mariano Martinez Peck wrote: > >> > >> > >> My idea was to build a Dev image only for BetaTesters. Those people who > can help us to test and don't care if the image blows up in their face. > Because it was easier, I upload that image in gforge and send the email to > the list. However, my idea was to do the real ANN (to the rest of the > people) and link in download section (so that final users can download it) > once the image was already tested and without big problems. > >> > >> What do you think ? > > > > I think this makes no sense... :-) > > > > So to explain: waiting two days until making the link on the download page: > ok. We did that. Not announcing it yet. Ok, > we will announce when it's clear it's stable. But having people download an > old image without the bug-fixes by default? > No. > > We are already in Beta. Clearly marked. There is no need for a private, > more secret special beta. > > Ok. But those two days were in weekend :) But ok, maybe you are right. > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 24, 2010

Re: [Pharo-project] Pharo dev image rc2 thoughts

by Mariano Martinez Peck

On Sun, Jan 24, 2010 at 10:24 PM, Dale Henrichs <dale.henrichs(a)gemstone.com>wrote: > Mariano, > > The progress-bar problem is solvable. > > The progress bar problem appears because the dev image doits reinitalize > the progress bar class. The first question is: "Must the progress bar code > be initialized?" if no, then remove the initialization code and the problem > should be solved:) If yes, then I will dig into the problem and see what I > can come up with ... there are a couple of routes I can take, but I'd like > to know that we can't bypass the initialization before getting my hands that > dirty:) > > Cool you are reading this thread Dale. Maybe this is another typical case where I may need post/pre doit for groups :) hahahahah Of course, I need what you said it was most difficult...That's Morphy law :) But doesn't matter. We can bypass this problem. Maybe we can think about it with time, in Metacello 1.1 or something like that. I am completely ignorant about the progress. Could you detect where is exactly that the progress bar is initialized in that package ? > Dale > > ----- "Mariano Martinez Peck" <marianopeck(a)gmail.com> wrote: > > | 2010/1/24 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com> > | > | > > | > Now to the point. I understand that the separation of concerns is > | good, > | > because ImageForDevelopers is already a separated and tested > | package > | > that shouldn't be inside ConfigurationOfPharo. > | > > | > | I will tell you a bit the background: First, when I took the > | installScript > | from Damien, there where some stuff done in the script (like settings > | the > | preferences and the fonts) done in the installScript. It didn't have > | sense > | for me (of course I asked Damien) and I put that in ImageForDevelopers > | (and > | this is cool because it is versiones with monticello). Actually in > | DEVImageCreator >> install. I need also to clean that class as it has > | a lot > | of old stuff. But not time for the moment. > | > | When I create rc1, ImageForDevelopers was a dependency of > | ConfigurationOfPharo as you said. There was a problem installing it > | with the > | progress bar and Metacello. The image just frezze because of a > | sempahore and > | a delay....see issue: > | http://code.google.com/p/metacello/issues/detail?id=39 > | But I can even reproduce the problem....So, that quick solution (as I > | needed > | to relase the Pharo image) was to put in the installScript. > | > | And after a while I discovered that I even like more that approach. > | Someone > | may want just the packages of a dev image, but not to set > | preferences, > | fonts, cleanups, etc. And I don't have the Metacello bug. > | The problem I found also putting it as a dependency is that it has to > | be the > | LATEST (I think that you cannot even said that XX package has to be > | the last > | one to be loaded) package to be loaded. I can put it as postDoIt for > | the > | project, but this cannot be done because it is ONLY required for > | certain > | groups > | > | > | > - Shouldn't be necessary to create a > | ConfigurationOfImageForDevelopers > | > and in this configuration reference ConfigurationOfPharo and then > | the > | > installScript for the dev image use *only* > | > ConfigurationOfImageForDevelopers? > | > > | > > | It can work, but actually for me we are having a problem (maybe we > | need the > | support the post/pre doit for groupos...but dale said it was > | complicated). I > | would like to just do (ConfigurationOfPharo project version: 'XXX') > | load:'ImageForDeveloper' > | > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 24, 2010

Re: [Pharo-project] [update] #10507

by Marcus Denker

On Jan 24, 2010, at 10:26 PM, Marcus Denker wrote: > > On Jan 24, 2010, at 10:15 PM, Mariano Martinez Peck wrote: >> >> >> My idea was to build a Dev image only for BetaTesters. Those people who can help us to test and don't care if the image blows up in their face. Because it was easier, I upload that image in gforge and send the email to the list. However, my idea was to do the real ANN (to the rest of the people) and link in download section (so that final users can download it) once the image was already tested and without big problems. >> >> What do you think ? > > I think this makes no sense... :-) > So to explain: waiting two days until making the link on the download page: ok. We did that. Not announcing it yet. Ok, we will announce when it's clear it's stable. But having people download an old image without the bug-fixes by default? No. We are already in Beta. Clearly marked. There is no need for a private, more secret special beta. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 24, 2010

Re: [Pharo-project] [update] #10507

by Marcus Denker

On Jan 24, 2010, at 10:15 PM, Mariano Martinez Peck wrote: > > > My idea was to build a Dev image only for BetaTesters. Those people who can help us to test and don't care if the image blows up in their face. Because it was easier, I upload that image in gforge and send the email to the list. However, my idea was to do the real ANN (to the rest of the people) and link in download section (so that final users can download it) once the image was already tested and without big problems. > > What do you think ? I think this makes no sense... :-) Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 24, 2010

Re: [Pharo-project] RBSpelling errors when class has Pool Dictionary - Re: [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by Lukas Renggli

>> Go to "Apple Mail" and type the word "Refactoring". It should be >> highlighted with the spell-checker. Click on "Add to Dictionary". Then >> the tests should pass. >> >> No, sorry. I have to fix the tests. Wait. > > hahahahha no problem. I am not hurry at all :) I think I fixed it. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 24, 2010