October 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] New changes to Gofer

by Tudor Girba

If you want to take a look at the Metacello configuration of Moose, you can find it in the ConfigurationOfMoose package. Cheers, Doru On 22 Oct 2009, at 20:40, StÃ©phane Ducasse wrote: > may be fernando you should have a look at Metacello > because it is used gofer and it will be the way to go soon :) > You can have a look at Glamour, Mondrian or MooseLoader as an example. > > Stef > > On Oct 22, 2009, at 8:34 PM, Fernando olivero wrote: > >> Hi, when loading Lumiere an deprecation warning comes up, seems that >> the Flair configuration and gofer usage change significantly. >> >> Gofer Seems to have a much more expresive protocol now! Great! >> >> But could somebody provide examples on how to implement behavior in a >> loader for >> >> 1. loading the lastest versions of several packages. >> 2. commit to squeaksource some pacakges >> >> Would be really helpfull to update Alien, AlienOpenGL, Lumiere >> loaders. >> >> >> Fernando >> >> _______________________________________________ >> 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 -- www.tudorgirba.com "Beauty is where we see it."

Oct. 22, 2009

Re: [Pharo-project] New changes to Gofer

by StÃ©phane Ducasse

Then Alien will be part of the pharo core :) this way we will be able to have access to platform widgets and more. Stef On Oct 22, 2009, at 8:34 PM, Fernando olivero wrote: > Hi, when loading Lumiere an deprecation warning comes up, seems that > the Flair configuration and gofer usage change significantly. > > Gofer Seems to have a much more expresive protocol now! Great! > > But could somebody provide examples on how to implement behavior in a > loader for > > 1. loading the lastest versions of several packages. > 2. commit to squeaksource some pacakges > > Would be really helpfull to update Alien, AlienOpenGL, Lumiere > loaders. > > > Fernando > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 22, 2009

Re: [Pharo-project] New changes to Gofer

by StÃ©phane Ducasse

may be fernando you should have a look at Metacello because it is used gofer and it will be the way to go soon :) You can have a look at Glamour, Mondrian or MooseLoader as an example. Stef On Oct 22, 2009, at 8:34 PM, Fernando olivero wrote: > Hi, when loading Lumiere an deprecation warning comes up, seems that > the Flair configuration and gofer usage change significantly. > > Gofer Seems to have a much more expresive protocol now! Great! > > But could somebody provide examples on how to implement behavior in a > loader for > > 1. loading the lastest versions of several packages. > 2. commit to squeaksource some pacakges > > Would be really helpfull to update Alien, AlienOpenGL, Lumiere > loaders. > > > Fernando > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 22, 2009

Re: [Pharo-project] New changes to Gofer

by Lukas Renggli

This is the delta to older versions: Please note that I updated the article to match the latest version of Gofer. Instead of just using add: and let Gofer guess what you mean, you have to specify if the string you provide is a package (addPackage:) or a version (addVersion:). This gives predictable results and avoids various problems that we encountered with different package naming conventions. 2009/10/22 Lukas Renggli <renggli(a)gmail.com>: > Check out the class comment of Gofer, which contains this blog post > <http://www.lukas-renggli.ch/blog/gofer>. > > Cheers, > Lukas > > 2009/10/22 Fernando olivero <oliverof(a)lu.unisi.ch>: >> Hi, when loading Lumiere an deprecation warning comes up, seems that >> the Flair configuration and gofer usage change significantly. >> >> Gofer Seems to have a much more expresive protocol now! Great! >> >> But could somebody provide examples on how to implement behavior in a >> loader for >> >> 1. Â loading Â the lastest versions of several packages. >> 2. Â commit to squeaksource some pacakges >> >> Would be really helpfull to update Alien, AlienOpenGL, Lumiere loaders. >> >> >> Fernando >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > -- Lukas Renggli http://www.lukas-renggli.ch

Oct. 22, 2009

Re: [Pharo-project] New changes to Gofer

by Lukas Renggli

Check out the class comment of Gofer, which contains this blog post <http://www.lukas-renggli.ch/blog/gofer>. Cheers, Lukas 2009/10/22 Fernando olivero <oliverof(a)lu.unisi.ch>: > Hi, when loading Lumiere an deprecation warning comes up, seems that > the Flair configuration and gofer usage change significantly. > > Gofer Seems to have a much more expresive protocol now! Great! > > But could somebody provide examples on how to implement behavior in a > loader for > > 1. Â loading Â the lastest versions of several packages. > 2. Â commit to squeaksource some pacakges > > Would be really helpfull to update Alien, AlienOpenGL, Lumiere loaders. > > > Fernando > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli http://www.lukas-renggli.ch

Oct. 22, 2009

[Pharo-project] New changes to Gofer

by Fernando olivero

Hi, when loading Lumiere an deprecation warning comes up, seems that the Flair configuration and gofer usage change significantly. Gofer Seems to have a much more expresive protocol now! Great! But could somebody provide examples on how to implement behavior in a loader for 1. loading the lastest versions of several packages. 2. commit to squeaksource some pacakges Would be really helpfull to update Alien, AlienOpenGL, Lumiere loaders. Fernando

Oct. 22, 2009

Re: [Pharo-project] HashTable vs Dictionary

by John M McIntosh

In the far past Visual Age would become the implementation logic for Sets depending on how big the set was, so for example with 10 elements it would be linear list. Of course it's been 14 years, perhaps I'm remembering it wrong. On 2009-10-22, at 6:46 AM, Lukas Renggli wrote: >> So this means that by default we have bad performance. no? > > No. > > In a fresh Pharo Web image less than 6% of the keys in Dictionaries > and less than 10% of the values in Sets have a weak-hashes. Moreover > the largest set with weak-hash values has 516 elements (on average > only 1.8 elements), the largest dictionary with weak-hash keys has > 1002 elements (on average only 4.3 elements). Using HashTable in such > a situation would introduce a major speed penalty and waste a lot of > memory. > > It would be cool if the Set and the Dictionary would choose their > implementation strategy automatically depending on the use-case. In a > standard Pharo image however that would just be the current > implementation. There are simply no instances in the image where it > would be worthwhile (large amount of data with bad hash) to use a > HashMap. > > 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 -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

Oct. 22, 2009

Re: [Pharo-project] the we site does not point to the rc1 image/

by Adrian Lienhard

On Oct 22, 2009, at 18:14 , StÃ©phane Ducasse wrote: > ok I was wrong. > May be should change beta to Release Candidate in the heading. done ADrian > > stef > > On Oct 22, 2009, at 1:58 PM, Adrian Lienhard wrote: > >> which link do you mean? >> >> Adrian >> >> On Oct 22, 2009, at 12:37 , StÃ©phane Ducasse wrote: >> >>> can somebody fix it? >>> >>> Stef >>> >>> _______________________________________________ >>> 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

Oct. 22, 2009

[Pharo-project] [update 1.1 ] #11011

by StÃ©phane Ducasse

11011 ----- - Issue 1357: use includesSelector: rather than selectors includes: Rationale for using #includesSelector: - a single message is better than two - an optimized method is better than a slow one The method is optimized because it directly ask methodDict includesKey: rather than creating an unecessary intermediate collection.

Oct. 22, 2009

Re: [Pharo-project] making #classVarNames answer a sorted Array

by StÃ©phane Ducasse

> >> This is related to http://code.google.com/p/pharo/issues/detail? >> id=1353 >> >> >> According to usage of classVarNames, a sorted Array would behave >> better >> >> - same class as instVarNames (I remember such discussion in Pharo) >> - optimized without extra code cost (especially if keys are also an >> Array) >> - sorted Array do compare fast with = (better than Sets) >> - no need to sort a sorted Array, so half senders will be simplified yes a lot of asSortedCollection everywhere. I'm in favor of integrating your changes.

Oct. 22, 2009