February 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [squeak-dev] Re: SqueakSource down... again

by StÃ©phane Ducasse

> Stef, > > I believe that the source is on SqueakSource in the squeaksource3 repository. This is a port of SqueakSource to Seaside3.0 that was done by Philippe, Tobias and James Foster... Thanks!. > Tobias mentioned that he was getting close t finishing things up in an earlier message.

Feb. 25, 2011

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

by laurent laffont

Marcus, I've worked on this this week: - I've fixed ReleaseTest.testUndeclared and RBInlineMethodFromComponentTest.testInlineEmptyComponentMethod - For all Metacello tests, the fix is available but Dale said: "I haven't released my changes yet ... once I'm satisfied with the the behavior on PharoCore1.2 (that's where I'm doing development) I now have to get the new version of Gofer ported to Squeak and GemStone before I can make the full release ... otherwise the tests will be failing on Squeak/GemStone ..." I think this is really problematic to wait for Squeak/GemStone but one way to go forward is to put them in #expectedFailures - For XML I can fix this tonight if Otto don't want / can do it. So there's only one failing test without fix awaiting: ReleaseTest.testObsoleteClasses. Guillermo and I had a look at it on Monday: GuilleP: Ok, obsoletes come from: ClassRenameFixTest seems to be creating an AutoGeneratedClassForTestingSystemChanges GuilleP: But I can't find the source of AnObsoleteMCMockClassG :( laurentlaffont: it comes from MCMockPackageInfo>>#classNames laurentlaffont: see also the comment in MCPackageTest>>#tearDown some work needed to fix this. But I agree that it seems few people care about 1.2. Sad, I like it far better than 1.1.1. Laurent. On Fri, Feb 25, 2011 at 1:18 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > I personally thing if we ever want to release 1.2, we need to start to be > more radical. > > The XML package breaks the build? So let's remove it completely. Let's ship > 1.2, but without > all the packages that are problematic. > > Same for any other package that has a failing test. > > Marcus > > > On Feb 25, 2011, at 1:12 PM, Torsten Bergmann wrote: > > > Still I do not understand: > > > > Evaluate this in an updated Pharo core 1.2: > > > > ------------------------------------------------------------------------ > > Gofer new > > squeaksource: 'MetacelloRepository'; > > package: 'ConfigurationOfXMLSupport'; > > load. > > > > (Smalltalk at: #ConfigurationOfXMLSupport) project latestVersion > > ------------------------------------------------------------------------ > > > > returns 1.1.8 [ConfigurationOfXMLSupport] > > > > This is now broken by Otto. OK, he broke it, he has to repair it ;) > > > > But independent from that, the method in: > > > > ConfigurationOfPharo>>version12beta2: > > > > includes the following: > > > > project: 'XMLSupport' with: '1.1.6'. > > > > So I would have expected that for Pharo "1.2-beta2" the 1.1.6 (and not > the > > 1.1.8) of XMLSupport gets loaded and Hudson should have been green. > > > > Why does Metacello load the 1.1.8 when a previous project version (1.1.6) > > is referenced? > > > > Dale, any comments? > > > > Bye > > T. > > > > > > > > -- > > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > >

Feb. 25, 2011

Re: [Pharo-project] Issue 3571 in pharo: [Failing Test] Tests.Release.ReleaseTest.testUndeclared

by pharo＠googlecode.com

Updates: Status: Closed Comment #4 on issue 3571 by marcus.d...(a)gmail.com: [Failing Test] Tests.Release.ReleaseTest.testUndeclared http://code.google.com/p/pharo/issues/detail?id=3571 test is green as of buid #149

Feb. 25, 2011

Re: [Pharo-project] SilverSmalltalk

by StÃ©phane Ducasse

does it run on your machine? If people pay for it then there is a market for pharo too. > You're probably aware of it. I found it impressive > http://www.silversmalltalk.com/ > > Cheers, > Alexandre > --

Feb. 25, 2011

Re: [Pharo-project] Issue 3482 in pharo: InterimSoundMorph references to SketchMorph

by pharo＠googlecode.com

Updates: Status: Closed Comment #17 on issue 3482 by marcus.d...(a)gmail.com: InterimSoundMorph references to SketchMorph http://code.google.com/p/pharo/issues/detail?id=3482 Test is not failing anymore for Undeclared

Feb. 25, 2011

[Pharo-project] [update 1.2] #12338

by Marcus Denker

12338 ----- - Issue 3699: Beeper beep raises MNU - remove SocketTests as they are failing on the testserver -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Feb. 25, 2011

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

by Marcus Denker

I personally thing if we ever want to release 1.2, we need to start to be more radical. The XML package breaks the build? So let's remove it completely. Let's ship 1.2, but without all the packages that are problematic. Same for any other package that has a failing test. Marcus On Feb 25, 2011, at 1:12 PM, Torsten Bergmann wrote: > Still I do not understand: > > Evaluate this in an updated Pharo core 1.2: > > ------------------------------------------------------------------------ > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfXMLSupport'; > load. > > (Smalltalk at: #ConfigurationOfXMLSupport) project latestVersion > ------------------------------------------------------------------------ > > returns 1.1.8 [ConfigurationOfXMLSupport] > > This is now broken by Otto. OK, he broke it, he has to repair it ;) > > But independent from that, the method in: > > ConfigurationOfPharo>>version12beta2: > > includes the following: > > project: 'XMLSupport' with: '1.1.6'. > > So I would have expected that for Pharo "1.2-beta2" the 1.1.6 (and not the > 1.1.8) of XMLSupport gets loaded and Hudson should have been green. > > Why does Metacello load the 1.1.8 when a previous project version (1.1.6) > is referenced? > > Dale, any comments? > > Bye > T. > > > > -- > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Feb. 25, 2011

Re: [Pharo-project] SqueakSource3 (was: Re: Pharo Sources Google Hit Ratio)

by laurent laffont

On Fri, Feb 25, 2011 at 12:38 PM, Tobias Pape <Das.Linux(a)gmx.de> wrote: > Am 2011-02-25 um 10:19 schrieb laurent laffont: > > > > On Fri, Feb 25, 2011 at 10:14 AM, Tobias Pape <Das.Linux(a)gmx.de> wrote: > > [â¦] > > > >> I started this thing around mid-last year in efforts > >> to get SqueakSource working on Seaside3, Magritte2 > >> and gemstone with Email support, while integrating > >> the different squeaksource versions floating around. > >> During that time I tried to make SqueakSource more > >> Framework-like to enhance extensibility. > >> Philippe and Dale contributed much to the current state. > >> In the last 3 month, I had little time for this > >> project, but I plan to be able to release an alpha or so > >> in the next weeks. > >> > > Would be cool to have a webdesigner making this sexy :) > > > > Laurent. > > Full ACK. > Alas, Iâm at most typographer and in no way web designer:/ > May be we can launch a SqueakSource design contest with a prize to be won at ESUG 2011 conference Laurent. > > So Long > -Tobias

Feb. 25, 2011

Re: [Pharo-project] Issue 3699 in pharo: Beeper beep raises MNU

by pharo＠googlecode.com

Updates: Status: Closed Comment #7 on issue 3699 by marcus.d...(a)gmail.com: Beeper beep raises MNU http://code.google.com/p/pharo/issues/detail?id=3699 in 1.2 12338

Feb. 25, 2011

Re: [Pharo-project] Issue 3743 in pharo: Fix Finder UI (add shortcuts and more commands)

by pharo＠googlecode.com

Comment #7 on issue 3743 by marcus.d...(a)gmail.com: Fix Finder UI (add shortcuts and more commands) http://code.google.com/p/pharo/issues/detail?id=3743 Issue 3722 has been merged into this issue.

Feb. 25, 2011