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

Re: [Pharo-project] Fwd: [squeakland] Four year old and her older sister win a Squeak-based programming contest in Singapore

by Serge Stinckwich

cool ! too bad i was in Singapore two weeks ago ... On Tue, Jul 21, 2009 at 7:48 PM, StÃ©phane Ducasse<stephane.ducasse(a)inria.fr> wrote: > This is why I was sad to curve out etoys. But this is life. > > Stef > > Begin forwarded message: > >>> I thought I should share this success story on this list. >>> >>> http://www.straitstimes.com/Breaking%2BNews/Singapore/Story/STIStory_405695… >>> >>> I am a concil member of the Singapore IT Standards Committee[1] and >>> an >>> organizer of the >>> code::XtremeApps[2] programming contest. Â We have had a Junior >>> Category since 2008 >>> and it is targeted at children 12 years and below. Â Last year we used >>> Alice and this year >>> we used Squeak. Â We had about 31 teams with about 80 children >>> participate in this contest. >>> >>> The link above is about a two-person team (a 4 year old and her 8 >>> year >>> old sister) who >>> wrote an application on healthy lifestyle focusing on anti-smoking >>> messages. >>> >>> Thanks. >>> >>> [1] http://www.itsc.org.sg >>> [2] http://www.itsc.org.sg/codeXtremeApps2009.html > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Smalltalkers do: [:it | All with: Class, (And love: it)] http://doesnotunderstand.org/

July 22, 2009

[Pharo-project] Copying image+changes between Windows and Linux

by Schwab,Wilhelm K

Hello all, Are any of you using both Linux and Windows? Is it just me, or does button swapping get weird when bouncing between the two? I'm not sure if the behavior is random, or if there is a pattern to it. So far, it just seems to work as I expect sometimes, and not others, and I _think_ changing OS is a trigger for it. Bill

July 22, 2009

Re: [Pharo-project] Show stopper network bug on Windows

by Schwab,Wilhelm K

Sig, Queue veryLoudHeadSlap.wav - however, that is not a fix for it on Linux. Also, on Windows, I am not getting the fully qualified name, which is another problem. It also helps make the case for formalized session management, as the image should know when it has had its first cup of coffee (the vm can inform it). Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Igor Stasenko Sent: Tuesday, July 21, 2009 6:53 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Show stopper network bug on Windows Guys, see my comment on that issue.: #localHostName should not be used before #initializeNetwork. Hope it helps. _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 22, 2009

Re: [Pharo-project] Persist a morph in a message.

by Cameron Sanders

You are better than I suspected, Watson! On Jul 21, 2009, at 8:16 PM, Igor Stasenko wrote: > 2009/7/22 Cameron Sanders <camsanders01(a)roadrunner.com>: >> Perhaps Stef is "moonlighting" under an alias... ? (He replied to >> himself for cover.) >> > Then you are 'moonlighting' under a 'Sherlock Holmes' alias :) > >> -cam >> >> On Jul 21, 2009, at 5:16 PM, Igor Stasenko wrote: >> >>> 2009/7/21 nullPointer <epicfan(a)gmail.com>: >>>> >>>>> Just a guess: maybe it is better to persist a morph(s) as is - as >>>>> original objects - just keep them somewhere in classvars. >>>>> Then to create a new view of it, just do a #deepCopy. >>>> >>>> Perhaps could be a combined solution. Persist the morph in a >>>> method, but >>>> only load one time, if class var is nothing. Then in the next times >>>> send >>>> #deepCopy to prototype morph . That could be a solution for the >>>> velocity :) >>>> I believe than EasyMorphicGUI works of that way too. >>>> >>>> Regards. >>> >>> Any reasons to stay anonymous? Hey, we don't/can't harm you in any >>> way :) >>> Instead, i think that it would be not only me, who could say, that >>> we >>> would really like to help you with that. >>> >> >> >> _______________________________________________ >> 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

July 22, 2009

Re: [Pharo-project] Who are you?

by Stuart Herring

I'm using Pharo with Seaside for a small commercial website for a friend's business (http://test.creativecorsetry.com.au) - not live yet, but only a month or so away. I originally started on Squeak 3.10, but Pharo looked like being the better choice for the future. Regards, Stuart On Tue, Jul 21, 2009 at 7:13 AM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > Dear all, > > 284 people are subscribed to this mailing list. It is a bit hard to > deduce how many users of Pharo there are, but the number of > subscriptions gives a number at least. > How many companies are using Pharo? Without thinking too much, I know > there are Netstyle.ch and Pinesoft. Are there more? > > I am preparing an academic presentation and having such figure will be > great. > > Kind regards, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 22, 2009

Re: [Pharo-project] Persist a morph in a message.

by Igor Stasenko

2009/7/22 Cameron Sanders <camsanders01(a)roadrunner.com>: > Perhaps Stef is "moonlighting" under an alias... ? (He replied to > himself for cover.) > Then you are 'moonlighting' under a 'Sherlock Holmes' alias :) > -cam > > On Jul 21, 2009, at 5:16 PM, Igor Stasenko wrote: > >> 2009/7/21 nullPointer <epicfan(a)gmail.com>: >>> >>>> Just a guess: maybe it is better to persist a morph(s) as is - as >>>> original objects - just keep them somewhere in classvars. >>>> Then to create a new view of it, just do a #deepCopy. >>> >>> Perhaps could be a combined solution. Persist the morph in a >>> method, but >>> only load one time, if class var is nothing. Then in the next times >>> send >>> #deepCopy to prototype morph . That could be a solution for the >>> velocity :) >>> I believe than EasyMorphicGUI works of that way too. >>> >>> Regards. >> >> Any reasons to stay anonymous? Hey, we don't/can't harm you in any >> way :) >> Instead, i think that it would be not only me, who could say, that we >> would really like to help you with that. >> > > > _______________________________________________ > 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.

July 22, 2009

Re: [Pharo-project] Persist a morph in a message.

by Cameron Sanders

Perhaps Stef is "moonlighting" under an alias... ? (He replied to himself for cover.) -cam On Jul 21, 2009, at 5:16 PM, Igor Stasenko wrote: > 2009/7/21 nullPointer <epicfan(a)gmail.com>: >> >>> Just a guess: maybe it is better to persist a morph(s) as is - as >>> original objects - just keep them somewhere in classvars. >>> Then to create a new view of it, just do a #deepCopy. >> >> Perhaps could be a combined solution. Persist the morph in a >> method, but >> only load one time, if class var is nothing. Then in the next times >> send >> #deepCopy to prototype morph . That could be a solution for the >> velocity :) >> I believe than EasyMorphicGUI works of that way too. >> >> Regards. > > Any reasons to stay anonymous? Hey, we don't/can't harm you in any > way :) > Instead, i think that it would be not only me, who could say, that we > would really like to help you with that. >

July 21, 2009

Re: [Pharo-project] Show stopper network bug on Windows

by Igor Stasenko

Guys, see my comment on that issue.: #localHostName should not be used before #initializeNetwork. Hope it helps.

July 21, 2009

Re: [Pharo-project] Show stopper network bug on Windows

by Schwab,Wilhelm K

This is not quite working, but I suspect this is a defect in primHostNameSize, and will fall by loading VM maker and looking at the socket plugin. I do not know enough to say whether the primitive needs to be fixed, or simply avoided consistent with #useOldNetwork. -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Schwab,Wilhelm K Sent: Tuesday, July 21, 2009 2:44 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Show stopper network bug on Windows I think I have it willing to keep running now. I looked for the #inform: in the process browser, and missed it the first time - I needed to ask for the full stack, and there it was, a good long way down the list :) It is now sending text to the transcript, so cross your fingers. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Schwab,Wilhelm K Sent: Tuesday, July 21, 2009 2:22 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Show stopper network bug on Windows It's trying to run on a win2k3 box. I say trying because it insists on telling me (modally) how many updates it processed - every time. Is there a way to gag that? Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse Sent: Tuesday, July 21, 2009 1:36 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Show stopper network bug on Windows Yes we do not have a windows at hand. can you let us know from which update the problem is related. > In this case the first step woud be to identify which update > introduced the problem. > > Suppose that a core #10200 image still works, you could do: > > 10200 to: 10384 do: [ :i | > Utilities updateFromServerThroughUpdateNumber: i. > NetNameResolver localHostAddress ] > > And then see after which update number the first exception is thrown. > I did not test this, but it should work. > > Adrian _______________________________________________ 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

July 21, 2009

Re: [Pharo-project] Show stopper network bug on Windows

by Schwab,Wilhelm K

I am hopefully getting that answer for us. Actually, it just blew up in 10264, but over #next returning nil in Monticello, or so it seems. More fundamentally than that, are you saying that the code works on a mac, or is it that you have an IPv6-aware network? Again, I have seen this on both Windows and Linux, and strongly suspect that the problem is that #primHostNameSize blows up on IPv4 or otherwise in connection with trying to accommodate both IP standards. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse Sent: Tuesday, July 21, 2009 1:36 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Show stopper network bug on Windows Yes we do not have a windows at hand. can you let us know from which update the problem is related. > In this case the first step woud be to identify which update > introduced the problem. > > Suppose that a core #10200 image still works, you could do: > > 10200 to: 10384 do: [ :i | > Utilities updateFromServerThroughUpdateNumber: i. > NetNameResolver localHostAddress ] > > And then see after which update number the first exception is thrown. > I did not test this, but it should work. > > Adrian _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 21, 2009