August 2008 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] A thought about Morphic and Seaside

by StÃ©phane Ducasse

Yes damien is right. Stef > >> A side related question. >> I wonder, when you have more instance variable referencing the same >> object, does it make more difficult to get unused object garbage >> collected? >> In DrGeo I *fell* I have this kind of problem with object referenced >> in other object and vis-versa, then never garbage collected. Or did I >> miss something? > > I'm unsure it answers your question but the garbage collector should > be able to detect cycles of unused objects and delete them. > > > -- > 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

Aug. 18, 2008

Re: [Pharo-project] test report for pharo0.1-10050web08.08.1 image

by StÃ©phane Ducasse

yes Stef On Aug 18, 2008, at 9:07 AM, Damien Cassou wrote: > On Mon, Aug 18, 2008 at 9:02 AM, laurent laffont > <laurent.laffont(a)gmail.com> wrote: >> >> >> On Sun, Aug 17, 2008 at 5:30 PM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >>> >>> Ok I will fix the halt in regex. >>> BTW it would be good to have a continuous test runner on pharo and >>> not >>> pharo-dev >> >> OK, I'll have to update my tools to be independant of Monticello and >> XML-Parser as these packages are not included in pharo. > > Monticello is included. If you need XML-Parser, I guess it's ok to > install it along with ContinuousIntegration. > > > -- > 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

Aug. 18, 2008

[Pharo-project] Fwd: BasicButton for fun

by StÃ©phane Ducasse

Begin forwarded message: > From: StÃ©phane Ducasse <stephane.ducasse(a)univ-savoie.fr> > Date: August 17, 2008 10:43:51 PM CEDT > To: An open mailing list to discuss any topics related to an open- > source Smalltalk <Pharo-project(a)lists.gforge.inria.fr> > Subject: BasicButton for fun > > In fact this is fun to see that even font default are inconsistent... > > TextStyle defaultFont is different from Preferences standardButtonFont > > But it may be worth checking the senders of allMorphDo: or submorph... > > > > > > stef

Aug. 18, 2008

Re: [Pharo-project] test report for pharo0.1-10050web08.08.1 image

by laurent laffont

> http://www.squeaksource.com/XMLSupport. XML-Parser and > ContinuousIntegration won't be included into Pharo but you can load > them before running the tests without problem. > OK, thank you. -- Laurent Laffont

Aug. 18, 2008

Re: [Pharo-project] test report for pharo0.1-10050web08.08.1 image

by Damien Cassou

On Mon, Aug 18, 2008 at 9:24 AM, laurent laffont <laurent.laffont(a)gmail.com> wrote: >> > OK, I'll have to update my tools to be independant of Monticello and >> > XML-Parser as these packages are not included in pharo. >> >> Monticello is included. If you need XML-Parser, I guess it's ok to >> install it along with ContinuousIntegration. > > I cannot find where to get XML-Parser package (not on squeaksource ?) If I > can script the loading of this package as I do with ContinuousIntegration > package, work is done... As I understand, one objective of Pharo is to keep > it small, so it's not better to avoid XML-Parser and ContinuousIntegration > to be included in Pharo ? http://www.squeaksource.com/XMLSupport. XML-Parser and ContinuousIntegration won't be included into Pharo but you can load them before running the tests without problem. -- 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)

Aug. 18, 2008

Re: [Pharo-project] A thought about Morphic and Seaside

by Damien Cassou

On Mon, Aug 18, 2008 at 9:13 AM, Hilaire Fernandes <hilaire(a)ofset.org> wrote: > A side related question. > I wonder, when you have more instance variable referencing the same > object, does it make more difficult to get unused object garbage > collected? > In DrGeo I *fell* I have this kind of problem with object referenced > in other object and vis-versa, then never garbage collected. Or did I > miss something? I'm unsure it answers your question but the garbage collector should be able to detect cycles of unused objects and delete them. -- 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)

Aug. 18, 2008

Re: [Pharo-project] test report for pharo0.1-10050web08.08.1 image

by laurent laffont

> > OK, I'll have to update my tools to be independant of Monticello and > > XML-Parser as these packages are not included in pharo. > > Monticello is included. If you need XML-Parser, I guess it's ok to > install it along with ContinuousIntegration. > I cannot find where to get XML-Parser package (not on squeaksource ?) If I can script the loading of this package as I do with ContinuousIntegration package, work is done... As I understand, one objective of Pharo is to keep it small, so it's not better to avoid XML-Parser and ContinuousIntegration to be included in Pharo ? -- Laurent Laffont

Aug. 18, 2008

Re: [Pharo-project] A thought about Morphic and Seaside

by Hilaire Fernandes

A side related question. I wonder, when you have more instance variable referencing the same object, does it make more difficult to get unused object garbage collected? In DrGeo I *fell* I have this kind of problem with object referenced in other object and vis-versa, then never garbage collected. Or did I miss something? Hilaire 2008/8/17 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Hello guys > > We were browsing code with marcus and I realized something quite funny about > Morphic. > Morphic is somehow close to seaside for the following point: > > There is a list that contains the children. In Seaside you have to return a > list containing the children > components too. Now this is really interesting to see that a lot of > complexity in Morphic code > comes from the fact that the programmers avoided to have an instance > variable for an element > to the pretext that the element was already in the submorphs list. > > Then you end up with code like > > label: aString > > | oldLabel m | > (oldLabel := self findA: StringMorph) > ifNotNil: [oldLabel delete]. > m := StringMorph contents: aString font: TextStyle defaultFont. > self extent: m extent + (borderWidth + 6). > m position: self center - (m extent // 2). > self addMorph: m. > m lock > > label > | s | > s := ''. > self allMorphsDo: [:m | (m isKindOf: StringMorph) ifTrue: [s := m > contents]]. > ^ s > > instead of > > label > ^ label > > label: aString > > .... > > where you have to query the submorph of the right kind.... > > Marcus was mentioning to me that Morphic is a bit like applying > GraphTraversal that the law of demeter > guy loves so much. And we see the results, an ugly code all over the places. > > So I will certainly play a bit with this design difference to see what it > makes. But I'm sure now it makes a big difference. > > stef > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- http://blog.ofset.org/hilaire

Aug. 18, 2008

Re: [Pharo-project] test report for pharo0.1-10050web08.08.1 image

by Damien Cassou

On Mon, Aug 18, 2008 at 9:02 AM, laurent laffont <laurent.laffont(a)gmail.com> wrote: > > > On Sun, Aug 17, 2008 at 5:30 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> >> Ok I will fix the halt in regex. >> BTW it would be good to have a continuous test runner on pharo and not >> pharo-dev > > OK, I'll have to update my tools to be independant of Monticello and > XML-Parser as these packages are not included in pharo. Monticello is included. If you need XML-Parser, I guess it's ok to install it along with ContinuousIntegration. -- 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)

Aug. 18, 2008

Re: [Pharo-project] test report for pharo0.1-10050web08.08.1 image

by laurent laffont

On Sun, Aug 17, 2008 at 5:30 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Ok I will fix the halt in regex. > BTW it would be good to have a continuous test runner on pharo and not > pharo-dev OK, I'll have to update my tools to be independant of Monticello and XML-Parser as these packages are not included in pharo. Laurent Laffont

Aug. 18, 2008