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

Re: [Pharo-project] Discard changes after clicking Ok if a condition is false.

by Peter H. Meadows

I don't understand your question. Can you provide more details? Also, I think you'd be better to ask this on the pharo-users list (rather than the dev list) On 25 January 2013 23:02, J. P. L. MartÃn <arguser(a)gmail.com> wrote: > I have an object I want to edit, when I hit ok a question is made,e.g: the > data I've entered doesn't already exist? ifFalse an alertDialogWindow pops > up and it shouldn't apply changes to the object. But I found that ok method > does "applyChanges" when clicked. >

Jan. 26, 2013

[Pharo-project] [update 2.0] #20490

by StÃ©phane Ducasse

20490 ----- Issue 7321: Add fail message with description. Thanks Camillo Bruni. http://code.google.com/p/pharo/issues/detail?id=7321 Issue 7322: Issue 7322: Preparations for Regression Tests: backup image and more vm options. Thanks Camillo Bruni. http://code.google.com/p/pharo/issues/detail?id=7322 Issue 7320: Password field does no longer use asterisks to hide the password. Thanks Benjamin van Ryseghem http://code.google.com/p/pharo/issues/detail?id=7320 Issue 7330: [BUG]: Autocomplete "use enter to accept" broken. Thanks Sean De Nigris http://code.google.com/p/pharo/issues/detail?id=7330 Issue 7329: Reintroduce rename in Nautilus, and move format to another shortcut. Thanks Benjamin van Ryseghem http://code.google.com/p/pharo/issues/detail?id=7329 Diff information: http://ss3.gemstone.com/ss/Pharo20/System-Support-StephaneDucasse.767.diff http://ss3.gemstone.com/ss/Pharo20/SUnit-Core-StephaneDucasse.64.diff http://ss3.gemstone.com/ss/Pharo20/Polymorph-Widgets-StephaneDucasse.758.di… http://ss3.gemstone.com/ss/Pharo20/NautilusRefactoring-StephaneDucasse.66.d… http://ss3.gemstone.com/ss/Pharo20/NECompletion-StephaneDucasse.78.diff http://ss3.gemstone.com/ss/Pharo20/KeyChain-StephaneDucasse.29.diff >From bright sun of Chile :) More to come probably after breakfast :) Stef

Jan. 26, 2013

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

by H. Hirzel

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

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

by Camillo Bruni

=> #last works => Igor you should add a description to the jenkins job with the basics :) On 2013-01-26, at 11:15, Camillo Bruni <camillobruni(a)gmail.com> wrote: > ok, no stable configuration defined ;) > > https://ci.inria.fr/rmod/job/Athens/18/console > > so trying #development > > > On 2013-01-26, at 11:14, Camillo Bruni <camillobruni(a)gmail.com> wrote: > >> I just set up the jenkins job so we have one ;) >> Check the ci configuration: >> >> ./vm.sh $JOB_NAME.image config $REPO ConfigurationOfAthens --install=1.4 >> >> so maybe I should change that to stable... then again, this is not my job either I think ;) >> >> On 2013-01-26, at 01:03, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: >> >>> I opened the MC repository of Athens in the image that we can get from the ci >>> and I do not understand why there are lot of packages that are not the loaded. >>> Are they current development? >>> Is the CI image really holding the latest stable version? >>> >>> Stef

Jan. 26, 2013

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

by Camillo Bruni

ok, no stable configuration defined ;) https://ci.inria.fr/rmod/job/Athens/18/console so trying #development On 2013-01-26, at 11:14, Camillo Bruni <camillobruni(a)gmail.com> wrote: > I just set up the jenkins job so we have one ;) > Check the ci configuration: > > ./vm.sh $JOB_NAME.image config $REPO ConfigurationOfAthens --install=1.4 > > so maybe I should change that to stable... then again, this is not my job either I think ;) > > On 2013-01-26, at 01:03, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: > >> I opened the MC repository of Athens in the image that we can get from the ci >> and I do not understand why there are lot of packages that are not the loaded. >> Are they current development? >> Is the CI image really holding the latest stable version? >> >> Stef >> >> >> >> >> >>> I tried the latest image >>> >>> getLibraryPath >>> >>> (NativeBoost platformId = NativeBoostConstants linux32PlatformId) ifTrue: [ >>> ^ '/usr/lib/libcairo.so' >>> ]. >>> (NativeBoost platformId = NativeBoostConstants mac32PlaformId) ifTrue: [ >>> ^ 'libcairo.2.dylib' >>> ]. >>> self error: 'define your own path' >>> >>> >>> and I got an error >>> NativeBoostConstants mac32PlaformId DNU ? >>> >>> :( >>> >>> I'm sad. Why we do not have a version working with the vm. >>> How can we expect other people to use it? >>> >>> Stef >>> >>> >>> >>> >>> On Jan 25, 2013, at 8:41 PM, StÃ©phane Ducasse wrote: >>> >>>> Ok this is the image but where is the vm that I should use? >>>> >>>> Stef >>>> >>>> On Jan 20, 2013, at 7:30 PM, Camillo Bruni wrote: >>>> >>>>> You should not even have to ask for it ;) >>>>> >>>>> https://ci.inria.fr/rmod/job/Athens/ >>>>> >>>>> >>>>> On 2013-01-20, at 16:00, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>>> >>>>>> Because I want to try boids. >>>>>> >>>>>> Stef >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> >

Jan. 26, 2013

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

by Camillo Bruni

I just set up the jenkins job so we have one ;) Check the ci configuration: ./vm.sh $JOB_NAME.image config $REPO ConfigurationOfAthens --install=1.4 so maybe I should change that to stable... then again, this is not my job either I think ;) On 2013-01-26, at 01:03, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: > I opened the MC repository of Athens in the image that we can get from the ci > and I do not understand why there are lot of packages that are not the loaded. > Are they current development? > Is the CI image really holding the latest stable version? > > Stef > > > > > >> I tried the latest image >> >> getLibraryPath >> >> (NativeBoost platformId = NativeBoostConstants linux32PlatformId) ifTrue: [ >> ^ '/usr/lib/libcairo.so' >> ]. >> (NativeBoost platformId = NativeBoostConstants mac32PlaformId) ifTrue: [ >> ^ 'libcairo.2.dylib' >> ]. >> self error: 'define your own path' >> >> >> and I got an error >> NativeBoostConstants mac32PlaformId DNU ? >> >> :( >> >> I'm sad. Why we do not have a version working with the vm. >> How can we expect other people to use it? >> >> Stef >> >> >> >> >> On Jan 25, 2013, at 8:41 PM, StÃ©phane Ducasse wrote: >> >>> Ok this is the image but where is the vm that I should use? >>> >>> Stef >>> >>> On Jan 20, 2013, at 7:30 PM, Camillo Bruni wrote: >>> >>>> You should not even have to ask for it ;) >>>> >>>> https://ci.inria.fr/rmod/job/Athens/ >>>> >>>> >>>> On 2013-01-20, at 16:00, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>> >>>>> Because I want to try boids. >>>>> >>>>> Stef >>>>> >>>> >>>> >>> >>> >> >> > >

Jan. 26, 2013

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

by Peter H. Meadows

Very cool. Thanks! On 25 January 2013 22:23, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > nono... I downloaded latest version and it says "class side" :) > > On Jan 25, 2013, at 11:21 PM, Benjamin < > benjamin.vanryseghem.pharo(a)gmail.com> wrote: > > > Has been done, and probably lost in the versions > > > > > > > > Ben > > > > On Jan 25, 2013, at 11:19 PM, Sven Van Caekenberghe wrote: > > > >> > >> On 25 Jan 2013, at 22:27, "Sean P. DeNigris" <sean(a)clipperadams.com> > wrote: > >> > >>> EstebanLM wrote > >>>> Issue 7296: visual feedback from 'class side button' when a > class has > >>>> class side methods > >>> > >>> Great idea! > >> > >> Indeed. > >> > >> But like in the sentence above I would prefer 'class side' as label > instead of 'show class'. > >> > >> Just an idea... > > > > > > >

Jan. 26, 2013

Re: [Pharo-project] In-Image Fuel Documentation

by H. Hirzel

On 1/26/13, Ben Coman <btc(a)openinworld.com> wrote: > Mariano Martinez Peck wrote: >> On Thu, Jan 24, 2013 at 4:16 PM, Sean P. DeNigris >> <sean(a)clipperadams.com>wrote: >> >> >>> I eventually found this awesome website [1]. It would be great if there >>> were >>> some basic examples in the image. I found the tests too well factored to >>> be >>> used for this purpose. >>> >> >> >> what do you mean by this? >> FLUserGuidesTest contains the examples used in the website (although >> there >> may not be everything and still it could be outdated). >> Maybe we can move this test into a Fuel-Examples package? >> > +1 When a someone first installs a package, to find and know about > FLUserGuidesTest is a random walk and a guess. Having a package named > *-Examples draws the user's attention immediately. > +1 for the Examples package, I did not find the tests either .... --Hannes

Jan. 26, 2013

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

by David T. Lewis

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. 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

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

by Ben Coman

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". > 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