January 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] where can I find the athens player?

by StÃ©phane Ducasse

thanks I will publish now. but you will have to look at what I did because I was trying to make it work a bit stupidly ;) With my solution the text gets suddenly black :) On Jan 27, 2013, at 6:36 AM, Esteban Lorenzano wrote: > I added you as a contributor... feel free to commit your changes :) > > On Jan 26, 2013, at 7:46 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> I just loaded playground. >> Now I have a question :) >> >> AthensPlayground example2 >> raises an error >> >> >> methNode sourceText: requestor text string >> >> requestor is a Playground model and it does not understand text. >> >> >> So I fix it somehow and I cleaned a bit the code but I cannot publish (may be this is a problem with my password but I do not see why) >> Can I get a contributor? >> >> >> Stef >> >>> ahhh, btw, you don't need the chipmunk library to use the AthensPlayground, just the cairo lib :) >>> >>> On Jan 26, 2013, at 5:26 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>>> Hi, >>>> >>>> The AthensPlayground is part of the Storm project, you can find here: http://smalltalkhub.com/#!/~estebanlm/Storm >>>> >>>> I *think* the metacello config is in sync with sources so you just need to follow instruction. If you have any problem please let me know :) >>>> >>>> Esteban >>>> >>>> On Jan 26, 2013, at 1:01 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>> >>>>> Hi esteban >>>>> >>>>> where is your code to try athens? >>>>> It would be good to move all the code to >>>>> Pharo/Athens >>>>> >>>>> >>>>> Stef >>>>> >>>> >>> >> >> > >

Jan. 27, 2013

Re: [Pharo-project] where can I find the athens player?

by Esteban Lorenzano

I added you as a contributor... feel free to commit your changes :) On Jan 26, 2013, at 7:46 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I just loaded playground. > Now I have a question :) > > AthensPlayground example2 > raises an error > > > methNode sourceText: requestor text string > > requestor is a Playground model and it does not understand text. > > > So I fix it somehow and I cleaned a bit the code but I cannot publish (may be this is a problem with my password but I do not see why) > Can I get a contributor? > > > Stef > >> ahhh, btw, you don't need the chipmunk library to use the AthensPlayground, just the cairo lib :) >> >> On Jan 26, 2013, at 5:26 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >>> Hi, >>> >>> The AthensPlayground is part of the Storm project, you can find here: http://smalltalkhub.com/#!/~estebanlm/Storm >>> >>> I *think* the metacello config is in sync with sources so you just need to follow instruction. If you have any problem please let me know :) >>> >>> Esteban >>> >>> On Jan 26, 2013, at 1:01 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> >>>> Hi esteban >>>> >>>> where is your code to try athens? >>>> It would be good to move all the code to >>>> Pharo/Athens >>>> >>>> >>>> Stef >>>> >>> >> > >

Jan. 27, 2013

Re: [Pharo-project] Pharo 2.0beta One-click download link gives 404 error

by Camillo Bruni

yes, we're aware of that: https://code.google.com/p/pharo/issues/detail?id=7315 On 2013-01-26, at 12:15, "H. Hirzel" <hannes.hirzel(a)gmail.com> wrote: > Hello > > The download link from > http://www.pharo-project.org/pharo-download/beta-2-0 > > gives a 404 error. > > However the image download from the same page > http://pharo.gforge.inria.fr/ci/image/20/latest.zip > > works fine. > > Regards > > Hannes >

Jan. 26, 2013

[Pharo-project] NativeBoost loader isReceiver and friends

by Ciprian Teodorov

Hi Igor, While looking through NB code I have found some things you might be interested in. The subjects are the #pushAsValue #pushAsPointer: methods in: NBExternalAddressType, NBExternalObjectType, NBExternalStructureType, NBExternalEnumerationType, NBFFICallbackType. Why some of them check if loader isReceiver, and some others don't? some also check even (loader isReceiver and: [ gen requestor includesBehavior: objectClass ]) is this intentional or just copy/paste incompletness? In my opinion all these methods have to check both conditions... Moreover, I think it might be a good idea for them to accept nil and passNULL (0) I think this makes sense since checking for nil should be cheaper than a memory allocation when calling function with output arguments that we do not want... well in the cases they don't crash... but anyways if they crash with NULL... that is not our problem, right? Secondly I have found that NBExternalType>>verifyClassOf: oop is: aClass generator: gen is sort of a reimplementation of NBInterpreterProxy>>verifyClassOf: oop is: aClass again is this intentional? -- Dr. Ciprian TEODOROV IngÃ©nieur DÃ©veloppement CAO tÃ©l : 06 08 54 73 48 mail : ciprian.teodorov(a)gmail.com www.teodorov.ro

Jan. 26, 2013

Re: [Pharo-project] [update 2.0] #20491

by StÃ©phane Ducasse

no problem. I prefer that you say something because I'm sure that you see it than nothing. Stef On Jan 26, 2013, at 3:53 PM, Torsten Bergmann wrote: > Mmmmhhh .... the image had no modified packages and I got it on monday > from CI. I used a fresh one from today too - it works now. > Sorry for the noise ... > > Thanks > T.

Jan. 26, 2013

[Pharo-project] [update 2.0] #20491

by Torsten Bergmann

Jan. 26, 2013

Re: [Pharo-project] where can I find the athens player?

by StÃ©phane Ducasse

I just loaded playground. Now I have a question :) AthensPlayground example2 raises an error methNode sourceText: requestor text string requestor is a Playground model and it does not understand text. So I fix it somehow and I cleaned a bit the code but I cannot publish (may be this is a problem with my password but I do not see why) Can I get a contributor? Stef > ahhh, btw, you don't need the chipmunk library to use the AthensPlayground, just the cairo lib :) > > On Jan 26, 2013, at 5:26 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> Hi, >> >> The AthensPlayground is part of the Storm project, you can find here: http://smalltalkhub.com/#!/~estebanlm/Storm >> >> I *think* the metacello config is in sync with sources so you just need to follow instruction. If you have any problem please let me know :) >> >> Esteban >> >> On Jan 26, 2013, at 1:01 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >>> Hi esteban >>> >>> where is your code to try athens? >>> It would be good to move all the code to >>> Pharo/Athens >>> >>> >>> Stef >>> >> >

Jan. 26, 2013

Re: [Pharo-project] where can I find the athens player?

by StÃ©phane Ducasse

Thanks! Stef On Jan 26, 2013, at 1:26 PM, Esteban Lorenzano wrote: > Hi, > > The AthensPlayground is part of the Storm project, you can find here: http://smalltalkhub.com/#!/~estebanlm/Storm > > I *think* the metacello config is in sync with sources so you just need to follow instruction. If you have any problem please let me know :) > > Esteban > > On Jan 26, 2013, at 1:01 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> Hi esteban >> >> where is your code to try athens? >> It would be good to move all the code to >> Pharo/Athens >> >> >> Stef >> >

Jan. 26, 2013

Re: [Pharo-project] OSProcess updated for Pharo 2.0

by David T. Lewis

On Sun, Jan 27, 2013 at 01:11:07AM +0800, Ben Coman wrote: > David T. Lewis wrote: > >On Sat, Jan 26, 2013 at 08:50:43AM +0800, Ben Coman wrote: > > > >>David T. Lewis wrote: > >> > >>>Unit test notes: > >>> > >>>The AioEventHandlerTestCase failures are due to AioPlugin not included in > >>>the VM. I expect the tests will pass if AioPlugin is added to VM builds. > >>> > >>> > >>Just general curiosity, is there a way to have a test queued to run > >>first which tests for the plug-in, and if it fails the remaining tests > >>become "expected failures" rather than "failures". > >> > > > >Yes, you could do this by implementing #expectedFailures to check for the > >plugin and answer a different set of selectors depending on what it finds. > > > >It all depends on what you mean by an "expected failure". To me, failing > >to find the plugin is not an expected failure. > > Failing to find the plugin should not be an expected failure, but then > all subsequent tests are expected to fail and are just noise. Actually > the recent post on 'test dependencies' in Phexample looks like a good > way to do this. > Now I understand what you mean. You're right. Personally I don't mind seeing all of the tests that are impacted by a problem like this, but I agree it's mostly noise at that point. Dave

Jan. 26, 2013

Re: [Pharo-project] OSProcess updated for Pharo 2.0

by Ben Coman

David T. Lewis wrote: > On Sat, Jan 26, 2013 at 08:50:43AM +0800, Ben Coman wrote: > >> David T. Lewis wrote: >> >>> On Fri, Jan 18, 2013 at 03:28:10PM +0100, Damien Cassou wrote: >>> >>> >>>> you don't need FileSystem-Legacy if you use OSProcess from Coral: >>>> >>>> Gofer new >>>> squeaksource3: 'coral'; >>>> package: 'OSProcess'; >>>> load. >>>> >>>> >>>> >>> OSProcess and CommandShell-Piping should now load cleanly in Pharo 2.0. >>> >>> The latest versions are OSProcess-dtl.75 and CommandShell-Piping-dtl.13 >>> in the SqueakSource repositories for OSProcess and CommandShell. >>> >>> Thanks to Damien Cassou for doing the original work for OSProcess support >>> in Coral. I adapted his work so it will now load in both Squeak and Pharo. >>> >>> Unit test notes: >>> >>> The AioEventHandlerTestCase failures are due to AioPlugin not included in >>> the VM. I expect the tests will pass if AioPlugin is added to VM builds. >>> >>> >> Just general curiosity, is there a way to have a test queued to run >> first which tests for the plug-in, and if it fails the remaining tests >> become "expected failures" rather than "failures". >> > > Yes, you could do this by implementing #expectedFailures to check for the > plugin and answer a different set of selectors depending on what it finds. > > It all depends on what you mean by an "expected failure". To me, failing > to find the plugin is not an expected failure. Failing to find the plugin should not be an expected failure, but then all subsequent tests are expected to fail and are just noise. Actually the recent post on 'test dependencies' in Phexample looks like a good way to do this. > It means that something is > wrong, and somebody should do something about it. In this case it serves > as a reminder to include AioPlugin in the next VM build. After all, that > is one of the reasons for doing all those tests in the first place :) > > A related question is how to handle failures when running on some other OS > (e.g. Windows) where OSProcess is really not meaningfully implemented. In > that case, the failures really are expected. I allow them to fail because > I wrote the tests for my own benefit as the developer (in that context, > a feature that does not work on Windows really should fail the test, as it > shows what still needs to be implemented), but running the tests as part > of a larger suite on a range of operating systems would be a problem. I > don't really have any answer for that. I suppose I could enumerate all the > things that are not expected to work on a non-unix system, but that sounds > like a lot of work (and no fun) to me. > > Dave > > > >>> Many test rely on #forkSqueak to create cooperating OS processes for the >>> tests. These tests fail on Cog, although this does not affect basic >>> functionality of OSProcess itself. >>> >>> UnixProcessAccessorTestCase>>testRedirectStdOutTo fails due to a problem >>> introduced in the oscog branch of the OSProcessPlugin. This should be fixed >>> in the plugin but is a minor concern and does not affect normal usage >>> of OSProcess. >>> >>> Dave >>> >>> >>> >>> >>> > > >

Jan. 26, 2013