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

Jenkins build is back to normal : Pharo-2.0-Tests Â» run 1,vm,win #248

by no-reply＠ci.inria.fr

See <https://ci.inria.fr/pharo/job/Pharo-2.0-Tests/./Run=run%201,VM=vm,label=win…>

June 8, 2013

Re: [Pharo-dev] [Moose-dev] SourceCity works

by StÃ©phane Ducasse

thanks igor :) >> Thank you Igor, >> >> This allowed me to successfully load, debug & run SourceCity on an 10.6.8 Mac. >> > i just updated the config, to fix an issue when using in 3.0 image, > which miss ShortPointArray. > (but it is used only by my demo)

June 8, 2013

Re: [Pharo-dev] [update 3.0] #30188

by StÃ©phane Ducasse

On Jun 8, 2013, at 1:17 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Jun 8, 2013, at 12:31 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> so how do we sync before I do something. >> >> when I run the scripts of esteban >> ./integrate >> >> the staged file is not empty and I do not understand why >> because to me it should be empty. >> right now I have and it looks totally bogus. >> >> #Pharo3.0^M30184-Pha-Update.cs^M30185-Pha-Update.cs^M30186-Pha-Update.cs^M30187-Pha-Update.cs^M30188-Pha-Update.cs^M30188-Pha-Update.cs >> > Yes, it should be empty but it works even like this. It looks just at the last entry. ok so I was not completely wrong. So we sync and I will continue to integrate. > > Marcus > >

June 8, 2013

Re: [Pharo-dev] Necessity of TDD with Smalltalk

by Stephan Eggermont

Ben wrote: >Actually some Smalltalk'ers consider the debugger a major facilitator of >TDD by mostly coding from within the debugger. Yes. It is part of what we present as "TDD done right". We've shown it at a devnology user group meeting in March. If anyone is interested in doing a presentation to their local (non-smalltalk) user group, just let me know. >1. Before writing any application code, write a test. which only contains self assert: false. which is the simplest thing needed to get the test to fail. >2. Execute that test straight away. Of course it fails because you >haven't written any application code. >3. Up comes the debugger - now "from within the debugger" add the >application code needed to satisfy the test. >4. Repeat. While writing the application code, you often notice the name of the test method is not right. Not being able to fix that in the debugger is one of the annoying things why "smalltalk environments are not TDD oriented" (Even though they are much better than other environments for TDD). Another is lack of browser support for long method names. Tests tend to have (very) long names Stephan

June 8, 2013

Re: [Pharo-dev] SourceCity works

by Igor Stasenko

On 8 June 2013 10:29, Stephan Eggermont <stephan(a)stack.nl> wrote: > Thank you Igor, > > This allowed me to successfully load, debug & run SourceCity on an 10.6.8 Mac. > i just updated the config, to fix an issue when using in 3.0 image, which miss ShortPointArray. (but it is used only by my demo) > Steps taken: >> just tried in latest 2.0 image. >> >> Pharo2.0 >> Latest update: #20606 >> >> Gofer new >> smalltalkhubUser: 'PharoExtras' project: 'NBOpenGL'; >> package: 'ConfigurationOfNBOpenGL'; >> load. >> >> (ConfigurationOfNBOpenGL project version: '2.0') load >> >> GLTTRenderingDemo new openInWorld > > Load the individual SourceCity packages from smalltalkhub: > > SourceCity-Core > SourceCity-Importer > SourceCity-Layout > SourceCity-Tools > > remove > display bindRenderBuffers > from > SourceCityGLVizualisationBuilder>fillRenderingList:pickingMode: > SourceCityGLVizualisationRenderer>render > > see it work: > SourceCity exampleRpackage > > Next step: fix code & configuration > > Stephan > > > > On 7 jun 2013, at 23:34, Igor Stasenko wrote: > >> On 7 June 2013 21:07, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>> Hi! >>> >>> I have installed NBOpenGL from http://smalltalkhub.com/#!/~PharoExtras/NBOpenGL >>> I have loaded Version 2.0 using the configuration >>> >>> The method NBMacGlAPI>>glApiCall: fnSpec index: fnIndex attributes: attributes context: contextToRetry refers to the class NBCallFailureHandler, which is not existing >>> >>> Apparently NBSTIvarLoader is also missing... >>> I guess ConfigurationOfNBOpenGL is not loading everything... >>> It would be nice to fix this. >> >> just tried in latest 2.0 image. >> >> Pharo2.0 >> Latest update: #20606 >> >> Gofer new >> smalltalkhubUser: 'PharoExtras' project: 'NBOpenGL'; >> package: 'ConfigurationOfNBOpenGL'; >> load. >> >> (ConfigurationOfNBOpenGL project version: '2.0') load >> >> GLTTRenderingDemo new openInWorld >> >> everything loads and works. >> (it takes 5 minutes to load though... ) >> >>> >>> Cheers, >>> Alexandre >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- Best regards, Igor Stasenko.

June 8, 2013

Re: [Pharo-dev] OpenGL: NBMacGlAPI missing?

by Igor Stasenko

On 7 June 2013 23:34, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 7 June 2013 21:07, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> Hi! >> >> I have installed NBOpenGL from http://smalltalkhub.com/#!/~PharoExtras/NBOpenGL >> I have loaded Version 2.0 using the configuration >> >> The method NBMacGlAPI>>glApiCall: fnSpec index: fnIndex attributes: attributes context: contextToRetry refers to the class NBCallFailureHandler, which is not existing >> >> Apparently NBSTIvarLoader is also missing... >> I guess ConfigurationOfNBOpenGL is not loading everything... >> It would be nice to fix this. > > just tried in latest 2.0 image. > > Pharo2.0 > Latest update: #20606 > > Gofer new > smalltalkhubUser: 'PharoExtras' project: 'NBOpenGL'; > package: 'ConfigurationOfNBOpenGL'; > load. > > (ConfigurationOfNBOpenGL project version: '2.0') load > > GLTTRenderingDemo new openInWorld > > everything loads and works. > (it takes 5 minutes to load though... ) > You can also download an image with preloaded configuration NBOpenGL (https://ci.inria.fr/pharo-contribution/job/NBOpenGL/) from jenkins server. >> >> Cheers, >> Alexandre >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> > > > > -- > Best regards, > Igor Stasenko. -- Best regards, Igor Stasenko.

June 8, 2013

Re: [Pharo-dev] Necessity of TDD with Smalltalk

by Attila Magyar

I think the tests could provide valuable design feedback about the code under test, so it is good to have them. I can respond to those feedbacks effectively only when I'm writing them first, otherwise it might be too late. But this is a long topic. When I write tests first, I like the fact that the initial state of my test is red. So I can catch the point when it changes to green. If this happens when I expect, then I can be sure that I understand what is happening, and I managed to write a meaningful test. Writing tests afterwards makes easier to write tests which are always green. To avoid this I have to break the test after I finished it by changing something in the code. This is an extra step which I can save by writing tests first. -- View this message in context: http://forum.world.st/Pharo-dev-Necessity-of-TDD-with-Smalltalk-tp4691867p4… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 8, 2013

Re: [Pharo-dev] [update 3.0] #30188

by Marcus Denker

On Jun 8, 2013, at 12:31 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > so how do we sync before I do something. > > when I run the scripts of esteban > ./integrate > > the staged file is not empty and I do not understand why > because to me it should be empty. > right now I have and it looks totally bogus. > > #Pharo3.0^M30184-Pha-Update.cs^M30185-Pha-Update.cs^M30186-Pha-Update.cs^M30187-Pha-Update.cs^M30188-Pha-Update.cs^M30188-Pha-Update.cs > Yes, it should be empty but it works even like this. It looks just at the last entry. Marcus

June 8, 2013

Re: [Pharo-dev] [update 3.0] #30188

by Marcus Denker

On Jun 8, 2013, at 12:29 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > when I look at pharo-update I have > > 30186-Pha-Update.cs > 30187-Pha-Update.cs > 30188-Pha-Update.cs > 30189-Pha-Update.cs > updates30.staged > > I do not understand why there is a staged file in there. > The idea is that *only* the staged file should be there, the updates file is just on the server. > #Pharo3.0 > 30184-Pha-Update.cs > 30185-Pha-Update.cs > 30186-Pha-Update.cs > 30187-Pha-Update.cs > 30188-Pha-Update.cs > 30188-Pha-Update.cs > > I do not understand why the staged file is in this folder. > The file should there. There is a bug right now that it contains more than one entry. And there is a bug that the updates30 is wrongly generated (yes, I should have looked at thatâ¦) But it works for the update process. https://pharo.fogbugz.com/f/cases/10412/Pharo-3-updates-list-on-the-server-… > So I'm confused and I looks like that I lost my time. > > > So I can rollback until > 30187 -> ScriptLoader30-StephaneDucasse.214.mcz > > but I do not know how to do it efficiently. No, not needed. I will check. And in general, we should simplify the whole thing. Marcus

June 8, 2013

Re: [Pharo-dev] [update 3.0] #30188

by StÃ©phane Ducasse

so how do we sync before I do something. when I run the scripts of esteban ./integrate the staged file is not empty and I do not understand why because to me it should be empty. right now I have and it looks totally bogus. #Pharo3.0^M30184-Pha-Update.cs^M30185-Pha-Update.cs^M30186-Pha-Update.cs^M30187-Pha-Update.cs^M30188-Pha-Update.cs^M30188-Pha-Update.cs Stef On Jun 8, 2013, at 12:28 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: > when I look at pharo-update I have > > 30186-Pha-Update.cs > 30187-Pha-Update.cs > 30188-Pha-Update.cs > 30189-Pha-Update.cs > updates30.staged > > I do not understand why there is a staged file in there. > > #Pharo3.0 > 30184-Pha-Update.cs > 30185-Pha-Update.cs > 30186-Pha-Update.cs > 30187-Pha-Update.cs > 30188-Pha-Update.cs > 30188-Pha-Update.cs > > I do not understand why the staged file is in this folder. > > So I'm confused and I looks like that I lost my time. > > > So I can rollback until > 30187 -> ScriptLoader30-StephaneDucasse.214.mcz > > but I do not know how to do it efficiently. > > Stef >

June 8, 2013