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

[Pharo-project] [update 1.4] #14050

by StÃ©phane Ducasse

14050 ----- Preparation for Ring integration

July 19, 2011

[Pharo-project] How Moprhs is rendered

by Hilaire Fernandes

To optimise the DrGeo canvas (get it faster), I try to understand in detail how is done the rendering of Morphs embedded in a pasteupmorph. I did not find any detailed information on the Internet about that. Any pointer? Right now, DrGeo canvas is a pasteUpMorph, the line, segment, point, circle, etc. are all Morph added in the pasteUpMoprh. When the model of a geometry sketch is updated, then all the Morphs view are updated in one shot (it appeared to be faster than to climb the model tree to update only the morphs needing update) Hilaire -- Education 0.2 -- http://blog.ofset.org/hilaire

July 19, 2011

Re: [Pharo-project] why isEmptyOrNil is not defined in Object?

by Nicolas Cellier

I don't like isEmptyOrNil. It has been introduced mainly because we can now distinguish these two operations in a "FillInTheBlank" - cancel returns nil - accept returns a String eventually empty The original implementation did always return an empty String even if cancel was pressed. But no application is really prepared to deal with nil, and most did interpret an empty String as a cancel. So we replaced the isEmpty checks by isEmptyOrNil... I would have done it differently: 1) let the default return an empty String even if cancelled 2) provide a ifCancelled: addtional key for the rare apps which really need to distinguish. UIManager default request: 'OK ?' initialAnswer: '' ifCancelled: [^nil]. Default behaviour would be equivalent to UIManager default request: 'OK ?' initialAnswer: '' ifCancelled: ['']. So my take would be to deprecate it. Nicolas 2011/7/19 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Hi guys > > I'm puzzled and probably need food. but why isEmptyOrNil is not defined in > Object? > because right now if a variable is '' or nil or something else I cannot use > it. > > Stef >

July 19, 2011

Re: [Pharo-project] why isEmptyOrNil is not defined in Object?

by Lukas Renggli

I would say for the same reason #isEmpty is not defined on Object, but only on Collection. #isEmptyOrNil is the equivalent of obj isNil or: [ obj isEmpty ] (which i find clearer and) which doesn't work on arbitrary objects either. Lukas On Tuesday, 19 July 2011, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > I'm puzzled and probably need food. but why Â isEmptyOrNil is not defined in Object? > because right now if a variable is '' or nil or something else I cannot use it. > > Stef > -- Lukas Renggli www.lukas-renggli.ch

July 19, 2011

[Pharo-project] why isEmptyOrNil is not defined in Object?

by StÃ©phane Ducasse

Hi guys I'm puzzled and probably need food. but why isEmptyOrNil is not defined in Object? because right now if a variable is '' or nil or something else I cannot use it. Stef

July 19, 2011

[Pharo-project] [update 1.4] #14049

by StÃ©phane Ducasse

14049 ----- Merging latest ring core fixes + tests with veronica.

July 19, 2011

Re: [Pharo-project] [update 1.3] #13287

by StÃ©phane Ducasse

Thanks lukas. Our goal is to create a really good system. We do not say that we know everything but this is important to try and build the best system we can. And feedback/discussions/critics are important so that we all make progress. Again Pharo is our system not mine. Stef On Jul 18, 2011, at 8:44 PM, Lukas Renggli wrote: > Great, thank you for the quick fix. > > On Monday, 18 July 2011, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> 13287 >> ----- >> >> - Issue 4528: Exception on:fork: enhancement. Thanks Igor Stasenko and Lukas Renggli for the idea. >> >> - Issue 4529: Announcement delivery breaks if last subscriber is curtailed. Thanks Henrik Johanssen. >> > > -- > Lukas Renggli > www.lukas-renggli.ch >

July 19, 2011

Re: [Pharo-project] Stubbing class-side methods

by Denis Kudriashov

I think not. This way is substitution of method literal. But "self sends" stubbing required anonimous subclass creation with required methods overrides. 2011/7/19 Dennis Schetinin <chaetal(a)gmail.com> > Can we test self sends this way? > > > 2011/7/19 Denis Kudriashov <dionisiydk(a)gmail.com> > >> I should add it to Mocketry. >> >> 2011/7/19 Sean P. DeNigris <sean(a)clipperadams.com> >> >> Ah, so the lookups are done once when the method is compiled and then >>> stored >>> in the CompiledMethod... >>> >>> My vision is to write something like: >>> cannedNow := DateAndTime stub: #now; andReturn: [ DateAndTime >>> year: 2011 >>> month: 12 day: 24 hour: 12 minute: 34 second: 55 ]. >>> testableClass := MyClass usingDouble: cannedNow. >>> >>> The first line seems easy, and for the second line, I have so far (very >>> rough, but working): >>> >>> | class copy | >>> class := MyClass. >>> copy := MyClass copy. >>> >>> copy methods do: [ :m | | classRef | >>> (m hasLiteralSuchThat: [ :l | ((l isKindOf: Association) >>> and: [ l key = >>> #DateAndTime])]) >>> ifTrue: [ | newMeth refIndex | >>> newMeth := copy methodDictionary at: m >>> selector put: m copy. >>> refIndex := newMeth >>> indexOfLiteralSuchThat: [ :l | ((l isKindOf: >>> Association) and: [ l key = #DateAndTime])]. >>> newMeth literalAt: refIndex put: >>> #DateAndTime->MockedClass ] ]. >>> ^ copy. >>> >>> Where CompiledMethod>>indexOfLiteralSuchThat: aBlock >>> "Answer the literal index of the argument, literal, or zero if >>> none." >>> 2 to: self numLiterals - 1 "exclude superclass + >>> selector/properties" >>> do: >>> [:index | >>> (aBlock value: (self objectAt: index)) ifTrue: [^index - >>> 1]]. >>> ^0 >>> >>> Thanks again. >>> Sean >>> >>> >>> -- >>> View this message in context: >>> http://forum.world.st/Stubbing-class-side-methods-tp3674065p3676637.html >>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>> >>> >> > > > -- > Dennis Schetinin >

July 19, 2011

Re: [Pharo-project] Stubbing class-side methods

by Dennis Schetinin

Can we test self sends this way? 2011/7/19 Denis Kudriashov <dionisiydk(a)gmail.com> > I should add it to Mocketry. > > 2011/7/19 Sean P. DeNigris <sean(a)clipperadams.com> > > Ah, so the lookups are done once when the method is compiled and then >> stored >> in the CompiledMethod... >> >> My vision is to write something like: >> cannedNow := DateAndTime stub: #now; andReturn: [ DateAndTime year: >> 2011 >> month: 12 day: 24 hour: 12 minute: 34 second: 55 ]. >> testableClass := MyClass usingDouble: cannedNow. >> >> The first line seems easy, and for the second line, I have so far (very >> rough, but working): >> >> | class copy | >> class := MyClass. >> copy := MyClass copy. >> >> copy methods do: [ :m | | classRef | >> (m hasLiteralSuchThat: [ :l | ((l isKindOf: Association) >> and: [ l key = >> #DateAndTime])]) >> ifTrue: [ | newMeth refIndex | >> newMeth := copy methodDictionary at: m >> selector put: m copy. >> refIndex := newMeth indexOfLiteralSuchThat: >> [ :l | ((l isKindOf: >> Association) and: [ l key = #DateAndTime])]. >> newMeth literalAt: refIndex put: >> #DateAndTime->MockedClass ] ]. >> ^ copy. >> >> Where CompiledMethod>>indexOfLiteralSuchThat: aBlock >> "Answer the literal index of the argument, literal, or zero if >> none." >> 2 to: self numLiterals - 1 "exclude superclass + >> selector/properties" >> do: >> [:index | >> (aBlock value: (self objectAt: index)) ifTrue: [^index - >> 1]]. >> ^0 >> >> Thanks again. >> Sean >> >> >> -- >> View this message in context: >> http://forum.world.st/Stubbing-class-side-methods-tp3674065p3676637.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> > -- Dennis Schetinin

July 19, 2011

Re: [Pharo-project] Stubbing class-side methods

by Denis Kudriashov

I should add it to Mocketry. 2011/7/19 Sean P. DeNigris <sean(a)clipperadams.com> > Ah, so the lookups are done once when the method is compiled and then > stored > in the CompiledMethod... > > My vision is to write something like: > cannedNow := DateAndTime stub: #now; andReturn: [ DateAndTime year: > 2011 > month: 12 day: 24 hour: 12 minute: 34 second: 55 ]. > testableClass := MyClass usingDouble: cannedNow. > > The first line seems easy, and for the second line, I have so far (very > rough, but working): > > | class copy | > class := MyClass. > copy := MyClass copy. > > copy methods do: [ :m | | classRef | > (m hasLiteralSuchThat: [ :l | ((l isKindOf: Association) > and: [ l key = > #DateAndTime])]) > ifTrue: [ | newMeth refIndex | > newMeth := copy methodDictionary at: m > selector put: m copy. > refIndex := newMeth indexOfLiteralSuchThat: > [ :l | ((l isKindOf: > Association) and: [ l key = #DateAndTime])]. > newMeth literalAt: refIndex put: > #DateAndTime->MockedClass ] ]. > ^ copy. > > Where CompiledMethod>>indexOfLiteralSuchThat: aBlock > "Answer the literal index of the argument, literal, or zero if > none." > 2 to: self numLiterals - 1 "exclude superclass + > selector/properties" > do: > [:index | > (aBlock value: (self objectAt: index)) ifTrue: [^index - > 1]]. > ^0 > > Thanks again. > Sean > > > -- > View this message in context: > http://forum.world.st/Stubbing-class-side-methods-tp3674065p3676637.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >

July 19, 2011