- Pharo-dev - lists.pharo.org

Re: [Pharo-project] implementors of

by Damien Cassou

On Tue, Sep 22, 2009 at 6:11 AM, Ross Boylan <ross(a)biostat.ucsf.edu> wrote: > In the system browser I have PRAjaxSearchWidget>>renderContentOn: > selected. Â When I hit the "implementors" button, or when I highlight a > method name in the body of renderContentOn: and hit alt-m, I only get > implementors of renderContentOn:. > > Is it supposed to work this way? Â Is there a convenient way to get a > list of all the methods in body of renderContentOn:, and pick one to see > its implementors (as in vanilla squeak, at least 3.10). > > I'm working with Pier-1.2.app.zip downloaded a few days ago from the > Pier site. Â Running on Linux. The list of messages sent in a method only appears in some browsers and not others (this is a choice of Colin and/or Lukas who don't like this list IIRC). So, if you can't live without this list, you have to install the O2-based browsers. Since it's a bit tricky, I advise you to use the latest Pharo web (http://pharo-project.org/pharo-download) and change the default browser (click on the top-right icon of any browser and 'Choose new default Browser'). Bye -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Sept. 22, 2009

Re: [Pharo-project] errata for pharo by example

by Damien Cassou

On Tue, Sep 22, 2009 at 12:06 AM, Chris Kassopulo <ckasso(a)sprynet.com> wrote: > pg 8 > > BouncingAtomsMorph new openInWorld > > Unknown variable: BouncingAtomsMorph That works in latest Pharo: http://pharo-project.org/pharo-download -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Sept. 22, 2009

Re: [Pharo-project] implementors of

by StÃ©phane Ducasse

which browser are you using because OB2Package is in flux. Stef On Sep 22, 2009, at 6:11 AM, Ross Boylan wrote: > In the system browser I have PRAjaxSearchWidget>>renderContentOn: > selected. When I hit the "implementors" button, or when I highlight a > method name in the body of renderContentOn: and hit alt-m, I only get > implementors of renderContentOn:. > > Is it supposed to work this way? Is there a convenient way to get a > list of all the methods in body of renderContentOn:, and pick one to > see > its implementors (as in vanilla squeak, at least 3.10). > > I'm working with Pier-1.2.app.zip downloaded a few days ago from the > Pier site. Running on Linux. > > Thanks. > Ross > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 22, 2009

Re: [Pharo-project] errata for pharo by example

by StÃ©phane Ducasse

You should load the PharoMorphic/DemoAndExamplePackage they should be added to pharo-dev On Sep 22, 2009, at 12:06 AM, Chris Kassopulo wrote: > pg 8 > > BouncingAtomsMorph new openInWorld > > Unknown variable: BouncingAtomsMorph > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 22, 2009

[Pharo-project] implementors of

by Ross Boylan

In the system browser I have PRAjaxSearchWidget>>renderContentOn: selected. When I hit the "implementors" button, or when I highlight a method name in the body of renderContentOn: and hit alt-m, I only get implementors of renderContentOn:. Is it supposed to work this way? Is there a convenient way to get a list of all the methods in body of renderContentOn:, and pick one to see its implementors (as in vanilla squeak, at least 3.10). I'm working with Pier-1.2.app.zip downloaded a few days ago from the Pier site. Running on Linux. Thanks. Ross

Sept. 22, 2009

[Pharo-project] errata for pharo by example

by Chris Kassopulo

pg 8 BouncingAtomsMorph new openInWorld Unknown variable: BouncingAtomsMorph

Sept. 21, 2009

Re: [Pharo-project] Closure fixes

by Michael Roberts

For anyone actually reviewing this, it breaks after Part 4. Inability to recompile the system. There are MethodProperties around but i'm not sure there should be. need to look closer at the trunk update mechanism. cheers, Mike "A. Load Gofer" ScriptLoader new installGofer. "B. Install packages" | gofer packages | gofer := Gofer new. gofer url: 'http://www.squeaksource.com/PharoTaskForces'. packages := #( "Part 2" 'Kernel-MikeRoberts.405' "Part 3" 'Compiler-MikeRoberts.130' 'CompilerTests-MikeRoberts.21' 'KernelTests-MikeRoberts.150' "Part 4" 'Compiler-MikeRoberts.131'). packages do: [:each | gofer copy add: each; load].

Sept. 21, 2009

Re: [Pharo-project] [squeak-dev] About Collections-ul.137..140

by Ralph Boland

Further comments on fasterSets. My understanding is that the newer version of fasterSets is scheduled to be incorporated into Pharo1.1. It would be unfortunate if one version of fasterSets is incorporated into Squeak and a different version is incorporated into Pharo. Can we get together and decide on one or better still merge the best features of both. I am frustrated by this split so cannot be considered unbiased. Can someone qualified and unbiased be appointed to coordinate creating a version of fasterSets that both the Squeak people and Pharo people are happy with and contains the best features of both. I am willing to work on the problem. P.S. My understanding was that there was no interest in having fasterSets added to Squeak. If/when this changed I would have appreciated being brought into the loop. Regards, Ralph Boland 2009/9/21 Ralph Boland <rpboland(a)gmail.com>: > 2009/9/21 Damien Cassou <damien.cassou(a)gmail.com>: >> ---------- Forwarded message ---------- >> From: Levente Uzonyi <leves(a)elte.hu> >> Date: Sun, Sep 20, 2009 at 4:38 PM >> Subject: [squeak-dev] About Collections-ul.137..140 >> To: squeak-dev(a)lists.squeakfoundation.org >> >> >> Hi! >> >> Just uploaded four packages to inbox: Collections-ul.137, >> Collections-ul.138, Collections-ul.139 and Collections-ul.140. These >> packages reimplement #rehash and #grow in Set and its subclasses >> (except MethodDictionary). The ideas come are from Ralph Boland's >> FasterSets project, but the implementation is different. According to >> my measurements they are even faster. The four packages should be >> loaded in the given order one-by-one otherwise mc might remove old >> methods before adding new ones, etc (couldn't come up with a better mc >> based load mechanism). >> >> While I was rewriting these methods, I found that KeyedSet and >> KeyedIdentitySet are not used (no references, no senders) in the >> trunk. >> Also checked that in a 3.8.1 full image they have no references (just >> senders in DecompilerTests >> #decompilerDiscrepancies). I think they >> might be removed from the base image and moved to a separate package. >> >> Cheers, >> Levente >> >> >> >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Lambdas are relegated to relative obscurity until Java makes them >> popular by not having them." James Iry >> > > > It sounds like you are using an older version of fasterSets. Â The > original version did not make the > modifications for Method dictionary but the new version does. Â I also > made a number of other improvements. > I suggest you test your version to the version currently in fasterSets > to see which one is actually faster. > Note that fasterSets has code for measuring performance at least in > terms of the number of compares. > Perhaps you can make the comparision and post the results. Â I would > like to see them. > I suggest that you study the current version of fasterSets and your > version and combine the best > features of both. > > If you wanted to make improvements I don't know why you didn't start > from the newer version. > I believe it was Damien Cassou who proposed that I make most of them. > I also asked that any modifications be incorporated into fasterSets > but I assume you have not done this. > > > Regards, > > Ralph Boland >

Sept. 21, 2009

Re: [Pharo-project] Fwd: [squeak-dev] About Collections-ul.137..140

by StÃ©phane Ducasse

Hi ralph May be I missed something. > It sounds like you are using an older version of fasterSets. The > original version did not make the > modifications for Method dictionary but the new version does. I also > made a number of other improvements. Are you talking about the pharo version? Because I integrated the version I thought was the best > I suggest you test your version to the version currently in fasterSets > to see which one is actually faster. > Note that fasterSets has code for measuring performance at least in > terms of the number of compares. > Perhaps you can make the comparision and post the results. I would > like to see them. > I suggest that you study the current version of fasterSets and your > version and combine the best > features of both. > > If you wanted to make improvements I don't know why you didn't start > from the newer version. > I believe it was Damien Cassou who proposed that I make most of them. > I also asked that any modifications be incorporated into fasterSets > but I assume you have not done this. to who are you talking to? Pharo integrator (me, marcus...) or do the squeak guy. Stef

Sept. 21, 2009

Re: [Pharo-project] Package loader on Pharo

by StÃ©phane Ducasse

> This is confusing for me. this is simple ScriptLoader should be named ThePrivateClassIntegratorUseToIntegrateAndManageRelease > Maybe the Pharo board should take a decision now in order to the > community to push it. There are: > > ChangeSets ok to keep to manage simple changes > ScriptLoader private don't use don't look at it is crap (I wrote) > Monticello alone ok > Monticello configurations ok > Metacello will manage group of packages and projects based on Monticello > Installer to script different code input > Gofer to script Monticello > They share a lot of overlapped functionality. Some scripts use one of > them, some other. This confuse the developers and the community. Maybe > now is the moment to discuss the tools in order to polish them and use > them, at leas until a new tool arrives that is better than the used by > Pharo. > > You said that ScriptLoader will not be part of the core image but as I > can see, only ScriptLoader and Installer can be installed directly > from > the web in an image that it doesn't have it. > > Can the community discuss this? Or the Pharo board write its opinion? done :)

Sept. 21, 2009