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

Re: [Pharo-project] Proposal to refactor MethodFinder with pragmas

by Pavel Krivanek

What about only to use a pragma directly in the methods that will inform that the method has no side effect and doesn't modify the state of the object? This information may be used not only for the MethodFinder. -- Pavel On Fri, Jun 24, 2011 at 11:25 AM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > Currently MethodFinder uses a list of acceptable selectors to execute. > This list of selectors is not maintained which results in a lot of > selectors to exist only in this list as they have been removed in the > system. I propose to use pragmas on classes to generate this list > automatically. > > Here is an example > > Magnitude class>>finderApprovedMethods > Â Â Â <finderApproveInstanceMethod: #max:> > Â Â Â <finderApproveInstanceMethod: #min:> > Â Â Â <finderApproveInstanceMethod: #min:max:> > Â Â Â <finderApproveInstanceMethod: #< > > Â Â Â <finderApproveInstanceMethod: #<= > > Â Â Â <finderApproveInstanceMethod: #< > > Â Â Â <finderApproveInstanceMethod: #<= > > Â Â Â <finderApproveInstanceMethod: #between:and: > > > What do you think? > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry > >

June 24, 2011

[Pharo-project] Proposal to refactor MethodFinder with pragmas

by Damien Cassou

Currently MethodFinder uses a list of acceptable selectors to execute. This list of selectors is not maintained which results in a lot of selectors to exist only in this list as they have been removed in the system. I propose to use pragmas on classes to generate this list automatically. Here is an example Magnitude class>>finderApprovedMethods <finderApproveInstanceMethod: #max:> <finderApproveInstanceMethod: #min:> <finderApproveInstanceMethod: #min:max:> <finderApproveInstanceMethod: #< > <finderApproveInstanceMethod: #<= > <finderApproveInstanceMethod: #< > <finderApproveInstanceMethod: #<= > <finderApproveInstanceMethod: #between:and: > What do you think? -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

June 24, 2011

Re: [Pharo-project] [update 1.3] #13274

by Pavel Krivanek

Great, can you try to integrate this issue too: http://code.google.com/p/pharo/issues/detail?id=4435 Then no override of standard Pharo content will be necessary for generation of kernel, gofer and core image. Cheers, -- Pavel On Fri, Jun 24, 2011 at 9:47 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > 13274 > ----- > > Issue 4445: Â Â shrinkToKernel later ChangeSets cleanup > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=4445 > > Issue 4436: Â Â HandMorph mouseTrailFrom: problem > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=4436 > > Issue 4443: Â Â StrikeFontSet isSynthetic > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=4443 > > > -- > Marcus Denker Â -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > >

June 24, 2011

[Pharo-project] [update 1.3] #13274

by Marcus Denker

13274 ----- Issue 4445: shrinkToKernel later ChangeSets cleanup http://code.google.com/p/pharo/issues/detail?id=4445 Issue 4436: HandMorph mouseTrailFrom: problem http://code.google.com/p/pharo/issues/detail?id=4436 Issue 4443: StrikeFontSet isSynthetic http://code.google.com/p/pharo/issues/detail?id=4443 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 24, 2011

Re: [Pharo-project] ConfigurationOfPhexample (was #assert:equals: feels backwards)

by laurent laffont

Added: Gofer it squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfPhexample'; load. (Smalltalk at: #ConfigurationOfPhexample) load. Actually one test is failing in PharoCore 1.3: ForExampleStack>>shouldFailWhenPopEmpty Laurent. On Thu, Jun 23, 2011 at 10:18 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Phexample does not patch SUnit at all. It adds only Object>>should, and > then everything else is 100% SUnit compatible by extending TestCase with > Phexample. > > But beside the DSL, with Phexample you also get a new way of organizing > your tests. Every test returns a value and thus becomes an example. And > examples can be based on other examples. This simple change makes the setUp > irrelevant because you can simply use an example for setting up. > > I believe this is a cool infrastructure. > > Cheers, > Doru > > > On 22 Jun 2011, at 08:38, laurent laffont wrote: > > > > > On Wed, Jun 22, 2011 at 7:58 AM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > > > > On Jun 22, 2011, at 7:44 AM, laurent laffont wrote: > > > > > Camillo and Dennis, > > > > > > Thanks for answer and yes, I think you're right about using > PhExample/Mocketry DSL, that's the way to go. > > > > except that I would not patch SUnit but have another Testing framework > for that. > > And I\m not sure that I want to write should equals:..... not enought > experience to have a good point of view > > > > > > > > I don't know about PhExample but Mocketry does not patch SUnit but > provide extensions to Object / SmallInteger / ... for the DSL part. > > > > It loads easily and also have an HelpSystem book :) > > > > Gofer it > > squeaksource: 'MetacelloRepository'; > > package: 'ConfigurationOfMocketry'; > > load. > > > > ConfigurationOfMocketry load. > > > > 1 should equal: 1. > > > > > > I think I will use it for TWM. > > > > > > Laurent. > > > > > > > > Laurent. > > > > > > > > > On Wed, Jun 22, 2011 at 6:31 AM, Dennis Schetinin <chaetal(a)gmail.com> > wrote: > > > > > > > > > 2011/6/22 laurent laffont <laurent.laffont(a)gmail.com> > > > IMO having the expected value before is the right way ! Do you TDD ? It > makes a lot of sense for me to write assert: expected equals: actual. Am I > alone ? > > > > > > I practice TDD, and I start tests with assertions (after naming them). > But I'm not sure I specify expected value first, as I'm focused on the > result (I write the test for). Btw, I use Mocketry and exploit its sugar (or > DSL?) for specifications there. So, I write: > > > > > > actualValue should equal: expectedValue. > > > > > > That is, after I've decided on a test case and named it, I think: what > should I test? That's the actualValue. I name and write it. And only after > that, I think about the value it should haveâ¦ well, in most cases at least. > > > > > > Anyway, I'm not sure an order I use to write assertion should be > repeated by assertion messages. Just as order I use to write a test (name -> > assertion -> the way to fetch the actual value -> â¦) is not reflected by > test code. It's much more important to have a readable and understandable > (after many months) code. And for me it's much more natural to read it this > way: > > > > > > self assert: actualValue equals: expectedValue > > > > > > > > > > > > If you do TDD, you have first to decide what you expect. You don't know > how to get it because the code doesn't exist yet. So you usually I write > > > > > > self assert: 'i want this' equals: > > > > > > then stop because I have to think about the interface / selectors / > object I want. So it matches the flow of thought when I'm writing tests. > > > > > > And the other weird thing is that with this "fix" I now have to change > hundred of tests I've written to be semantically correct !!!! > > > > > > > > > Laurent. > > > > > > > > > On Wed, Jun 22, 2011 at 12:39 AM, Sean P. DeNigris < > sean(a)clipperadams.com> wrote: > > > > > > Mariano Martinez Peck wrote: > > > > > > > > I don't understand Sean's problem. > > > > > > > > > > Still using 1.2.2 :) Thanks for fixing it. > > > > > > Sean > > > > > > -- > > > View this message in context: > http://forum.world.st/assert-equals-feels-backwards-tp3614760p3615548.html > > > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > > > > > > > > > > > > > > > > -- > > > Dennis Schetinin > > > > > > > > > > > -- > www.tudorgirba.com > > "Sometimes the best solution is not the best solution." > > >

June 23, 2011

[Pharo-project] [update 1.3] #13273

by Marcus Denker

13273 ----- Issue 4434: CrLfFileStream>>#lineEndingConvention: http://code.google.com/p/pharo/issues/detail?id=4434 Issue 4129: #assert:equals: is the opposite as expected http://code.google.com/p/pharo/issues/detail?id=4129 Issue 4437: safer FreeTypeSettings>>#monitorType http://code.google.com/p/pharo/issues/detail?id=4437 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 23, 2011

Re: [Pharo-project] [Pharo-users] [COTDC] 77 - LazyMorphTreeMorph

by Tudor Girba

I am a MorphTreeMorph, but I only render the rows lazily as they appear on screen. Caveat: There is no rendering in the background. This means that if a row takes too long to render, you can experience a shorter or longer freeze when scrolling. Doru On 23 Jun 2011, at 20:46, laurent laffont wrote: > Today: LazyMorphTreeMorph > > > Comment Of The Day Contest - One Day One Comment > Rules: > #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). > #2: If you cannot comment it, deprecate it. > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > Laurent -- www.tudorgirba.com "What we can governs what we wish."

June 23, 2011

[Pharo-project] [COTDC] 77 - LazyMorphTreeMorph

by laurent laffont

Today: LazyMorphTreeMorph Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

June 23, 2011

Re: [Pharo-project] [COTDC] 75 - MorphTreeNavigationBar

by laurent laffont

On Wed, Jun 22, 2011 at 9:30 PM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > Today: MorphTreeNavigationBar > I'm a pager control used to navigate in a MorphTreeMorph that has a lot of entries. You can see one of my subclass in action using: ClassListExample new open Laurent > > Comment Of The Day Contest - One Day One Comment > Rules: > #1: Each day a not commented class is elected. Each day the best comment > will be integrated with name of the author(s). > #2: If you cannot comment it, deprecate it. > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > Laurent >

June 23, 2011

Re: [Pharo-project] [PBE-Spanish] Status update 2011-06-21

by Clara Allende

But I'm Argentinian :D It's quite common here too :O 2011/6/23 Alexandre Bergel <alexandre.bergel(a)me.com> > Allende is a common name here in Chile :-) > It is a bit like "Dupon" in France > > Alexandre > > > On 23 Jun 2011, at 08:30, Clara Allende wrote: > > > BTW, I'm not related to her :P nor to Salvador Allende (the Chilean > president). At least not that I'm aware of :D > > Maybe I could inherit a lot of money and I don't know about it ;) LOL > > > > 2011/6/23 Mariano Martinez Peck <marianopeck(a)gmail.com> > > > > > > On Wed, Jun 22, 2011 at 11:12 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > > thanks clara this is great to see this book translation making progress. > > We are creating good energy. > > > > Stef (I will ask mariano to explain me for the surname) > > > > > > http://en.wikipedia.org/wiki/Isabel_Allende > > > > :) > > > > > > > > On Jun 22, 2011, at 8:10 PM, Clara Allende wrote: > > > > > I would like to help with the translation if I can :) and if you wish > :O > > > > > > 2011/6/21 Diogenes Moreira <diogenes.moreira(a)gmail.com> > > > Thank you very muchhhhhhhh. for your efforts > > > > > > D > > > (and the english wrong readers ) > > > > > > > > > On Tue, Jun 21, 2011 at 8:52 PM, Nicolas Paez <nicopaez(a)gmail.com> > wrote: > > > Hello everyone, > > > > > > Here is the weekly update of the Spanish translation of Pharo By > Example book. > > > > > > Summary > > > â¢ Just 4 charpters remaining to complete the rough translation. > > > â¢ During this week we will focus on completing the translation of > the remaining chapters and on fixing the compilation errors we are getting. > > > â¢ We have also started to define the revision process. > > > â¢ By end of June we will publish a new drop with the completed > chapters. > > > Chapters drill down > > > > > > Chapter 01: 80% > > > Chapter 02: completed, but not published yet and with compilation > errors > > > Chapter 03: completed, already published > > > Chapter 04: completed, already published > > > Chapter 05: completed, but not published yet and with compilation > errors > > > Chapter 06: 21% > > > Chapter 07: completed, and with compilation errors > > > Chapter 08: completed, and with compilation errors > > > Chapter 09: completed, and with compilation errors > > > Chapter 10: just started > > > Chapter 11: completed, already published > > > Chapter 12: 52% > > > Chapter 13: completed, and with compilation errors > > > Chapter 14: completed > > > > > > Regards, > > > NicoPaez > > > http://nicopaez.wordpress.com > > > > > > > > > > > > > > > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > >

June 23, 2011