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

[Pharo-project] problem with metacello in 1.2

by Fabrizio Perin

Hi all, i was trying to make Moose loadable into a 1.2 i did try to run the configuration of Moose and i got an error at the very beginning caused by the configuration of metacello. Am i missing something or it actually should work? I did expect to have problem but not with the configuration of metacello. I'm using a Pharo image 12203 on a Squeak4.2.5beta1U VM To reproduce the error just open the image and execute in a workspace: Gofer new squeaksource: 'Moose'; package: 'ConfigurationOfMoose'; load. (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault Attached the log. Thanks, Fabrizio

Oct. 23, 2010

Re: [Pharo-project] akuhn/SUnit: run faster tests first & step through tests

by StÃ©phane Ducasse

It was too difficult to integrate. Stef On Oct 23, 2010, at 2:01 PM, Niko Schwarz wrote: > What's the status of akuhn/SUnit? I couldn't find his code in 1.2 core. > > Niko > > On Wed, Feb 3, 2010 at 1:13 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> this loads well in the latest 1,1 core :) >> so now we should really have a look and these cool changes >> >> Stef >> >> On Jan 6, 2010, at 2:38 PM, Adrian Kuhn wrote: >> >>> SystemChangeNotifier uniqueInstance >>> noMoreNotificationsFor: TestCase. >>> Gofer it >>> disablePackageCache; >>> squeaksource: 'akuhn'; >>> package: 'SUnit'; >>> package: 'SUnitGUI'; >>> load. >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > http://scg.unibe.ch/staff/Schwarz > twitter.com/nes1983 > Tel: +41 076 235 8683 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 23, 2010

Re: [Pharo-project] some patterns I would like to **kill**

by StÃ©phane Ducasse

On Oct 23, 2010, at 1:58 PM, Igor Stasenko wrote: > On 23 October 2010 14:33, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> I think that if you have a container that contains morphs probably findA and other queries are useful. >> Now for a button that is also at the same place a field is the best. >> > > <sarcasm> > if morph having a random submorphs, inserted out of nowhere, just for > fun to see what happen. then yes.. findA is userful, as well as > respondsTo: > </sarcasm> I like your sarcasm, we are all in sync on that Open a 3.8 or 3.9 and check findA: > but if we are talking about specific morphs, like Pluggable and > friends, who serving a certain purpose (building UI from spec), > where no place for 'random', then this truly a bad design. :) > >> Stef >> >> >> On Oct 22, 2010, at 11:14 PM, Schwab,Wilhelm K wrote: >> >>> Stef, >>> >>> #respondsTo: - no argument. More defensive programming (aka masked bugs). Tests like this have their place, but are over-used in Squeak. >>> >>> Using #submorphs *might* be easier to defend. Morphs were designed to be usable in large numbers, and one might argue (playing Devil's Advocate here) that lookups are cheaper than the additional gc load. An instance variable could also cache stale information. Of course, for something that is accessed frequently, an instance variable avoids the lookup and I agree that it is cleaner and easier to read. >>> >>> Bill >>> >>> >>> >>> ________________________________________ >>> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of stephane ducasse [stephane.ducasse(a)free.fr] >>> Sent: Thursday, October 21, 2010 4:47 PM >>> To: Pharo Development >>> Subject: [Pharo-project] some patterns I would like to **kill** >>> >>> Hi >>> >>> I was reading Pluggable and friends >>> I identified some patterns. >>> >>> >>> The respondsTo plague >>> Examples: >>> >>> color := self fillStyle asColor. >>> (self labelMorph respondsTo: #enabled:) >>> ifTrue: [self labelMorph enabled: self enabled]. >>> (self labelMorph respondsTo: #interactionState:) >>> ifTrue: [self labelMorph interactionState: self interactionState] >>> >>> (self labelMorph respondsTo: #enabled:) ifTrue: [ >>> self labelMorph enabled: aBoolean]. >>> >>> (self enabled not and: [self label isMorph and: [(self label respondsTo: #enabled:) not]]) >>> >>> >>> by construction a labelObject should be a morph and it should answer enabled: and the case where this is not the case should be fixed. >>> >>> >>> Using submorphs to avoid one single inst var makes code quite ugly to read: >>> >>> >>> labelMorph >>> "Answer the actual label morph." >>> >>> self hasSubmorphs ifFalse: [^nil]. >>> self firstSubmorph hasSubmorphs ifFalse: [^nil]. >>> ^self firstSubmorph firstSubmorph >>> >>> >>> >>> >>> >>> _______________________________________________ >>> 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 >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 23, 2010

Re: [Pharo-project] akuhn/SUnit: run faster tests first & step through tests

by Niko Schwarz

What's the status of akuhn/SUnit? I couldn't find his code in 1.2 core. Niko On Wed, Feb 3, 2010 at 1:13 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > this loads well in the latest 1,1 core :) > so now we should really have a look and these cool changes > > Stef > > On Jan 6, 2010, at 2:38 PM, Adrian Kuhn wrote: > >> SystemChangeNotifier uniqueInstance >> Â Â Â Â Â Â Â Â noMoreNotificationsFor: TestCase. >> Â Â Â Gofer it >> Â Â Â Â Â Â Â disablePackageCache; >> Â Â Â Â Â Â Â squeaksource: 'akuhn'; >> Â Â Â Â Â Â Â package: 'SUnit'; >> Â Â Â Â Â Â Â package: 'SUnitGUI'; >> Â Â Â Â Â Â Â load. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- http://scg.unibe.ch/staff/Schwarz twitter.com/nes1983 Tel: +41 076 235 8683

Oct. 23, 2010

Re: [Pharo-project] a useful check

by Igor Stasenko

On 23 October 2010 14:36, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > What is the way to fix that? > something ifTrue: [ [ code which never runs ] ] -->> something ifTrue: [ code which now can run ] unless, of course it is used like: block := something ifTrue: [ [block1 ] ] ifFalse: [ [block2]]. > >> SystemNavigation new browseAllSelect: >> Â Â Â [:m| | is | >> Â Â Â is := InstructionStream on: m. >> Â Â Â is scanFor: [:b| b = 143 and: [(m at: is thirdByte * 256 + is fourthByte + is pc + 4) = 135]]] > > > lookForCode: code ifDifferent: handleBlock > Â Â Â Â "We are expecting a certain numeric code next. > Â Â Â Â However, in the FTP protocol, multiple lines are allowed. > Â Â Â Â If the response is multi-line, the fourth character of the first line is a > Â Â Â Â $- and the last line repeats the numeric code but the code is followed by > Â Â Â Â a space. So it's possible that there are more lines left of the last response that > Â Â Â Â we need to throw away. We use peekForAll: so that we don't discard the > Â Â Â Â next response that is not a continuation line." > > > Â Â Â Â "check for multi-line response" > Â Â Â Â (self lastResponse size > 3 > Â Â Â Â Â Â Â Â Â Â Â Â and: [(self lastResponse at: 4) = $-]) > Â Â Â Â Â Â Â Â ifTrue: ["Discard continuation lines." > Â Â Â Â Â Â Â Â Â Â Â Â [ | headToDiscard | > Â Â Â Â Â Â Â Â Â Â Â Â headToDiscard := self lastResponse first: 4. > Â Â Â Â Â Â Â Â Â Â Â Â [[self stream peekForAll: headToDiscard] > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â whileTrue: [self stream nextLine]] > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â on: Exception > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â do: [:ex | ^handleBlock value: nil]]]. > Â Â Â Â ^ super lookForCode: code ifDifferent: handleBlock > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

Oct. 23, 2010

[Pharo-project] if you want to join the pharo sprint

by StÃ©phane Ducasse

skype stducasse, we chat there. Stef

Oct. 23, 2010

Re: [Pharo-project] some patterns I would like to **kill**

by Igor Stasenko

On 23 October 2010 14:33, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I think that if you have a container that contains morphs probably findA and other queries are useful. > Now for a button that is also at the same place a field is the best. > <sarcasm> if morph having a random submorphs, inserted out of nowhere, just for fun to see what happen. then yes.. findA is userful, as well as respondsTo: </sarcasm> but if we are talking about specific morphs, like Pluggable and friends, who serving a certain purpose (building UI from spec), where no place for 'random', then this truly a bad design. > Stef > > > On Oct 22, 2010, at 11:14 PM, Schwab,Wilhelm K wrote: > >> Stef, >> >> #respondsTo: - no argument. Â More defensive programming (aka masked bugs). Â Tests like this have their place, but are over-used in Squeak. >> >> Using #submorphs *might* be easier to defend. Â Morphs were designed to be usable in large numbers, and one might argue (playing Devil's Advocate here) that lookups are cheaper than the additional gc load. Â An instance variable could also cache stale information. Â Of course, for something that is accessed frequently, an instance variable avoids the lookup and I agree that it is cleaner and easier to read. >> >> Bill >> >> >> >> ________________________________________ >> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of stephane ducasse [stephane.ducasse(a)free.fr] >> Sent: Thursday, October 21, 2010 4:47 PM >> To: Pharo Development >> Subject: [Pharo-project] some patterns I would like to **kill** >> >> Hi >> >> I was reading Pluggable and friends >> I identified some patterns. >> >> >> The respondsTo plague >> Examples: >> >> color := self fillStyle asColor. >> Â Â Â Â (self labelMorph respondsTo: #enabled:) >> Â Â Â Â Â Â Â Â ifTrue: [self labelMorph enabled: self enabled]. >> Â Â Â Â (self labelMorph respondsTo: #interactionState:) >> Â Â Â Â Â Â Â Â ifTrue: [self labelMorph interactionState: self interactionState] >> >> (self labelMorph respondsTo: #enabled:) ifTrue: [ >> Â Â Â Â self labelMorph enabled: aBoolean]. >> >> (self enabled not and: [self label isMorph and: [(self label respondsTo: #enabled:) not]]) >> >> >> by construction a labelObject should be a morph and it should answer enabled: and the case where this is not the case should be fixed. >> >> >> Using submorphs to avoid one single inst var makes code quite ugly to read: >> >> >> labelMorph >> Â Â Â Â "Answer the actual label morph." >> >> Â Â Â Â self hasSubmorphs ifFalse: [^nil]. >> Â Â Â Â self firstSubmorph hasSubmorphs ifFalse: [^nil]. >> Â Â Â Â ^self firstSubmorph firstSubmorph >> >> >> >> >> >> _______________________________________________ >> 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 > -- Best regards, Igor Stasenko AKA sig.

Oct. 23, 2010

Re: [Pharo-project] Object>>at:modify:???

by Mariano Martinez Peck

On Sat, Oct 23, 2010 at 1:32 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Ok we can deprecate it. > > ys, but please please please use deprecated: anExplanationString on: date in: version cheers mariano > On Oct 22, 2010, at 11:04 PM, Hernan Wilkinson wrote: > > > In a 1.1 image I have, the class HttpRequest is using that message... > > > > On Thu, Oct 21, 2010 at 4:08 PM, stephane ducasse < > stephane.ducasse(a)free.fr> wrote: > > I would like to deprecate the following method since nobody use it. > > What do you think? > > > > Stef > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > > > -- > > HernÃ¡n Wilkinson > > Agile Software Development, Teaching & Coaching > > Mobile: +54 - 911 - 4470 - 7207 > > email: hernan.wilkinson(a)10Pines.com > > site: http://www.10Pines.com > > > > _______________________________________________ > > 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 >

Oct. 23, 2010

Re: [Pharo-project] a useful check

by StÃ©phane Ducasse

What is the way to fix that? > SystemNavigation new browseAllSelect: > [:m| | is | > is := InstructionStream on: m. > is scanFor: [:b| b = 143 and: [(m at: is thirdByte * 256 + is fourthByte + is pc + 4) = 135]]] lookForCode: code ifDifferent: handleBlock "We are expecting a certain numeric code next. However, in the FTP protocol, multiple lines are allowed. If the response is multi-line, the fourth character of the first line is a $- and the last line repeats the numeric code but the code is followed by a space. So it's possible that there are more lines left of the last response that we need to throw away. We use peekForAll: so that we don't discard the next response that is not a continuation line." "check for multi-line response" (self lastResponse size > 3 and: [(self lastResponse at: 4) = $-]) ifTrue: ["Discard continuation lines." [ | headToDiscard | headToDiscard := self lastResponse first: 4. [[self stream peekForAll: headToDiscard] whileTrue: [self stream nextLine]] on: Exception do: [:ex | ^handleBlock value: nil]]]. ^ super lookForCode: code ifDifferent: handleBlock

Oct. 23, 2010

Re: [Pharo-project] some patterns I would like to **kill**

by StÃ©phane Ducasse

I think that if you have a container that contains morphs probably findA and other queries are useful. Now for a button that is also at the same place a field is the best. Stef On Oct 22, 2010, at 11:14 PM, Schwab,Wilhelm K wrote: > Stef, > > #respondsTo: - no argument. More defensive programming (aka masked bugs). Tests like this have their place, but are over-used in Squeak. > > Using #submorphs *might* be easier to defend. Morphs were designed to be usable in large numbers, and one might argue (playing Devil's Advocate here) that lookups are cheaper than the additional gc load. An instance variable could also cache stale information. Of course, for something that is accessed frequently, an instance variable avoids the lookup and I agree that it is cleaner and easier to read. > > Bill > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of stephane ducasse [stephane.ducasse(a)free.fr] > Sent: Thursday, October 21, 2010 4:47 PM > To: Pharo Development > Subject: [Pharo-project] some patterns I would like to **kill** > > Hi > > I was reading Pluggable and friends > I identified some patterns. > > > The respondsTo plague > Examples: > > color := self fillStyle asColor. > (self labelMorph respondsTo: #enabled:) > ifTrue: [self labelMorph enabled: self enabled]. > (self labelMorph respondsTo: #interactionState:) > ifTrue: [self labelMorph interactionState: self interactionState] > > (self labelMorph respondsTo: #enabled:) ifTrue: [ > self labelMorph enabled: aBoolean]. > > (self enabled not and: [self label isMorph and: [(self label respondsTo: #enabled:) not]]) > > > by construction a labelObject should be a morph and it should answer enabled: and the case where this is not the case should be fixed. > > > Using submorphs to avoid one single inst var makes code quite ugly to read: > > > labelMorph > "Answer the actual label morph." > > self hasSubmorphs ifFalse: [^nil]. > self firstSubmorph hasSubmorphs ifFalse: [^nil]. > ^self firstSubmorph firstSubmorph > > > > > > _______________________________________________ > 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

Oct. 23, 2010