- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Reintegration of StringSocket

by Damien Cassou

On Tue, Jun 17, 2008 at 3:41 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > I've just published a new version of Universes which includes > StringSocket and its super class ObjectSocket (renamed > StringSocketStream and ObjectSocketStream). I have also replaced > direct references to other Nebraska classes (CanvasEncoder and > NebraskaDebuger) to: > > Smalltalk at: #NebraskaDebugger ifPresent: [:debug | debug ...]. > > It seems to me these classes were only used to log things. Do you agree Lex? >From Lex who is not on the list: Â«Yes, that looks like a great change. Also, I like the general strategy of splitting StringSocket from Nebraska. StringSocket was always meant to be usable by itself.Â» -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

June 18, 2008

Re: [Pharo-project] Missing PluggableTextController and PluggableTextView

by Alain Plantec

On Tuesday 17 June 2008 14:43:29 Alain Plantec wrote: > On Tuesday 17 June 2008 14:25:28 Damien Cassou wrote: >> > I've found another problem related to view instance variable + OB. > I will report it tonight. Hi Damien and Andrew, Controller 'view' instance variable has been removed. In pharo-dev, Undeclared shows a 'view' key which is referenced from OBTextMorphEditor, OBTextMorphEditorWithShout and TextMorphForShoutEditor. I've attached 2 separated fixes (for OB and for shout). Cheers alain > > cheers > alain > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >

June 18, 2008

Re: [Pharo-project] Re: Re: Re: MissingPluggableTextControllerandPluggableTextView

by StÃ©phane Ducasse

Excellent! Excellent! I like this feeling. Soon (more or less) we will be able to focus on the making of new things (versus the cleaning). Please note that I truly respect what was done (even if I can have really harsh statement), I'm not idiot and know that building is far more difficult than removing them. It would be good to think about a first release of pharo the milestone says: - tests green Stef On Jun 17, 2008, at 4:37 PM, Damien Cassou wrote: > On Tue, Jun 17, 2008 at 4:34 PM, Damien Cassou <damien.cassou(a)gmail.com > > wrote: >>> Unfortunately, I can't add it to Universes > > Done > > -- > Damien Cassou > Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good > luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 17, 2008

Re: [Pharo-project] Re: Missing PluggableTextController andPluggableTextView

by StÃ©phane Ducasse

this would be really cool :) Stef On Jun 17, 2008, at 2:37 PM, Andrew Tween wrote: > I'll take a look and see if I can create a Pharo compatible Shout, > > Andy > > > "Damien Cassou" <damien.cassou(a)gmail.com> wrote in message news:6ac749c10806170525r2da65fbr17a00ce24f0cd041@mail.gmail.com > ... > I've just update my image to 10041 and tried to generate a pharo-dev > from it. However, the process failed while trying to install Shout > because it depends on PluggableTextController and PluggableTextView > which are not in the image anymore. > > -- > Damien Cassou > Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good > luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 17, 2008

Re: [Pharo-project] New pharo-dev based on latest version

by StÃ©phane Ducasse

cooool On Jun 17, 2008, at 3:47 PM, Damien Cassou wrote: > I've just published a new pharo-dev version on: > http://code.google.com/p/pharo/wiki/Downloads?tm=2. It is based on > version 10041 which contains cleaning of MVC. > > -- > Damien Cassou > Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good > luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 17, 2008

Re: [Pharo-project] [ANN] MVC removal step two harvested

by StÃ©phane Ducasse

good that someone is chekcing, I was in a meeting. We should really define a process that should be run by me and after a machine automatically before updates :) Stef On Jun 17, 2008, at 2:23 PM, Norbert Hartl wrote: > On Tue, 2008-06-17 at 13:35 +0200, StÃ©phane Ducasse wrote: >> Hi all >> >> I harvested the changes proposed by alain for the removal of MVC. >> Please test pharo since it was a large change. >> > tests run as expected. There is one obsolete class left which > is referenced by MvcTextEditor. That sounds like it is to be > removed anyway ;) > > Otherwise a > > AppRegistry removeObsolete > > will do. > > Norbert > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 17, 2008

Re: [Pharo-project] ObjectFinalizerTests understanding problems

by Norbert Hartl

On Tue, 2008-06-17 at 16:16 +0200, Adrian Lienhard wrote: > Hi Norbert > > Since there was nobody else replying on the Squeak-dev mailing list, > what do we do? At least, my "fix" is not satisfying as it just works > around the actual problem. But then I don't feel like diving into the > finalization mechanism to fix it. I don't think its critical. I think > we should just remove the test (like they did in 3.10). > I agree. At the moment there is only one method that calls it and that method itself does not have a sender. The only other solution I can see is to change Object>>finalizationRegistry and I wouldn't dare :) +1 Norbert > Cheers, > Adrian > > On Jun 14, 2008, at 12:23 , Norbert Hartl wrote: > > > On Sat, 2008-06-14 at 12:18 +0200, StÃ©phane Ducasse wrote: > >> No idea :) > >> > >> may be ask in the squeak mailing-list? > >> > > You are right :) > > > > Norbert > >> On Jun 14, 2008, at 12:03 PM, Norbert Hartl wrote: > >> > >>> Before I recognized that Adrian fixed the > >>> > >>> ObjectFinalizerTests>>testFinalizationOfEquals > >>> > >>> I gave it try myself. I came to the same conclusion as Adrian > >>> how to fix. But now after knowing how it works I do not know > >>> why the test succeeds :) > >>> > >>> The test uses > >>> > >>> 1 to: 5 do: [:n | o := Object new. bag add: n. o toFinalizeSend: > >>> #remove: to: bag with: n]. > >>> 1 to: 5 do: [:n | o := Object new. bag add: n. o toFinalizeSend: > >>> #remove: to: bag with: n]. > >>> > >>> My problem is that toFinalizeSend:to:with adds an Objectfinalizer > >>> to the finalizationRegistry of the instance. But > >>> > >>> Object>>finalizationRegistry > >>> "Answer the finalization registry associated with the receiver." > >>> ^WeakRegistry default > >>> > >>> returns a global object which is WeakKeyDictionary. And > >>> > >>> | d | > >>> d := WeakKeyDictionary new. > >>> d at: (1 asString copy) put: $a. > >>> d at: (1 asString copy) put: $b. > >>> d size > >>> > >>> prints 1. To me that would exchange every entry from the first > >>> run by the second run (because the objects are equal). > >>> > >>> So I would assume that if there does not happen a run of the > >>> garbagecollector between the two loops the objects of the first > >>> loop should be still contained in the bag. But the test is named > >>> finalizationOfEquals so I have to assume: self doesNotUnderstand > >>> > >>> Can someone explain it to me, please? > >>> > >>> Norbert > >>> > >>> > >>> _______________________________________________ > >>> 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 17, 2008

Re: [Pharo-project] Re: Re: Re: MissingPluggableTextControllerandPluggableTextView

by Damien Cassou

On Tue, Jun 17, 2008 at 4:34 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: >> Unfortunately, I can't add it to Universes Done -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

June 17, 2008

Re: [Pharo-project] Re: Re: Re: MissingPluggableTextControllerandPluggableTextView

by Damien Cassou

On Tue, Jun 17, 2008 at 4:03 PM, Andrew Tween <amtween(a)hotmail.com> wrote: > I have created the http://www.squeaksource.com/shout/Shout.3.15-tween.71.mcz > package which no longer contains MVC stuff. Thank you very much > Unfortunately, I can't add it to Universes - the Universe editor tells me it > is owned by someone else :( It's probably me :-). > I agree with your suggestion of not supporting MVC in squeak-dev images > anymore. Cool -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

June 17, 2008

Re: [Pharo-project] ObjectFinalizerTests understanding problems

by Adrian Lienhard

Hi Norbert Since there was nobody else replying on the Squeak-dev mailing list, what do we do? At least, my "fix" is not satisfying as it just works around the actual problem. But then I don't feel like diving into the finalization mechanism to fix it. I don't think its critical. I think we should just remove the test (like they did in 3.10). Cheers, Adrian On Jun 14, 2008, at 12:23 , Norbert Hartl wrote: > On Sat, 2008-06-14 at 12:18 +0200, StÃ©phane Ducasse wrote: >> No idea :) >> >> may be ask in the squeak mailing-list? >> > You are right :) > > Norbert >> On Jun 14, 2008, at 12:03 PM, Norbert Hartl wrote: >> >>> Before I recognized that Adrian fixed the >>> >>> ObjectFinalizerTests>>testFinalizationOfEquals >>> >>> I gave it try myself. I came to the same conclusion as Adrian >>> how to fix. But now after knowing how it works I do not know >>> why the test succeeds :) >>> >>> The test uses >>> >>> 1 to: 5 do: [:n | o := Object new. bag add: n. o toFinalizeSend: >>> #remove: to: bag with: n]. >>> 1 to: 5 do: [:n | o := Object new. bag add: n. o toFinalizeSend: >>> #remove: to: bag with: n]. >>> >>> My problem is that toFinalizeSend:to:with adds an Objectfinalizer >>> to the finalizationRegistry of the instance. But >>> >>> Object>>finalizationRegistry >>> "Answer the finalization registry associated with the receiver." >>> ^WeakRegistry default >>> >>> returns a global object which is WeakKeyDictionary. And >>> >>> | d | >>> d := WeakKeyDictionary new. >>> d at: (1 asString copy) put: $a. >>> d at: (1 asString copy) put: $b. >>> d size >>> >>> prints 1. To me that would exchange every entry from the first >>> run by the second run (because the objects are equal). >>> >>> So I would assume that if there does not happen a run of the >>> garbagecollector between the two loops the objects of the first >>> loop should be still contained in the bag. But the test is named >>> finalizationOfEquals so I have to assume: self doesNotUnderstand >>> >>> Can someone explain it to me, please? >>> >>> Norbert >>> >>> >>> _______________________________________________ >>> 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 17, 2008