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

[Pharo-project] A new chapter in the CollaborActive book

by Hilaire Fernandes

About localisation with gettext http://book.pharo-project.org/book/Localisation Please edit directly when you see any errors Hilaire

June 13, 2010

[Pharo-project] [update 1.2] #12008 and 12009

by StÃ©phane Ducasse

12008 ----- - 2990: fix a bug which make selection of strategy does not work. Thanks Jannik 2422 Removed - isolationSet and thisDefinition (instances variables never used) - methods reassigning isolationSet also removed (as it was never initialized). Thanks veronica. - TestSubclass 12009 ----- Partial cleanup for 2204 Rewrite plenty of Smalltalk at: as Smalltalk globals at:. Thanks simon

June 13, 2010

Re: [Pharo-project] [ANN 1.2] first 1.2 pre-built core image 12003

by Michael Roberts

This is the bug entry and fix for 1.1. I will do a separate one for 1.2. Just look at the objects slots. it got downgraded and version which should be nil got repopulated. I will remove the old structure for 1.2. http://code.google.com/p/pharo/issues/detail?id=2552 cheers Mike On Sun, Jun 13, 2010 at 2:23 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > do you have a pointer? > > Stef > On Jun 13, 2010, at 3:17 PM, Michael Roberts wrote: > >> Hi, >> >> SystemVersion current is missing all the state (i put some effort into >> making that). Â I'm not sure when it got lost but should really be >> fixed. >> >> thanks, >> Mike >> >> On Sat, Jun 12, 2010 at 1:37 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> Â Â Â Â https://gforge.inria.fr/frs/download.php/27158/PharoCore-1.2-12003-UNSTABLE… >>> >>> -- >>> 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 >>> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 13, 2010

Re: [Pharo-project] [ANN 1.2] first 1.2 pre-built core image 12003

by StÃ©phane Ducasse

do you have a pointer? Stef On Jun 13, 2010, at 3:17 PM, Michael Roberts wrote: > Hi, > > SystemVersion current is missing all the state (i put some effort into > making that). I'm not sure when it got lost but should really be > fixed. > > thanks, > Mike > > On Sat, Jun 12, 2010 at 1:37 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> https://gforge.inria.fr/frs/download.php/27158/PharoCore-1.2-12003-UNSTABLE… >> >> -- >> 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 >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 13, 2010

Re: [Pharo-project] [ANN 1.2] first 1.2 pre-built core image 12003

by Michael Roberts

Hi, SystemVersion current is missing all the state (i put some effort into making that). I'm not sure when it got lost but should really be fixed. thanks, Mike On Sat, Jun 12, 2010 at 1:37 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Â Â Â Â https://gforge.inria.fr/frs/download.php/27158/PharoCore-1.2-12003-UNSTABLE… > > -- > 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 >

June 13, 2010

Re: [Pharo-project] GUI Polymorph: lazy initialization

by Hilaire Fernandes

It is fine. Even miss used, I found lazy initialization comfortable. Please consider adding a nice comment in the documentation about the lazy initialisation pattern, external link will be nice as well. I am sure it will be use full. Hilaire Fernando olivero a Ã©crit : > Please don't take the wrong way, just wanted to point out the design > problem. > I think you have done a great work by coding a tutorial, which i found > very useful for building a Gaucho control panel for the next version.

June 13, 2010

Re: [Pharo-project] FW: Issue 2476 in pharo: ConnectionQueue broken in 1.0 and 1.1 beta

by StÃ©phane Ducasse

On Jun 13, 2010, at 9:18 AM, Yanni Chiu wrote: > Lukas Renggli wrote: >>> Is there a way to get the bleeding edge of Pharo and a stable version of Seaside? >> Not from my server, but you could setup one that builds whatever you >> need. For me, I use ... >> - ... the latest release candidate or stable release of Pharo only. >> - ... the latest package versions for code I am working on (RB, OB, >> Seaside, Magritte, Pier, ...) > > When I first set up my build server (hudson.jooshr.org) it was building the bleeding edge of Pharo and Seaside. I've since had to back off the bleeding edge of Pharo somewhat - I manually install new image .zip files now. I used to run the in-image update from whatever build image was installed, but the update often failed in headless mode, due to UI popups about deprecated methods, among other issues. I think there's a workaround, but I've not spent the time on it. The situation should improve now that there is a community build server for the core at: http://rmod.lille.inria.fr/hudson/. Yes we will have to think about the UIPopUp and nuke them. We should be able to control the UIPop only when on interactive mode. So having a exception is the way to go. > I then take the build image as the starting point to build my deliverable. I do this build on my local machine, using another Hudson server (they're easy to set up). In retrospect, I should have updated my initial build image much more frequently, then I would have detected the (minor) problems with Glorp and RFB, on PharoCore-1.1, much sooner. Note however that I had decided to start development using PharoCore-1.0 back in January, because it was more stable. So I had no real need to use 1.1 except to test for compatibility. I think that this was wise :) > > My plan now is to build whatever community packages that I depend on (e.g. Glorp & RFB), continuously against the bleeding edge of Pharo. Then, whenever I decide to update my initial build image, there should not be problems loading community packages that I have to fix before I can run my own code. good. > So if everyone were to build/test the community packages that they depend on, then we'd get test coverage on the most important ones. yes. We plan to include in the integration server all the metacello configuration > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 13, 2010

Re: [Pharo-project] Unwind errors: worse in 1.1?

by StÃ©phane Ducasse

can you describe a scenario that we can reproduce? Stef On Jun 13, 2010, at 12:11 AM, Schwab,Wilhelm K wrote: > I have long intermittently seen errors with walkbacks titled "Unwind error during termination." They might be more common in 1.1, and worse, I am now unable to close the offending notifiers/debuggers. I also tried "close all debuggers" without success. > > Bill > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 13, 2010

Re: [Pharo-project] FW: Issue 2476 in pharo: ConnectionQueue broken in 1.0 and 1.1 beta

by Yanni Chiu

Lukas Renggli wrote: >> Is there a way to get the bleeding edge of Pharo and a stable version of Seaside? > > Not from my server, but you could setup one that builds whatever you > need. For me, I use ... > > - ... the latest release candidate or stable release of Pharo only. > - ... the latest package versions for code I am working on (RB, OB, > Seaside, Magritte, Pier, ...) When I first set up my build server (hudson.jooshr.org) it was building the bleeding edge of Pharo and Seaside. I've since had to back off the bleeding edge of Pharo somewhat - I manually install new image .zip files now. I used to run the in-image update from whatever build image was installed, but the update often failed in headless mode, due to UI popups about deprecated methods, among other issues. I think there's a workaround, but I've not spent the time on it. The situation should improve now that there is a community build server for the core at: http://rmod.lille.inria.fr/hudson/. I then take the build image as the starting point to build my deliverable. I do this build on my local machine, using another Hudson server (they're easy to set up). In retrospect, I should have updated my initial build image much more frequently, then I would have detected the (minor) problems with Glorp and RFB, on PharoCore-1.1, much sooner. Note however that I had decided to start development using PharoCore-1.0 back in January, because it was more stable. So I had no real need to use 1.1 except to test for compatibility. My plan now is to build whatever community packages that I depend on (e.g. Glorp & RFB), continuously against the bleeding edge of Pharo. Then, whenever I decide to update my initial build image, there should not be problems loading community packages that I have to fix before I can run my own code. So if everyone were to build/test the community packages that they depend on, then we'd get test coverage on the most important ones.

June 13, 2010

Re: [Pharo-project] [SIXX] feedback

by Yanni Chiu

Schwab,Wilhelm K wrote: > > ... I am not sure how to tell if there are other > underscore assignments in the .sar. Unzip the .sar, then massage the source files to use newlines (e.g. tr '\r' '\n'). Then grep for '_'. That should give you an idea of the scale of the problem.

June 13, 2010