- Pharo-dev - lists.pharo.org

[Pharo-project] [ANN] Core image #10342

by Marcus Denker

https://gforge.inria.fr/frs/download.php/22466/Pharo0.1Core-10342.zip -- Marcus Denker - http://marcusdenker.de PLEIAD Lab - Computer Science Department (DCC) - University of Chile

June 17, 2009

Re: [Pharo-project] [Fix] Issue890 Mantis6535 SortedCollection loose sortBlock

by Damien Cassou

On Wed, Jun 17, 2009 at 5:44 PM, Marcus Denker<denker(a)acm.org> wrote: > Helps a little... but it feels to me that displaying a method, the > slowest > part is the Annotationpane. Maybe we can turn that off? It's off in > the core > image, too. I have tried disabling it but haven't felt any difference. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

June 17, 2009

Re: [Pharo-project] [Fix] Issue890 Mantis6535 SortedCollection loose sortBlock

by Marcus Denker

On 17.06.2009, at 09:34, Damien Cassou wrote: > On Wed, Jun 17, 2009 at 2:32 PM, Marcus Denker<denker(a)acm.org> wrote: >> I wonder if OB would not be much faster if the auto-category feature >> would >> be turned off? > > are you talking about the dynamic protocols (long methods, > override...)? They are much faster than before. You can disable them > to see if they are a source of slowdowns by going to the preference > browser, 'dynamic protocols' category. > Helps a little... but it feels to me that displaying a method, the slowest part is the Annotationpane. Maybe we can turn that off? It's off in the core image, too. Marcus

June 17, 2009

Re: [Pharo-project] MIT ScaledDecimal (Issue 816) has not been integrated correctly

by StÃ©phane Ducasse

Ok nicolas Sorry for the problem. I guess that I will wait for the code snippet stef writing should be writing a boring report for a month ago :) On Jun 17, 2009, at 3:09 PM, Nicolas Cellier wrote: > in update10307 (script385) related to > http://code.google.com/p/pharo/issues/detail?id=816 : > > ScaledDecimal2-Part1-nice.1.cs had a postscript to mutate old > instances to new instances and not losse existing ScaledDecimals (at > least the literals in ScaledDecimalTests). > > This has not been applied, so some ScaledDecimal now have a nil > numerator and denominator. > This makes some tests fail. > > Cure: detect and recompile these methods having a broken > ScaledDecimal literal. > I don't have time to give a code snippet by now... > > Nicolas > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 17, 2009

Re: [Pharo-project] [Fix] Issue890 Mantis6535 SortedCollection loose sortBlock

by Damien Cassou

On Wed, Jun 17, 2009 at 2:32 PM, Marcus Denker<denker(a)acm.org> wrote: > I wonder if OB would not be much faster if the auto-category feature > would > be turned off? are you talking about the dynamic protocols (long methods, override...)? They are much faster than before. You can disable them to see if they are a source of slowdowns by going to the preference browser, 'dynamic protocols' category. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

June 17, 2009

Re: [Pharo-project] testWhileModificationBeforeNotInlined

by Nicolas Cellier

2009/6/17 Adrian Lienhard <adi(a)netstyle.ch> > > On Jun 17, 2009, at 13:37 , StÃ©phane Ducasse wrote: > > > I would really like that we do not lose it. > > May be lukas we should tagged them > > We should check the SunitExtension of keith to see if he has something > > to support > > supposed to fail tests. > > We have this already: #expectedFailures. > > Adrian Stephane was maybe thinking of an Annotation rewrite... > > > > > > On Jun 17, 2009, at 12:19 PM, Lukas Renggli wrote: > > > >>> The point remains:some well known failing tests that won't be > >>> solved should > >>> go in known failures. > >> > >> Yes, agreed. I thought a fix would soon be available, but that > >> doesn't > >> seem the case. > >> > >> Anyway, most Smalltalk choke on these tests. > >> > >> Lukas > >> > >> -- > >> Lukas Renggli > >> http://www.lukas-renggli.ch > >> > >> _______________________________________________ > >> 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, 2009

[Pharo-project] MIT ScaledDecimal (Issue 816) has not been integrated correctly

by Nicolas Cellier

in update10307 (script385) related to http://code.google.com/p/pharo/issues/detail?id=816 : ScaledDecimal2-Part1-nice.1.cs had a postscript to mutate old instances to new instances and not losse existing ScaledDecimals (at least the literals in ScaledDecimalTests). This has not been applied, so some ScaledDecimal now have a nil numerator and denominator. This makes some tests fail. Cure: detect and recompile these methods having a broken ScaledDecimal literal. I don't have time to give a code snippet by now... Nicolas

June 17, 2009

[Pharo-project] Thing which can help developing brand-new GUI framework

by Igor Stasenko

I just thought, that it would be nice having a morph (named WarpGate) which will act as an event sink for any events targeted to it. Then it can translate morphic events to any kind of event, which new framework expecting and dispatch them directly to it. A SystemWindow client area will act as a display surface for framework. -- Best regards, Igor Stasenko AKA sig.

June 17, 2009

Re: [Pharo-project] [Fix] Issue890 Mantis6535 SortedCollection loose sortBlock

by Marcus Denker

On 17.06.2009, at 04:39, Adrian Lienhard wrote: > Hi Nicolas, > > On Jun 16, 2009, at 22:10 , Nicolas Cellier wrote: > > [...] > >> <rant> >> Monticello is quite a drag, and pharo feels globally unresponsive >> (even the core image). > > Yep, responsiveness can be improved. The core feels quite fast for me > (on a MacBook Pro), but still, for example opening a browser is not > instantaneous. Also, if you type really fast, the characters start > appearing late (I think Bill complained about that recently). > > OB is another story. For me, its at the border of being usable because > of its slowness. I wonder if OB would not be much faster if the auto-category feature would be turned off? Marcus

June 17, 2009

Re: [Pharo-project] testWhileModificationBeforeNotInlined

by Adrian Lienhard

On Jun 17, 2009, at 13:37 , StÃ©phane Ducasse wrote: > I would really like that we do not lose it. > May be lukas we should tagged them > We should check the SunitExtension of keith to see if he has something > to support > supposed to fail tests. We have this already: #expectedFailures. Adrian > > On Jun 17, 2009, at 12:19 PM, Lukas Renggli wrote: > >>> The point remains:some well known failing tests that won't be >>> solved should >>> go in known failures. >> >> Yes, agreed. I thought a fix would soon be available, but that >> doesn't >> seem the case. >> >> Anyway, most Smalltalk choke on these tests. >> >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> _______________________________________________ >> 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, 2009