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

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

by Bruni camillo

Perfect that is really great news! I will try it immediately. On 25 Jan 2013 15:08, "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> wrote: > Thanks a lot david!!! > > Stef > > On Jan 24, 2013, at 10:38 PM, 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. > > > > 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. 25, 2013

Re: [Pharo-project] OrderedCollections and File I/O

by J. P. L. MartÃn

Thank you all for your help, I've used Fuel to save my data and it was really easy to do. Thanks! On Wed, Jan 23, 2013 at 9:43 AM, Edgar J. De Cleene <edgardec2005(a)gmail.com>wrote: > > > > On 1/23/13 8:47 AM, "Mariano Martinez Peck" <marianopeck(a)gmail.com> wrote: > > > On Wed, Jan 23, 2013 at 6:39 AM, Edgar J. De Cleene <* > edgardec2005(a)gmail.com*> wrote: > > > > > On 1/23/13 6:25 AM, "Marcus Denker" <*marcus.denker(a)inria.fr*> wrote: > > > Keep in mind that ReferenceStream is deprecated in 2.0 > > > > The nice thing about Fuel is: > > > > -> Very much faster > > -> output more compact > > -> you can store *any* kind of objects. > > (even the one you are sure you can't, like the Context (stack > > frame)) > > > > Marcus > > Yes , I know Fuel is a great advance, but he ask about simple thing. > And also I said Pharo 1.4 and not Pharo 2.0. > > Thanks to Mariano and others , wish Fuel become Squeak citizen soon, for > Cuis guess should wait longer. > > > Edgar see new release: * > http://forum.world.st/ANN-Fuel-1-8-1-td4661609.html > *Supported and tested images: > Pharo 1.1.1, 1.1.2, 1.2, 1.3, 1.4, 2.0 > Squeak 4.1, 4.2, 4.3, 4.4 > > > Edgar > > > Mariano, yo se eso. > Pareciera que por tratar de ayudar a un nuevo con dos lineas de codigo > estoy desconociendo tu trabajo y el de todos los demas que estan trabajando > con Fuel. > No hay una unica receta, mis amigos de Pharo. > > Edgar >

Jan. 25, 2013

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

by StÃ©phane Ducasse

Thanks a lot david!!! Stef On Jan 24, 2013, at 10:38 PM, 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. > > 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. 25, 2013

Re: [Pharo-project] destructive / regression tests

by Sean P. DeNigris

Camillo Bruni-3 wrote > I think I got it! last night's hacking session was fruitful! > For now I have > ... Nice work, cami! Thanks :) -- View this message in context: http://forum.world.st/destructive-regression-tests-tp4665153p4665352.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 25, 2013

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