- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Getting a functionning unstable image

by Igor Stasenko

On 22 March 2011 13:28, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Mar 22, 2011, at 1:25 PM, StÃ©phane Ducasse wrote: > >> +1 >> >> Now condenses change should work too :) >> > > I am slowly adopting a radical "if we don't test it, it's will brake" point of view. > I now even say: If we don't test it, it *should* be broken! Because it is dead > code and should be removed. > I like a systematic approach. :) > Â Â Â Â Marcus > > -- Best regards, Igor Stasenko AKA sig.

March 22, 2011

Re: [Pharo-project] [COTDC] 34 - MCSystemCategoryParser -- help needed, seriously

by laurent laffont

On Tue, Mar 22, 2011 at 6:33 PM, Miguel CobÃ¡ <miguel.coba(a)gmail.com> wrote: > Hi Laurent, > > maybe instead of random picking a class it would be better to random > picking a category and to document all the classes in that category. > That way the knowledge gained from understanding a simple class can be > re-used to document the other classes in the package (as they are very > related) > I think that by choosing a new class from a different package each day > this knowledge is lost or at least not leveraged at its full. > > What do you think? > I will try to pick related classes for one week to see (indeed today it's Monticello related too). Laurent. > > El mar, 22-03-2011 a las 18:14 +0100, laurent laffont escribiÃ³: > > > > On Tue, Mar 22, 2011 at 1:23 PM, StÃ©phane Ducasse > > <stephane.ducasse(a)inria.fr> wrote: > > continue > > please continue > > > > > > OK I will change the process a little. > > > > One COTDC per day. If no or not satisfying comment I will not put it > > in results. > > > > So I abort this one. > > > > Laurent. > > > > > > > > Stef > > > > On Mar 22, 2011, at 8:14 AM, laurent laffont wrote: > > > > > Hi people, > > > > > > almost no participation in COTDC last days. > > > > > > I'm not a Smalltalk guru and even 30mn to look at code is > > sometimes not enough for me to understand some stuff alone. > > > > > > I like COTDC because of > > http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > ==> documentation. > > > > > > But quality / good comment is needed and there's ~600 > > classes without comment remaining. So if we want a 100% good > > commented Pharo in 2 years from now, we should do it every > > day. > > > > > > Laurent Laffont > > > > > > On Mon, Mar 21, 2011 at 8:36 PM, laurent laffont > > <laurent.laffont(a)gmail.com> wrote: > > > Could it be: > > > > > > I parse PackageInfo statement from Monticello packages file. > > > > > > Laurent. > > > > > > > > > > > > On Mon, Mar 21, 2011 at 8:02 AM, laurent laffont > > <laurent.laffont(a)gmail.com> wrote: > > > Today: MCSystemCategoryParser > > > > > > > > > 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 > > > > > > > > > > > > > > > > -- > Miguel CobÃ¡ > http://twitter.com/MiguelCobaMtz > http://miguel.leugim.com.mx > > > > >

March 22, 2011

Re: [Pharo-project] [COTDC] 34#2 - MCStWriter

by laurent laffont

On Tue, Mar 22, 2011 at 6:20 PM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > Today: MCStWriter > I write Category/Classes/Methods/.... definitions into Monticello source.stfile format found in .mcz packages. Example: String streamContents: [:aStream| |writer| writer := MCStWriter on: aStream. writer writeDefinitions: {True asClassDefinition. False asClassDefinition}. ] 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 >

March 22, 2011

Re: [Pharo-project] [COTDC] 34 - MCSystemCategoryParser -- help needed, seriously

by Miguel CobÃ¡

Hi Laurent, maybe instead of random picking a class it would be better to random picking a category and to document all the classes in that category. That way the knowledge gained from understanding a simple class can be re-used to document the other classes in the package (as they are very related) I think that by choosing a new class from a different package each day this knowledge is lost or at least not leveraged at its full. What do you think? El mar, 22-03-2011 a las 18:14 +0100, laurent laffont escribiÃ³: > > On Tue, Mar 22, 2011 at 1:23 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: > continue > please continue > > > OK I will change the process a little. > > One COTDC per day. If no or not satisfying comment I will not put it > in results. > > So I abort this one. > > Laurent. > > > > Stef > > On Mar 22, 2011, at 8:14 AM, laurent laffont wrote: > > > Hi people, > > > > almost no participation in COTDC last days. > > > > I'm not a Smalltalk guru and even 30mn to look at code is > sometimes not enough for me to understand some stuff alone. > > > > I like COTDC because of > http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > ==> documentation. > > > > But quality / good comment is needed and there's ~600 > classes without comment remaining. So if we want a 100% good > commented Pharo in 2 years from now, we should do it every > day. > > > > Laurent Laffont > > > > On Mon, Mar 21, 2011 at 8:36 PM, laurent laffont > <laurent.laffont(a)gmail.com> wrote: > > Could it be: > > > > I parse PackageInfo statement from Monticello packages file. > > > > Laurent. > > > > > > > > On Mon, Mar 21, 2011 at 8:02 AM, laurent laffont > <laurent.laffont(a)gmail.com> wrote: > > Today: MCSystemCategoryParser > > > > > > 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 > > > > > > > > -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

March 22, 2011

Re: [Pharo-project] Issue 3843 in pharo: isHealthy for HasedCollection

by pharo＠googlecode.com

Comment #4 on issue 3843 by ryd...(a)gmail.com: isHealthy for HasedCollection http://code.google.com/p/pharo/issues/detail?id=3843 Looks to me like something which belongs in the Testing trait for UnorderedCollections rather than in the UnorderedCollections themselves. (Collection testa were rewritten to use traits right, I'm not remembering incorrectly?)

March 22, 2011

[Pharo-project] [COTDC] 34#2 - MCStWriter

by laurent laffont

Today: MCStWriter 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

March 22, 2011

Re: [Pharo-project] [COTDC] 34 - MCSystemCategoryParser -- help needed, seriously

by laurent laffont

On Tue, Mar 22, 2011 at 1:23 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > continue > please continue > > OK I will change the process a little. One COTDC per day. If no or not satisfying comment I will not put it in results. So I abort this one. Laurent. > > Stef > On Mar 22, 2011, at 8:14 AM, laurent laffont wrote: > > > Hi people, > > > > almost no participation in COTDC last days. > > > > I'm not a Smalltalk guru and even 30mn to look at code is sometimes not > enough for me to understand some stuff alone. > > > > I like COTDC because of > http://code.google.com/p/pharo/wiki/CommentOfTheDayContest ==> > documentation. > > > > But quality / good comment is needed and there's ~600 classes without > comment remaining. So if we want a 100% good commented Pharo in 2 years from > now, we should do it every day. > > > > Laurent Laffont > > > > On Mon, Mar 21, 2011 at 8:36 PM, laurent laffont < > laurent.laffont(a)gmail.com> wrote: > > Could it be: > > > > I parse PackageInfo statement from Monticello packages file. > > > > Laurent. > > > > > > > > On Mon, Mar 21, 2011 at 8:02 AM, laurent laffont < > laurent.laffont(a)gmail.com> wrote: > > Today: MCSystemCategoryParser > > > > > > 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 > > > > > > >

March 22, 2011

Re: [Pharo-project] Issue 2672 in pharo: Remove UpdatingXXXMorph ....

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.3 Comment #3 on issue 2672 by marcus.d...(a)gmail.com: Remove UpdatingXXXMorph .... http://code.google.com/p/pharo/issues/detail?id=2672 (No comment was entered for this change.)

March 22, 2011

Re: [Pharo-project] Issue 2543 in pharo: RealEstateAgent should be cleaned

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.3 Comment #2 on issue 2543 by marcus.d...(a)gmail.com: RealEstateAgent should be cleaned http://code.google.com/p/pharo/issues/detail?id=2543 (No comment was entered for this change.)

March 22, 2011

Re: [Pharo-project] Issue 3840 in pharo: ivar errorHandler in Process seems to be unused

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3840 by marcus.d...(a)gmail.com: ivar errorHandler in Process seems to be unused http://code.google.com/p/pharo/issues/detail?id=3840 in 13103

March 22, 2011