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

Re: [Pharo-project] Getting started

by StÃ©phane Ducasse

Hi david this is strange because on mac I used the squeak 3.9 default setup and I just double click on the core image and this is working. My suggestions are - either use a pharo-dev without updating - or a core and update Can you let us know if this is working for you? Stef On Feb 22, 2009, at 9:59 AM, David Finlayson wrote: > I tried all the suggestions here (abandon the error and continue; > download a one-click source and over write the files with the dev > updates. In both cases, I wound up with an unstable image. I got > further with the second method and used it for a couple of hours, but > I am seeing a lot of errors. For example: errors are raised when I > delete morphs (something to do with the trash can); an error searching > in OB for the word "morph" raised an error in OBEnhancementMetaNode >> > Fan ?? > > I know that you guys are ripping out a lot of cruft in Squeak and > things are understandably unstable right now. You've made great > progress on the UI, that's for sure. I'll come back again when you > release the first stable build in a couple of months. > > Thanks for your work, > > David > > On Sat, Feb 21, 2009 at 7:44 PM, Rob Rothwell > <r.j.rothwell(a)gmail.com> wrote: >> 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@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 >> > > > > -- > David Finlayson, Ph.D. > Operational Geologist > > U.S. Geological Survey > Pacific Science Center > 400 Natural Bridges Drive > Santa Cruz, CA 95060, USA > > Office: 831-427-4757 > Lab: 831-427-4462 > Fax: 831-427-4748 > E-mail: dfinlayson(a)usgs.gov > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)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 StÃ©phane Ducasse

On Feb 22, 2009, at 12:52 AM, Lukas Renggli wrote: > 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. :) me too but the problem is that some rules are too broad. So we will learn and improve. Stef > > > 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 > > _______________________________________________ > Pharo-project mailing list > 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 StÃ©phane Ducasse

what is important is to see if the update is working on the core. We do not check if the update works when the tools and all the packages are loaded. Stef On Feb 22, 2009, at 4:44 AM, Rob Rothwell wrote: > 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@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. 22, 2009

Re: [Pharo-project] Getting started

by Marcus Denker

On 22.02.2009, at 09:59, David Finlayson wrote: > I tried all the suggestions here (abandon the error and continue; > download a one-click source and over write the files with the dev > updates. In both cases, I wound up with an unstable image. I got > further with the second method and used it for a couple of hours, but > I am seeing a lot of errors. For example: errors are raised when I > delete morphs (something to do with the trash can); an error searching > in OB for the word "morph" raised an error in OBEnhancementMetaNode >> > Fan ?? I have added reports for those at http://code.google.com/p/pharo/issues/list Thanks! Marcus -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

Feb. 22, 2009

Re: [Pharo-project] What about #ifNotNil and #ifNotNilDo:

by Lukas Renggli

Yeah, simply don't use #ifNotNilDo: and friends. If you follow the coding conventions of Seaside your code will basically run anywhere <http://www.seaside.st/community/conventions>. Slime also contains rules to automatically refactor non-portable code, for example: ansiCompatibilityConditionals ^ self rewrite: #( " kill abnormalities " ('``@boolean ifNotNilDo: ``@block' '``@boolean ifNotNil: ``@block') ('``@boolean ifNotNilDo: ``@block1 ifNil: ``@block2' '``@boolean ifNotNil: ``@block1 ifNil: ``@block2') ('``@boolean ifNil: ``@block1 ifNotNilDo: ``@block2' '``@boolean ifNil: ``@block1 ifNotNil: ``@block2') " normalize arguments " ('``@boolean ifNotNil: [ | `@temps | ``@body ]' '``@boolean ifNotNil: [ :arg | | `@temps | ``@body ]') ('``@boolean ifNotNil: [ | `@temps | ``@body ] ifNil: ``@block ' '``@boolean ifNotNil: [ :arg | | `@temps | ``@body ] ifNil: ``@block') ('``@boolean ifNil: ``@block ifNotNil: [ | `@temps | ``@body ]' '``@boolean ifNil: ``@block ifNotNil: [ :arg | | `@temps | ``@body ]')) methods: false name: 'ANSI Compatibility: Conditionals' Cheers, Lukas On Sun, Feb 22, 2009 at 10:22 AM, Marcus Denker <denker(a)iam.unibe.ch> wrote: > > On 21.02.2009, at 18:31, Damien Cassou wrote: > >> Hi, >> >> is there a way to get the #ifNotNilDo: behavior to write compatible >> Squeak and Pharo code? >> > > -> do not use ifNotNilDo: > -> use ifNotNil: without the argument. > > The real fix of course would be for Squeak adopting the optinal args > changeset > (this is from 2007...) > > Marcus > > -- > Marcus Denker -- denker(a)acm.org > http://www.marcusdenker.de > > > _______________________________________________ > 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. 22, 2009

Re: [Pharo-project] Getting started

by Marcus Denker

On 22.02.2009, at 09:59, David Finlayson wrote: > I tried all the suggestions here (abandon the error and continue; > download a one-click source and over write the files with the dev > updates. In both cases, I wound up with an unstable image. I got > further with the second method and used it for a couple of hours, but > I am seeing a lot of errors. For example: errors are raised when I > delete morphs (something to do with the trash can); an error searching > in OB for the word "morph" raised an error in OBEnhancementMetaNode >> > Fan ?? Ups. Normally the images are very usable... we need to look at how these problems where introduced in the last ones. > > > I know that you guys are ripping out a lot of cruft in Squeak and > things are understandably unstable right now. You've made great > progress on the UI, that's for sure. I'll come back again when you > release the first stable build in a couple of months. > I hope it's weeks, not months... Marcus > Thanks for your work, > > David > > On Sat, Feb 21, 2009 at 7:44 PM, Rob Rothwell > <r.j.rothwell(a)gmail.com> wrote: >> 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@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 >> > > > > -- > David Finlayson, Ph.D. > Operational Geologist > > U.S. Geological Survey > Pacific Science Center > 400 Natural Bridges Drive > Santa Cruz, CA 95060, USA > > Office: 831-427-4757 > Lab: 831-427-4462 > Fax: 831-427-4748 > E-mail: dfinlayson(a)usgs.gov > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

Feb. 22, 2009

Re: [Pharo-project] Getting started

by Marcus Denker

Uhh... we should really provide up-to-date one-click images all the time. I will have a look at that soon. Marcus On 21.02.2009, at 18:57, David Mitchell wrote: > 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 >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

Feb. 22, 2009

Re: [Pharo-project] What about #ifNotNil and #ifNotNilDo:

by Marcus Denker

On 21.02.2009, at 18:31, Damien Cassou wrote: > Hi, > > is there a way to get the #ifNotNilDo: behavior to write compatible > Squeak and Pharo code? > -> do not use ifNotNilDo: -> use ifNotNil: without the argument. The real fix of course would be for Squeak adopting the optinal args changeset (this is from 2007...) Marcus -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

Feb. 22, 2009

Re: [Pharo-project] Getting started

by David Finlayson

I tried all the suggestions here (abandon the error and continue; download a one-click source and over write the files with the dev updates. In both cases, I wound up with an unstable image. I got further with the second method and used it for a couple of hours, but I am seeing a lot of errors. For example: errors are raised when I delete morphs (something to do with the trash can); an error searching in OB for the word "morph" raised an error in OBEnhancementMetaNode >> Fan ?? I know that you guys are ripping out a lot of cruft in Squeak and things are understandably unstable right now. You've made great progress on the UI, that's for sure. I'll come back again when you release the first stable build in a couple of months. Thanks for your work, David On Sat, Feb 21, 2009 at 7:44 PM, Rob Rothwell <r.j.rothwell(a)gmail.com> wrote: > 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@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 > -- David Finlayson, Ph.D. Operational Geologist U.S. Geological Survey Pacific Science Center 400 Natural Bridges Drive Santa Cruz, CA 95060, USA Office: 831-427-4757 Lab: 831-427-4462 Fax: 831-427-4748 E-mail: dfinlayson(a)usgs.gov

Feb. 22, 2009

[Pharo-project] Fwd: Pharo on reddit

by StÃ©phane Ducasse

Begin forwarded message: > From: Michael Rueger <m.rueger(a)acm.org> > Date: February 22, 2009 1:04:00 AM CEST > To: Marcus Denker <denker(a)iam.unibe.ch> > Cc: StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr>, Adrian Lienhard <adi(a)netstyle.ch > > > Subject: Re: Pharo on reddit > > Marcus Denker wrote: >> 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) > > :-) > > But... > >> Please help a clueless Smalltalk noob. How the hell do I run this >> thing? Is it Mac only? > >> Download Squeak, then add Pharo image to Squeak folder, run >> squeak.exe, select Pharo image, boom. > > We probably still need to make the process easier. > I could look at building installers and deb/rpm packages based on > the squeakland and Sophie work. > > Michael >

Feb. 22, 2009