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

[Pharo-project] Glorp (was: Object>>changed:with: no longer in PharoCore-1.1-11383)

by Yanni Chiu

Mariano Martinez Peck wrote: > > On Fri, Jun 11, 2010 at 7:25 PM, Yanni Chiu wrote: > > The other Glorp patch is the Scanner change for '_' (in method names). > > > Ok, but this is working ok in Pharo 1.1. Isn't it ? The patch works, and is still needed for Pharo 1.1 - I can check further, if you think it is no longer needed. I compared the code and it has a minor change from what's in Pharo 1.1. (I had to reformat both versions, before doing the diff). There was a discussion on allowing '_' in method names in the Squeak list a few months ago. I'm not sure what the Pharo stance is. I thought this patch was the cure for problems loading Glorp test code (which have '_' in the method names), but like I said, if Pharo 1.1 is already supposed to accept '_' in method names, I can investigate the patch further. > > In PharoCore-1.1, two more tests fail: > > GlorpTest.GlorpManyToManyDBTest.testReadNodeAndDeleteChildWithSaveAndContinue > GlorpTest.GlorpUnitOfWorkTest.testRollbackOneToManyAfterAdd > > > Why you put the namespaces? you confuse me with VW ;) The results are from a copy&paste from a Hudson build test report. The latest Hudson build code adds the psuedo-package names. > In PharoCore-1.0, only these three tests were failing: > GlorpTest.Extras.GlorpMainBackendTest.testSetToBaseTestAFacility > > > forget this one. My problem. I need to fix it. > > > GlorpTest.GlorpRowMapForMementosCollectionTest.testRBSmallDictionary IIRC, this test seemed to make overly specific assumptions about the Dictionary implementation. > GlorpTest.GlorpSelectCommandTest.testExecute Can't remember anything about this one.

June 13, 2010

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

by Yanni Chiu

Schwab,Wilhelm K wrote: > Looking at your seaside3.st file, it does not look like it does > everything; omnibrowser.st is probably also part of it. Is there a > master script that I am missing, or do you specify that list > elsewhere? I think you want to follow the chain of "Upstream Projects" that is available in the Hudson server interface.

June 13, 2010

Re: [Pharo-project] could not find module vm-display-X11

by spiralofhope

I was previously using release candidate 1 of my distro, fully updated. I reinstalled my system, using the new candidate 2. I then followed the steps to reproduce the issue. . and I cannot. I see a gui open up, and I'm able to step through the integrated tutorial. Whatever issue I was having has been solved by this reinstall. Perhaps my earlier tinkering broke some of the innards of my earlier distro install or there was some issue that's since been resolved. -- http://spiralofhope.com

June 13, 2010

[Pharo-project] [SIXX] feedback

by Schwab,Wilhelm K

Masashi, I have been trying to do some testing of Pharo 1.1 through a Seaside 3.0 daily image. One of the first things I load is SIXX. Pharo has been addressing underscore assignment problems, and the default is now to treat them as syntax errors, and one was identified in SixxAutoMorphMemento class>>release. I have also noted them in the #instDict and #instDict: accessors. It would be helpful if you could change the underscores to := for future releases. I am not sure how to tell if there are other underscore assignments in the .sar. Thanks for SIXX! Bill

June 12, 2010

Re: [Pharo-project] Object>>changed:with: no longer in PharoCore-1.1-11383

by Mariano Martinez Peck

On Fri, Jun 11, 2010 at 7:25 PM, Yanni Chiu <yanni(a)rogers.com> wrote: > Mariano Martinez Peck wrote: > > >> On Fri, Jun 11, 2010 at 8:39 AM, Yanni Chiu wrote: >> I have a set of patches that get filed-in during my build. I have >> this fix there, for now. >> >> >> There are more for Glorp ? I want to have it perfectly working in Pharo. >> So, let me know and we can commit and integrate them. >> > > The other Glorp patch is the Scanner change for '_' (in method names). > > Ok, but this is working ok in Pharo 1.1. Isn't it ? > In PharoCore-1.1, two more tests fail: > > > GlorpTest.GlorpManyToManyDBTest.testReadNodeAndDeleteChildWithSaveAndContinue > GlorpTest.GlorpUnitOfWorkTest.testRollbackOneToManyAfterAdd > > Why you put the namespaces? you confuse me with VW ;) In PharoCore-1.0, only these three tests were failing: > GlorpTest.Extras.GlorpMainBackendTest.testSetToBaseTestAFacility > forget this one. My problem. I need to fix it. > GlorpTest.GlorpRowMapForMementosCollectionTest.testRBSmallDictionary > GlorpTest.GlorpSelectCommandTest.testExecute > > Do you know why they fail or how to fix them ? > Since these don't impact me, I probably won't look into them for a while. I > load the packages with Gofer directly, and use the native PostgreSQL Client > (not OpenDBX). > > > ups...sorry I read and answer in the moment hahahahhaa. cheers Mariano > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 12, 2010

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

by Schwab,Wilhelm K

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

June 12, 2010

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

by Fernando olivero

On Jun 11, 2010, at 2:04 PM, Hilaire Fernandes wrote: > Hi Fernando, > > Sure we can be more optimal in execution term, but it is not my > objective. I want the example to be concise and optimal under this term, > so smaller then may be easier to catch. > Hi Hilarie, i was not speaking of optimization. Just pointing out the miss use of the pattern , conceptually. Which i think when writing tutorials is important. Lazy initialization is conceptually used when the internal collaborator is hard to initialize and maybe would never be used. Which is not the case with the window, toolbar, etc 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. Fernando > > > Hilaire > > > > Fernando olivero a Ã©crit : >> Hi Laurent, great work! We need more documentation! >> >> Just a little coding style i would like to point out. >> >> I see you are using lazy initialization, but in this case i believe its >> a miss-use of the pattern. >> Because you always will have a toolbar and a menu bar, since the >> creation you are sure you need them, why not go and just initialize them >> before installing. >> >> Let me know what you think. >> >> >> So i propose changing the implementation to : >> >> initialize >> super initialize. >> self initializeMenuBar. >> self initializeToolbar. >> .... >> >> and >> >> initializeMenuBar >> | menu | >> menu := self window newMenu. >> menu >> addToggle: 'Load' >> target: self >> selector: #load. >> menu >> addToggle: 'Save' >> target: self >> selector: #save. >> menubar := self window newToolDockingBar. >> menubar >> add: 'File' >> font: self window theme menuBarFont >> icon: nil >> help: 'File operations' >> subMenu: menu. >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> 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 12, 2010

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

by Schwab,Wilhelm K

Lukas, Looking at your seaside3.st file, it does not look like it does everything; omnibrowser.st is probably also part of it. Is there a master script that I am missing, or do you specify that list elsewhere? Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Lukas Renggli [renggli(a)gmail.com] Sent: Saturday, June 12, 2010 4:09 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] FW: Issue 2476 in pharo: ConnectionQueue broken in 1.0 and 1.1 beta > This is interesting. Is there any way to find the script that was run to build a particular image? The scripts are here: http://github.com/renggli/builder/tree/master/scripts > What separates the successful and stable builds from the unstable ones? Unstable builds are builds that have failing tests (or too many code critics errors). > What (how bad) is a fail build? Filing builds are builds that could not be completed (missing package, compile error, ...). > You load Shout (which is a must<g>). Otherwise, how similar is the image to Pharo-dev + Seaside? Probably quite different. I load packages and set settings according to my preference. > 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, ...) > Is the reported "last duration" (41 min) the time it took to create the image? Yes, this includes the time to run the tests (and code critics). Lukas -- Lukas Renggli 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

June 12, 2010

[Pharo-project] [update 1.2] #12007

by StÃ©phane Ducasse

12007 ----- - Issue 2290: new windows (e.g. workspaces) appear wherever they feel like - SystemChangeNotifier-Tests from 3.9. - Issue 2381: We should probably remove slideToTrash

June 12, 2010

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

by Lukas Renggli

> This is interesting. Â Is there any way to find the script that was run to build a particular image? The scripts are here: http://github.com/renggli/builder/tree/master/scripts > What separates the successful and stable builds from the unstable ones? Unstable builds are builds that have failing tests (or too many code critics errors). > What (how bad) is a fail build? Filing builds are builds that could not be completed (missing package, compile error, ...). > You load Shout (which is a must<g>). Â Otherwise, how similar is the image to Pharo-dev + Seaside? Probably quite different. I load packages and set settings according to my preference. > 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, ...) > Is the reported "last duration" (41 min) the time it took to create the image? Yes, this includes the time to run the tests (and code critics). Lukas -- Lukas Renggli www.lukas-renggli.ch

June 12, 2010