- Pharo-dev - lists.pharo.org

Re: [Pharo-project] OSProcess updated for Pharo 2.0 (was: The monkey is back in town)

by David T. Lewis

On Fri, Jan 25, 2013 at 10:54:40AM +0100, Camillo Bruni wrote: > very nice! thanks! > So that means all the FileSystem changes have been included? I think so, yes. I'm not too familiar with using FileSystem yet, so let me know if I missed something. So far I have done the updates for all of OSProcess and CommandShell-Piping, but I have not yet done the rest of CommandShell. There is a lot of file system interaction in CommandShell, so that may take a while. But OSProcess is done, and class PipeableOSProcess in CommandShell-Piping is updated too. So that should be a help for many people. Dave > > On 2013-01-25, at 05:14, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > > > David T. Lewis wrote > >> OSProcess and CommandShell-Piping should now load cleanly in Pharo 2.0. > > > > Awesome!!! Thank you David. I just successfully used PipeableOSProcess in > > latest 2.0 with no load errors. > > > > Cheers, > > Sean > >

Jan. 25, 2013

Re: [Pharo-project] SmallLint applied on Pharo: Continued

by Jan Vrany

Ok, no stress. It's not like I've nothing else to do. Let me know once published :-) Jan On 25/01/13 12:32, StÃ©phane Ducasse wrote: > No I should publish them but I'm slow. > and doing too many things â¦ is it related :)? > > Stef > On Jan 25, 2013, at 9:24 AM, Jan Vrany wrote: > >> On 24/01/13 18:05, StÃ©phane Ducasse wrote: >>> Thanks! >> >> You're welcome! >> Are your recent changes included in Pharo 2.0 builds? Because I want >> to have a look at your changes. >> >> Jan >> >>> >>> On Jan 24, 2013, at 7:48 AM, Jan Vrany wrote: >>> >>>> Hi, >>>> >>>> we've made all SmallLint code in Smalltalk/X MIT-licensed. >>>> Enjoy. >>>> >>>> Jan >>>> >>>> >>>> On 22/01/13 23:59, StÃ©phane Ducasse wrote: >>>>>> Well. I've written the tag support, so let's make it simple, MIT. >>>>>> I may export a changeset with that code for you, if you like. >>>>> >>>>> Else I will just go over them and it will help me to understand. I think that this is not difficult. >>>>> >>>>>> For rules written by CG I'm not sure. You should check with him. >>>>>> But I think it won't be a problem given that you preserve all >>>>>> the signatures and #documentation and #version_XXX methods >>>>>> (we use them to track changes in the source). >>>>>> >>>>>> However, what I planned (and run out of time :-) is to make >>>>>> tag a first class object with name (symbol) description etc >>>>>> and have class methods to create them. Then one may define and >>>>>> describe meaning of the tag in an extension method. >>>>>> Also, the selection/rejection logic could dispatch back on >>>>>> the tag instance so you may then create fancy dynamic tags >>>>>> (like #portability that automatically includes everything tagged >>>>>> as #pharo #squeak #stx #va, for instance or whatever. >>>>>> >>>>>> I might hack it later this week, if you would include it into >>>>>> your version (otherwise I've more important things to do :-) >>>>> >>>>> I imagine well. >>>>> Let us keep it simple. Simple tags with a little class comments are good enough :) >>>>> >>>>>> >>>>>> Cheers >>>>>> >>>>>> On 22/01/13 19:32, StÃ©phane Ducasse wrote: >>>>>>> Jan >>>>>>> what is the license of your tags and other code? >>>>>>> >>>>>>> Stef >>>>>>> >>>>>>> On Jan 22, 2013, at 3:45 PM, Jan Vrany wrote: >>>>>>> >>>>>>>> On 22/01/13 18:22, StÃ©phane Ducasse wrote: >>>>>>>>> Hi >>>>>>>>> >>>>>>>>> I'm running the rule RBSubclassResponsibilityNotDefinedRule that >>>>>>>>> >>>>>>>>> Checks that all subclassResponsibility methods are defined in all leaf classes. >>>>>>>>> >>>>>>>>> Now the results display the sender of ^ subclassResponsibility but I have to manually find the >>>>>>>>> problems. I would be better to report the violations. Of course this is not that simple: returning a class and missing method. >>>>>>>>> >>>>>>>>> But this would be much better. Jan did you do that in your version? >>>>>>>> >>>>>>>> Good point. Yes, since now we do that :-) >>>>>>>> >>>>>>>> Jan >>>>>>>> >>>>>>>>> >>>>>>>>> Stef >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>> >>>> <smalltalkx-lint.zip> >>> >>> >>> >> >> > > >

Jan. 25, 2013

Re: [Pharo-project] SmallLint applied on Pharo: Continued

by StÃ©phane Ducasse

No I should publish them but I'm slow. and doing too many things â¦ is it related :)? Stef On Jan 25, 2013, at 9:24 AM, Jan Vrany wrote: > On 24/01/13 18:05, StÃ©phane Ducasse wrote: >> Thanks! > > You're welcome! > Are your recent changes included in Pharo 2.0 builds? Because I want > to have a look at your changes. > > Jan > >> >> On Jan 24, 2013, at 7:48 AM, Jan Vrany wrote: >> >>> Hi, >>> >>> we've made all SmallLint code in Smalltalk/X MIT-licensed. >>> Enjoy. >>> >>> Jan >>> >>> >>> On 22/01/13 23:59, StÃ©phane Ducasse wrote: >>>>> Well. I've written the tag support, so let's make it simple, MIT. >>>>> I may export a changeset with that code for you, if you like. >>>> >>>> Else I will just go over them and it will help me to understand. I think that this is not difficult. >>>> >>>>> For rules written by CG I'm not sure. You should check with him. >>>>> But I think it won't be a problem given that you preserve all >>>>> the signatures and #documentation and #version_XXX methods >>>>> (we use them to track changes in the source). >>>>> >>>>> However, what I planned (and run out of time :-) is to make >>>>> tag a first class object with name (symbol) description etc >>>>> and have class methods to create them. Then one may define and >>>>> describe meaning of the tag in an extension method. >>>>> Also, the selection/rejection logic could dispatch back on >>>>> the tag instance so you may then create fancy dynamic tags >>>>> (like #portability that automatically includes everything tagged >>>>> as #pharo #squeak #stx #va, for instance or whatever. >>>>> >>>>> I might hack it later this week, if you would include it into >>>>> your version (otherwise I've more important things to do :-) >>>> >>>> I imagine well. >>>> Let us keep it simple. Simple tags with a little class comments are good enough :) >>>> >>>>> >>>>> Cheers >>>>> >>>>> On 22/01/13 19:32, StÃ©phane Ducasse wrote: >>>>>> Jan >>>>>> what is the license of your tags and other code? >>>>>> >>>>>> Stef >>>>>> >>>>>> On Jan 22, 2013, at 3:45 PM, Jan Vrany wrote: >>>>>> >>>>>>> On 22/01/13 18:22, StÃ©phane Ducasse wrote: >>>>>>>> Hi >>>>>>>> >>>>>>>> I'm running the rule RBSubclassResponsibilityNotDefinedRule that >>>>>>>> >>>>>>>> Checks that all subclassResponsibility methods are defined in all leaf classes. >>>>>>>> >>>>>>>> Now the results display the sender of ^ subclassResponsibility but I have to manually find the >>>>>>>> problems. I would be better to report the violations. Of course this is not that simple: returning a class and missing method. >>>>>>>> >>>>>>>> But this would be much better. Jan did you do that in your version? >>>>>>> >>>>>>> Good point. Yes, since now we do that :-) >>>>>>> >>>>>>> Jan >>>>>>> >>>>>>>> >>>>>>>> Stef >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>>> >>> >>> <smalltalkx-lint.zip> >> >> >> > >

Jan. 25, 2013

Re: [Pharo-project] SmallLint applied on Pharo: Continued

by Jan Vrany

On 24/01/13 18:05, StÃ©phane Ducasse wrote: > Thanks! You're welcome! Are your recent changes included in Pharo 2.0 builds? Because I want to have a look at your changes. Jan > > On Jan 24, 2013, at 7:48 AM, Jan Vrany wrote: > >> Hi, >> >> we've made all SmallLint code in Smalltalk/X MIT-licensed. >> Enjoy. >> >> Jan >> >> >> On 22/01/13 23:59, StÃ©phane Ducasse wrote: >>>> Well. I've written the tag support, so let's make it simple, MIT. >>>> I may export a changeset with that code for you, if you like. >>> >>> Else I will just go over them and it will help me to understand. I think that this is not difficult. >>> >>>> For rules written by CG I'm not sure. You should check with him. >>>> But I think it won't be a problem given that you preserve all >>>> the signatures and #documentation and #version_XXX methods >>>> (we use them to track changes in the source). >>>> >>>> However, what I planned (and run out of time :-) is to make >>>> tag a first class object with name (symbol) description etc >>>> and have class methods to create them. Then one may define and >>>> describe meaning of the tag in an extension method. >>>> Also, the selection/rejection logic could dispatch back on >>>> the tag instance so you may then create fancy dynamic tags >>>> (like #portability that automatically includes everything tagged >>>> as #pharo #squeak #stx #va, for instance or whatever. >>>> >>>> I might hack it later this week, if you would include it into >>>> your version (otherwise I've more important things to do :-) >>> >>> I imagine well. >>> Let us keep it simple. Simple tags with a little class comments are good enough :) >>> >>>> >>>> Cheers >>>> >>>> On 22/01/13 19:32, StÃ©phane Ducasse wrote: >>>>> Jan >>>>> what is the license of your tags and other code? >>>>> >>>>> Stef >>>>> >>>>> On Jan 22, 2013, at 3:45 PM, Jan Vrany wrote: >>>>> >>>>>> On 22/01/13 18:22, StÃ©phane Ducasse wrote: >>>>>>> Hi >>>>>>> >>>>>>> I'm running the rule RBSubclassResponsibilityNotDefinedRule that >>>>>>> >>>>>>> Checks that all subclassResponsibility methods are defined in all leaf classes. >>>>>>> >>>>>>> Now the results display the sender of ^ subclassResponsibility but I have to manually find the >>>>>>> problems. I would be better to report the violations. Of course this is not that simple: returning a class and missing method. >>>>>>> >>>>>>> But this would be much better. Jan did you do that in your version? >>>>>> >>>>>> Good point. Yes, since now we do that :-) >>>>>> >>>>>> Jan >>>>>> >>>>>>> >>>>>>> Stef >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>> >>>> >>> >>> >>> >> >> <smalltalkx-lint.zip> > > >

Jan. 25, 2013

Re: [Pharo-project] DocTest

by Noury Bouraqadi

I find PhExample very interesting! Is there any doc/paper other than these two web pages. Noury On 23 janv. 2013, at 11:34, Tudor Girba wrote: > FYI, we are already using Phexample in Moose since several years, and it just works out of the box next to Sunit. > > Doru > > On Wednesday, January 23, 2013, Sven Van Caekenberghe wrote: > Yes we #should ;-) > > It is beautiful. > > On 23 Jan 2013, at 11:04, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > > check the project page for all examples and explanations: > > > > http://smalltalkthoughts.blogspot.ch/2009/11/phexample-because-examples-exp… > > http://www.iam.unibe.ch/~akuhn/blog/2009/shoulda-use-this-in-pharo > > > > to me this feels more like Smalltalk and less like Java ;) > > > > On 2013-01-23, at 08:47, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > >> Who should assert then? > >> From a certain POV, it does not seem that awfully unlogical to > >> delegate this responsability to a TestCase. > >> A TestCase is here to assert some rule. > >> > >> Nicolas > >> > >> 2013/1/23 Camillo Bruni <camillobruni(a)gmail.com>: > >>> for that we already have a fully working Phexample: > >>> > >>> http://www.squeaksource.com/phexample.html > >>> > >>> which I will push in 3.0, cause I never really liked #assert: and friends being > >>> sent to self. Furthermore we could finally build up decent messages! > >>> > >>> On 2013-01-22, at 18:24, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >>> > >>>> it would be nice to introduce the same syntax than Sunit > >>>> > >>>> exp assert: exp2 > >>>> > >>>> [ exp ] shouldraise: > >>>> > >>>> Stef > >>>> > >>>> > >>>> On Jan 21, 2013, at 4:41 AM, Benjamin wrote: > >>>> > >>>>> Hi guys, > >>>>> > >>>>> I am attending a python lecture and discovered DocTest[1], and I was wondering if such a tool exists for Pharo ? :) > >>>>> > >>>>> > >>>>> Ben > >>>>> > >>>>> [1]http://docs.python.org/2/library/doctest.html > >>>>> > >>>>> > >>>> > >>>> > >>> > >>> > >> > > > > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > Noury Bouraqadi Ecole des Mines de Douai http://car.mines-douai.fr/noury -- Afin de contribuer au respect de l'environnement, merci de n'imprimer ce courriel qu'en cas de necessite Please consider the environment before you print

Jan. 25, 2013

[Pharo-project] [update 2.0] #20488

by Esteban Lorenzano

20488 ----- Issue 7318: [BUG]: Partial Autocomplete DNU in Nautilus http://code.google.com/p/pharo/issues/detail?id=7318 Issue 7316: Jenkins: Some tests are run twice http://code.google.com/p/pharo/issues/detail?id=7316 Issue 7311: making MCfileInspector more robust to broken files http://code.google.com/p/pharo/issues/detail?id=7311 Issue 7207: Solution for issue 3882 introduced bugs with scaling and moving ImageMorphs using Morphic Halos http://code.google.com/p/pharo/issues/detail?id=7207 Diff information: http://ss3.gemstone.com/ss/Pharo20/NECompletion-EstebanLorenzano.76.diff http://ss3.gemstone.com/ss/Pharo20/Morphic-EstebanLorenzano.1332.diff http://ss3.gemstone.com/ss/Pharo20/MonticelloGUI-EstebanLorenzano.210.diff http://ss3.gemstone.com/ss/Pharo20/Monticello-EstebanLorenzano.747.diff http://ss3.gemstone.com/ss/Pharo20/HudsonBuildTools20-EstebanLorenzano.21.d…

Jan. 25, 2013

[Pharo-project] Fwd: problem related to showOnly in Glamour

by Usman Bhatti

Since the problem is occurring in Morphs, if someone from can have a look into the problem, it'll be great. PaginatedMorphTreeMorph(Object)>>doesNotUnderstand: #setSelectedMorph: ---------- Forwarded message ---------- From: Usman Bhatti <usman.bhatti(a)gmail.com> Date: Thu, Jan 24, 2013 at 6:11 PM Subject: problem related to showOnly in Glamour To: Moose-related development <moose-dev(a)iam.unibe.ch> I think I have stumbled upon a problem in Glamour. When selecting an entity that is in the model but not shown in the Tree presentation, there is a DNU when setting the selection port to the entity. To reproduce the problem: - execute the following script in Moose then right click and select "select in tree" on a number not displayed in the Tree presentation. The problem might arise due to the fact that all model entities do not have their morph nodes when using showOnly option. Can you please have a look? | browser items | browser := GLMTabulator withStatusbar. items := 50. browser column: #one; column: #two. browser transmit to: #one; andShow: [ :a | (a tree) title: 'Tree'; showOnly: 30; display: [:each | 1 to: items]; children: [ :item :x :level | level > 1 ifTrue: [ #() ] ifFalse: [ 1 to: item ]]]. browser transmit to: #two; from: #one; andShow: [ :a | a mondrian title: 'Numbers in Mondrian list'; painting: [:view :number | view shape rectangle width: 20; text: #printString; withoutBorder. view interaction item: 'Select in tree' action: [:each | ((browser paneNamed: #one) port:#selection) value:each ]. view nodes: (1 to: 40). view gridLayout. ] ]. browser openOn: 1 tx, Usman

Jan. 25, 2013

Re: [Pharo-project] destructive / regression tests

by Camillo Bruni

I think I got it! last night's hacking session was fruitful! For now I have - simple command line tests that run commandline arguments in a separate image and capture stdout/stderr - complete test-cases that are run in a separate image (including UI) by forking of images at the right point during test cases to accomplish that I requires OSProcess and redirect stderr/stdout to files. Furthermore I added a new save method to SmalltalkImage which does not transfer control to the new image but rather sticks to the original image. I will prepare a Configuration now On 2013-01-24, at 18:23, Marcus Denker <marcus.denker(a)inria.fr> wrote: > On Jan 24, 2013, at 6:16 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> On 24 January 2013 18:12, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>> I've been thinking these days on how to implement regression tests. >>> Obviously the core requirement is to launch a separate image and capture terminal output and/or result files. >>> >>> For now I will put them into a separate repository: >>> >>> http://smalltalkhub.com/#!/~Pharo/regression-testing >>> >>> Some question: >>> - Is there a test ConfigurationOf* which can be used to try loading different versions / groups? >>> - Is it ok to rely on OSProcess for now to run launch a separate new image? >> >> + 1 >> we need such tests. >> And actually it would be even useful to know which code crashing the >> system , e.g. >> we can even have a tests which succeed only if they crashing VM. > > Yes! > > We did a first (ad-hoc) regression tester for Opal: > > https://ci.inria.fr/rmod/job/OpalRegression/ > > We just have the tests in different packages and take care which to run when. The regression-test job > runs first slow tests that can not do any harm (compiling all method, but not installing them), > then as a second to run tests that recompile the whole image, this we save and then run all tests > on that: > > > ./vm.sh $JOB_NAME.image test --junit-xml-output "OpalCompiler-RegressionTests.*" > ./vm.sh $JOB_NAME.image test --junit-xml-output "OpalCompiler-DestructiveRegressionTests.*" --save > ./vm.sh $JOB_NAME.image test --junit-xml-output ".*" > > With that in place we can be quire sure that a change done on the compiler is not doing anything wrong. > (and that speeds up development quite a lotâ¦) > > Marcus > >

Jan. 25, 2013

Re: [Pharo-project] OSProcess updated for Pharo 2.0 (was: The monkey is back in town)

by Camillo Bruni

very nice! thanks! So that means all the FileSystem changes have been included? On 2013-01-25, at 05:14, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > David T. Lewis wrote >> OSProcess and CommandShell-Piping should now load cleanly in Pharo 2.0. > > Awesome!!! Thank you David. I just successfully used PipeableOSProcess in > latest 2.0 with no load errors. > > Cheers, > Sean > > > > -- > View this message in context: http://forum.world.st/The-monkey-is-back-in-town-tp4658091p4665268.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Jan. 25, 2013

[Pharo-project] SmalltalkInspect: Progressing with Pharo, an Interview with Stephane Ducasse

by Marcus Denker

"We start the fresh year 2013 with an interview with Stephane Ducasse from Inria, who started the Pharo Smalltalk project with a bunch of Smalltalkers [â¦] Aside from the product evolution of Pharo, we cover the new Pharo Consortium and Pharo Association, two organizations that were founded last year" http://smalltalkinspect.podspot.de/post/023-en-progressing-with-pharo-an-in…

Jan. 25, 2013