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

[Pharo-project] Fwd: Pharo on reddit

by StÃ©phane Ducasse

Begin forwarded message: > From: Marcus Denker <denker(a)iam.unibe.ch> > Date: February 22, 2009 1:00:47 AM CEST > To: StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr>, Adrian Lienhard <adi(a)netstyle.ch > >, Michael Rueger <m.rueger(a)acm.org> > Subject: Pharo on reddit > > Hi, > > http://www.reddit.com/r/programming/comments/7z55v/pharo_opensource_smallta… > > got us ca. 2430 visitors on 21st (up from 60-90 per day that we get > normally) > > Marcus > > -- > Marcus Denker -- denker(a)acm.org > http://www.marcusdenker.de >

Feb. 22, 2009

Re: [Pharo-project] Getting started

by Rob Rothwell

Is this reproducible then? (It is by me!) Should I report it as an issue? Rob On Sat, Feb 21, 2009 at 9:03 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>wrote: > I'm glad this came up, because I hit that one too and forgot about it. The > other thing I have found is that more recent images are somewhat particular > about the VM version - they will freeze if the (Windows is where I have seen > it) vm is too old. > > Bill > > ---- > Wilhelm K. Schwab, Ph.D. > bschwab AT anest DOT ufl DOT edu > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [ > pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Rob Rothwell [ > r.j.rothwell(a)gmail.com] > Sent: Saturday, February 21, 2009 2:15 PM > To: Pharo-project(a)lists.gforge.inria.fr; dfinlayson(a)usgs.gov > Subject: Re: [Pharo-project] Getting started > > I get that error with the new 10236 dev image as well; I don't recall > getting it with the 10231 dev image. I think it is related to the initial > FreeType startup process. > > Start with a 10236 image, click "abandon" and close the debug window, save > the image, close it, and open it again. At least I don't get the error the > next time. > > Rob > > On Sat, Feb 21, 2009 at 12:21 PM, David Finlayson <dfinlayson(a)usgs.gov > <mailto:dfinlayson@usgs.gov>> wrote: > What's the trick to getting a pharo image up and running? > > I tried downloading the pharo-dev image 20231 from the downloads page, > then I added SqueakV39.sources from a Squeak image. When I launched I > got an error dialog saying: > > Error: a primative has failed. > > I was hoping to take a look around at the work you folks are doing. > > -- > David Finlayson > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr<mailto: > Pharo-project(a)lists.gforge.inria.fr> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >

Feb. 22, 2009

Re: [Pharo-project] Getting started

by Schwab,Wilhelm K

I'm glad this came up, because I hit that one too and forgot about it. The other thing I have found is that more recent images are somewhat particular about the VM version - they will freeze if the (Windows is where I have seen it) vm is too old. Bill ---- Wilhelm K. Schwab, Ph.D. bschwab AT anest DOT ufl DOT edu ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Rob Rothwell [r.j.rothwell(a)gmail.com] Sent: Saturday, February 21, 2009 2:15 PM To: Pharo-project(a)lists.gforge.inria.fr; dfinlayson(a)usgs.gov Subject: Re: [Pharo-project] Getting started I get that error with the new 10236 dev image as well; I don't recall getting it with the 10231 dev image. I think it is related to the initial FreeType startup process. Start with a 10236 image, click "abandon" and close the debug window, save the image, close it, and open it again. At least I don't get the error the next time. Rob On Sat, Feb 21, 2009 at 12:21 PM, David Finlayson <dfinlayson(a)usgs.gov<mailto:dfinlayson@usgs.gov>> wrote: What's the trick to getting a pharo image up and running? I tried downloading the pharo-dev image 20231 from the downloads page, then I added SqueakV39.sources from a Squeak image. When I launched I got an error dialog saying: Error: a primative has failed. I was hoping to take a look around at the work you folks are doing. -- David Finlayson _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 22, 2009

Re: [Pharo-project] Tagging methods for expected lint failures

by Lukas Renggli

Normally yes, it should work. However some lint rules don't work on a single method but on a class or multiple classes. In these cases the pragmas don't really work and scale well. I could think of a solution here, but this is not implemented yet. In any case, if there is something wrong with the marking please report to me. Even if this is in the base code for more than a year, it is quite rarely used. As I said I prefer to fix the issues. Also I started to exclude certain rules by default. For example, it always complained about ever single test method that it is never sent. So this test is not run on subclasses of TestCase anymore. Lukas On Sat, Feb 21, 2009 at 10:00 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I hope so because I started to do use. > > > On Feb 21, 2009, at 5:56 PM, Adrian Lienhard wrote: > >> I've looked at some of the "Message sent but not implemented:" issues >> that Damien created. In tests where classes and methods are created at >> runtime, Lint incorrectly complains. >> >> Do we use pragmas to mark the expected failures (see http://www.lukas-renggli.ch/blog/ignoring-lint-rules)? >> Is this lint pragma honored by the version of Lint that we use? >> >> Adrian >> ___________________ >> http://www.adrian-lienhard.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

Feb. 21, 2009

Re: [Pharo-project] [update] #10241

by Rob Rothwell

I was trying to help confirm that this might fix the condenseChanges problems. When I take a 10236 dev image and update it to 10241 and try to do a Smalltalk condenseChanges, I get the attached Syntax Error during the condensing... Can anyone reproduce this? Rob On Sat, Feb 21, 2009 at 3:59 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Thanks adrian. > I got no time to test but this is cool to have that. > > Stef > > On Feb 21, 2009, at 3:10 PM, Adrian Lienhard wrote: > > > #10241 > > > > Issue 167: > > - Traits implementation refactoring (no sharing of compiled methods > > and source) > > - New tests for Traits MOP > > > > > > Since this changes the handling of sources, the following issues with > > condensing changes may be resolved: > > http://code.google.com/p/pharo/issues/detail?id=466 > > http://code.google.com/p/pharo/issues/detail?id=470 > > > > Can somebody check these issues? > > > > Adrian > > ___________________ > > http://www.adrian-lienhard.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 >

Feb. 21, 2009

Re: [Pharo-project] Tagging methods for expected lint failures

by StÃ©phane Ducasse

I hope so because I started to do use. On Feb 21, 2009, at 5:56 PM, Adrian Lienhard wrote: > I've looked at some of the "Message sent but not implemented:" issues > that Damien created. In tests where classes and methods are created at > runtime, Lint incorrectly complains. > > Do we use pragmas to mark the expected failures (see http://www.lukas-renggli.ch/blog/ignoring-lint-rules)? > Is this lint pragma honored by the version of Lint that we use? > > Adrian > ___________________ > http://www.adrian-lienhard.ch/ > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 21, 2009

Re: [Pharo-project] [update] #10241

by StÃ©phane Ducasse

Thanks adrian. I got no time to test but this is cool to have that. Stef On Feb 21, 2009, at 3:10 PM, Adrian Lienhard wrote: > #10241 > > Issue 167: > - Traits implementation refactoring (no sharing of compiled methods > and source) > - New tests for Traits MOP > > > Since this changes the handling of sources, the following issues with > condensing changes may be resolved: > http://code.google.com/p/pharo/issues/detail?id=466 > http://code.google.com/p/pharo/issues/detail?id=470 > > Can somebody check these issues? > > Adrian > ___________________ > http://www.adrian-lienhard.ch/ > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 21, 2009

[Pharo-project] Fwd: [vwnc] RBMethodSniffer (another RB plugin)

by StÃ©phane Ducasse

could be fun :) Stef Begin forwarded message: > From: Emiliano PÃ©rez <emilianogperez(a)gmail.com> > Date: February 20, 2009 11:22:08 PM CEST > To: vwnc-list <vwnc(a)cs.uiuc.edu> > Subject: [vwnc] RBMethodSniffer (another RB plugin) > > Hi list, > I've published another addon in the public repository. This time > it's a > method 'sneak peaker' (check the images below to see what i mean...). > Significantly simpler than the Blue Magic but still very usefull. And > they go great together by the way ; ) . > > Here's how it works: When the mouse pointer is over a selector with a > static receiver (self, super or class reference) or a selector with > only > one implementor, holding the alt key will show a little floatting > window > with the method definition. > It works within the RefactoringBrowser, the Debugger and the > Inspector. > > Name of the package: RBMethodSniffer > VW image: 7.6 > Prerequisites: RBQuickNavToolset (7.6_1.1), RBCodeHighlighting. > > Again, any comment/suggestion/bug-report will be more than welcome. > Hope > you enjoy it. > > Cheers, Emiliano. > > PD: If you have RBQuickNavToolset loaded in your image (RBBlueMagic > prereq) please first update it to 7.6_1.1 (unloading it has the same > effect). > I've added the version numer to the prerequisites in the Method > Sniffer > package but still couldn't make it load automatically... > > > > > > > _______________________________________________ > vwnc mailing list > vwnc(a)cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc >

Feb. 21, 2009

Re: [Pharo-project] Getting started

by Rob Rothwell

I get that error with the new 10236 dev image as well; I don't recall getting it with the 10231 dev image. I think it is related to the initial FreeType startup process. Start with a 10236 image, click "abandon" and close the debug window, save the image, close it, and open it again. At least I don't get the error the next time. Rob On Sat, Feb 21, 2009 at 12:21 PM, David Finlayson <dfinlayson(a)usgs.gov>wrote: > What's the trick to getting a pharo image up and running? > > I tried downloading the pharo-dev image 20231 from the downloads page, > then I added SqueakV39.sources from a Squeak image. When I launched I > got an error dialog saying: > > Error: a primative has failed. > > I was hoping to take a look around at the work you folks are doing. > > -- > David Finlayson > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 21, 2009

Re: [Pharo-project] Getting started

by David Mitchell

Haven't had that problem. I'm using SqueakV39.sources with Pharo. My approach: Start at the Pharo downloads page: https://gforge.inria.fr/frs/?group_id=1299 Pick a a one-click distribution such as: https://gforge.inria.fr/frs/download.php/10409/Pharo0.1-10107-oneclick.zip Unzip. Then grab the latest Pharo-dev zip which gives you a current image and changes with the developer tools. You can get the link from here: http://code.google.com/p/pharo/wiki/Downloads?tm=2 Unzip that image and changes and copy the files to the Contents/Resources folder in the one-click structure. One-clicks preconfigure the executable to look for a specific image and changes file name. So, I rename the old image & changes to something else and then rename the latest image & changes to match the original. Alternatively, you can fix up the platform-specific text files, but I never learned how to do that for Mac, so I just rename. On Sat, Feb 21, 2009 at 11:21 AM, David Finlayson <dfinlayson(a)usgs.gov> wrote: > What's the trick to getting a pharo image up and running? > > I tried downloading the pharo-dev image 20231 from the downloads page, > then I added SqueakV39.sources from a Squeak image. When I launched I > got an error dialog saying: > > Error: a primative has failed. > > I was hoping to take a look around at the work you folks are doing. > > -- > David Finlayson > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 21, 2009