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

[Pharo-project] Juan Cook has invited you to Dropbox

by Dropbox

We're excited to let you know that Juan Cook has invited you to Dropbox! Juan Cook has been using Dropbox to sync and share files online and across computers, and thought you might want it too. Visit http://www.getdropbox.com/link/20.cqyZ1lxSZM/NjQ3MjkzODM3 to get started. - The Dropbox Team ____________________________________________________ To stop receiving invites from Dropbox, please go to http://www.getdropbox.com/bl/568088f42f89/pharo-project%40lists.gforge.inri…

Nov. 5, 2009

[Pharo-project] New Pharo based on core 10493

by Damien Cassou

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

Nov. 5, 2009

Re: [Pharo-project] Making packages shipped with Pharo ready for 1.0

by Damien Cassou

On Mon, Nov 2, 2009 at 9:27 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > I checked the problem below again in the new Pharo 09.11.1 image but > it still contains the old method OBMethodNode>>dropOnClass:, which > references InputSensor. Maybe you need to sync with Lukas to get the > latest version of OB? fixed, sorry. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Nov. 5, 2009

Re: [Pharo-project] anyone think buttons still too large?

by StÃ©phane Ducasse

yes the problem is that glamour is not ready to write browsers because its update mechanism is not there. Stef On Nov 4, 2009, at 10:59 PM, Stephan Eggermont wrote: >> From: empty <emptist(a)googlegroups.com> >> I tried to install version 1 rc to find the buttons still too large. >> >> If you look at the whole class browser the first things you see are >> those >> big blue buttons. I'd prefer they not so big and colorful. >> >> Anyone have the same feel? > > Yes, I even played around with a painting tool and started digging > around > in Toolbuilder, OmniBrowser and PolyMorph. Let me just say that I > really, > really, really like Glamour. > > See issue 909 > > Stephan Eggermont > > <ButtonBar2.png> > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Nov. 5, 2009

Re: [Pharo-project] stupid but very intrigued question

by Mariano Martinez Peck

On Thu, Nov 5, 2009 at 9:32 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > I have > rc1 size => 11.3 mb > 1.1a (11031)=>11.5 mb > > so don't you have the same? > > Maybe Esteban was confused (as I was too) because in the inria website the image is zipped. It says: PharoCore-1.1-11011-alpha.zip<http://gforge.inria.fr/frs/download.php/24603/PharoCore-1.1-11011-alpha.zip>5.09 MB But...if you uncompress the zip you have an aprox. 11mb image Cheers Mariano > Stef > > On Nov 5, 2009, at 12:38 AM, Esteban Lorenzano wrote: > > > Hi, > > I was downloading a new pharo-core image (to load some iphone > > development tools into it), and I see the pharo-core alpha for 1.1... > > and the image size diference is SO BIG, that I wonder why... > > What is droped to get an image so small? > > > > Cheers, > > Esteban > > > > > > > > _______________________________________________ > > 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 >

Nov. 5, 2009

Re: [Pharo-project] Underscore assignments

by StÃ©phane Ducasse

ok when you are reayd update the bugtracker so that I can follow from chili. Stef On Nov 5, 2009, at 12:15 PM, Lukas Renggli wrote: > Please wait, I can prepare a complete patch for Pharo 1.1. > > I suggest that we just set the following preference in Pharo 1.0: > > Preferences disable: #allowUnderscoreAssignment > > Lukas > > > > 2009/11/5 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> so does it make sense that I integrate your changes? >> >> Stef >> >> On Nov 4, 2009, at 10:35 PM, Lukas Renggli wrote: >> >>>>> Preferences disable: #allowUnderscoreAssignment >>>> >>>> I did that, but I can still compile assignments with underscores. >>>> >>>> Do I miss anything? >>> >>> No, it is me that is totally confused tonight. >>> >>> You also need to evaluate the following expression: >>> >>> (Scanner classPool at: #TypeTable) at: $_ asciiValue put: #xLetter >>> >>> Afterwards you can create classes, inst-vars, methods, etc. that >>> have >>> an underscore inside. >>> >>> 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 >> > > > > -- > 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

Nov. 5, 2009

Re: [Pharo-project] SystemVersion

by StÃ©phane Ducasse

good idea. Now this class should not be alone in one package. Stef On Nov 4, 2009, at 9:17 PM, Michael Roberts wrote: > Hi, now that we have multiple branches & image types I want to improve > the publishing of test results. I'm lacking a neat way to get the > image type and branch number. I don't really want to parse the image > file name. > > Seems the best thing to use is: SystemVersion current version. Is > there anything else? > > results: > Pharo Core 1.0 --> 'Pharo1.0rc1' > Pharo Core 1.1 --> 'Pharo1.1a > Pharo 1.0 --> 'Pharo1.0rc1' > > We could add some state to SystemVersion, e.g #imageType, #branch, or > we agree on a convention for #version that can easily be parsed. > > What do you think? > > thanks, > Mike > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Nov. 5, 2009

Re: [Pharo-project] stupid but very intrigued question

by StÃ©phane Ducasse

I have rc1 size => 11.3 mb 1.1a (11031)=>11.5 mb so don't you have the same? Stef On Nov 5, 2009, at 12:38 AM, Esteban Lorenzano wrote: > Hi, > I was downloading a new pharo-core image (to load some iphone > development tools into it), and I see the pharo-core alpha for 1.1... > and the image size diference is SO BIG, that I wonder why... > What is droped to get an image so small? > > Cheers, > Esteban > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Nov. 5, 2009

Re: [Pharo-project] Underscore assignments

by Lukas Renggli

Please wait, I can prepare a complete patch for Pharo 1.1. I suggest that we just set the following preference in Pharo 1.0: Preferences disable: #allowUnderscoreAssignment Lukas 2009/11/5 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > so does it make sense that I integrate your changes? > > Stef > > On Nov 4, 2009, at 10:35 PM, Lukas Renggli wrote: > >>>> Â Â Preferences disable: #allowUnderscoreAssignment >>> >>> I did that, but I can still compile assignments with underscores. >>> >>> Do I miss anything? >> >> No, it is me that is totally confused tonight. >> >> You also need to evaluate the following expression: >> >> Â (Scanner classPool at: #TypeTable) at: $_ asciiValue put: #xLetter >> >> Afterwards you can create classes, inst-vars, methods, etc. that have >> an underscore inside. >> >> 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 > -- Lukas Renggli http://www.lukas-renggli.ch

Nov. 5, 2009

Re: [Pharo-project] Shadowed Variables

by Lukas Renggli

Lint already detects most kind of shadowing. Lukas 2009/11/5 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > this is good that you can do that. > Now this is a not so good habit for readibility. > > Stef > > > >> 2009/11/4 Lukas Renggli <renggli(a)gmail.com>: >>> It shows up in the transcript for all users of the trait when the >>> method is accepted. This is nasty, because that introduces ugly >>> dependencies. >>> >>> Of course we might want to relax the semantics of Smalltalk and allow >>> shadowing of variables, so that class variables could shadow globals; >>> instance variables could shadow super instance variables, class >>> variables, and globals; temp variables could shadow outer temp >>> variables, instance variables, class variables, and globals, etc. >>> >>> I thought Python allowed this kind of shadowing? Don't remember if >>> this was cool or not, but it sounds quite bit messy. >>> >> not only Python. >> Most languages i used to know, allowing a local-scope names to shadow >> an outer scope names without any warnings and bashing the user. >> Some IDEs could warn about such things, but not compiler. >> >>> Lukas >>> >>> >>> 2009/11/4 Â <csrabak(a)bol.com.br>: >>>> Em 04/11/2009 17:53, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com >>>> > escreveu: >>>> >>>> Right. Â However, shouldn't the message about shadowing be issued >>>> when >>>> we accept the method in the browser? >>>> >>>> >>>>> Â ??? Â Â Â Â Â Â Just Â Â Â Â Â looking Â Â Â Â Â the >>>>> first >>>>> ArrayTest>>#testCopyReplaceAllWith1Occurence, Â it has Â a Â temp >>>>> named >>>>> result and an inst var named result >>>>> >>>>> Â 2009/11/4 Lukas Renggli : >>>>>> First I thought this is Â because temps in trait methods shadow the >>>>>> inst-vars of Â the classes Â that use these Â traits (ouch!), Â but it >>>>>> doesn't seem to be the case. Â I don't understand either why we get >>>>>> these messages. >>>>>> Lukas >>>>>> 2009/11/4 StÃ©phane Ducasse : >>>>>>> Strange this is related to traits? >>>>>>> Stef >>>>>>> On Nov 4, 2009, at 5:17 PM, Lukas Renggli wrote: >>>>>>> >>>>>>>> When I recompile a Pharo image >>>>>>>> Compiler recompileAll >>>>>>>> I get 819 messages Â complaining about shadowed variables, mostly >>>>>>>> but not only in the new collection tests. Does anybody knows why >>>>>>>> this happens? >>>>>>>> Lukas >>>> [819 messages snipped] >>>> >>>> _______________________________________________ >>>> 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 >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> >> _______________________________________________ >> 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 > -- Lukas Renggli http://www.lukas-renggli.ch

Nov. 5, 2009