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

Re: [Pharo-project] [COTDC] 34 - MCSystemCategoryParser -- help needed, seriously
by laurent laffont March 22, 2011

March 22, 2011

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 >> > >

3 4

[Pharo-project] Issue 3843 in pharo: isHealthy for HasedCollection
by pharo＠googlecode.com March 22, 2011

March 22, 2011

Status: Accepted Owner: stephane...(a)gmail.com New issue 3843 by stephane...(a)gmail.com: isHealthy for HasedCollection http://code.google.com/p/pharo/issues/detail?id=3843 Some integrity checks for Dictionary and friends Attachments: HashedCollection-IntegrityCheck.2.cs 10.0 KB

1 4

Re: [Pharo-project] Issue 2672 in pharo: Remove UpdatingXXXMorph ....
by pharo＠googlecode.com March 22, 2011

March 22, 2011

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.)

1 0

Re: [Pharo-project] Issue 2543 in pharo: RealEstateAgent should be cleaned
by pharo＠googlecode.com March 22, 2011

March 22, 2011

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.)

1 0

[Pharo-project] Issue 3840 in pharo: ivar errorHandler in Process seems to be unused
by pharo＠googlecode.com March 22, 2011

March 22, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com New 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 errorHandler has just accessors. These are not sent in core.

1 2

[Pharo-project] [update 1.3] #13103
by Marcus Denker March 22, 2011

March 22, 2011

13103 ----- Issue 3821: makeStrong/makeWeak contains a bug Issue 3843: isHealthy for HasedCollection Issue 3840: ivar errorHandler in Process seems to be unused -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3821 in pharo: makeStrong/makeWeak contains a bug
by pharo＠googlecode.com March 22, 2011

March 22, 2011

Status: Accepted Owner: stephane...(a)gmail.com CC: siguc...(a)gmail.com, ryd...(a)gmail.com Labels: Milestone-1.3 New issue 3821 by stephane...(a)gmail.com: makeStrong/makeWeak contains a bug http://code.google.com/p/pharo/issues/detail?id=3821 makeStrong/makeWeak contains a bug, because it is using #becomeForward: but doesn't takes into account that subscription stored in a set , which is hash-based , so after become, the item will be at wrong position. So, we need to implement announcer>>replace: subscription with: newOne then a) we don't have to use become b) it will be thread safe, because you can protect replacement in subscription registry with monitor As an alternative, we can use Set instead of IdentitySet, and implement #hash and #== for subscriptions which don't changing when you switch between weak/strong. Then we can keep using #becomeForward: -- Best regards, Igor Stasenko AKA sig.

1 2

[Pharo-project] Issue 3339 in pharo: WeakOrderedCollection
by pharo＠googlecode.com March 22, 2011

March 22, 2011

Status: Accepted Owner: stephane.ducasse Labels: Milestone-1.3 New issue 3339 by stephane.ducasse: WeakOrderedCollection http://code.google.com/p/pharo/issues/detail?id=3339 Squeak got weak ordered collection and we could want to have that too.

2 2

[Pharo-project] Do you have a tool that works on Pharo ?
by Mariano Martinez Peck March 22, 2011

March 22, 2011

ifTrue: [ self writeOnPharoBook: aTool] We need to improve our documentation. Right now, we have a collaborative book where everyone can join and write: http://book.pharo-project.org/ Here we have a list of tools that run on Pharo: http://book.pharo-project.org/book/PharoTools and it is REALLY important to have such list updated and maintained. So, if you have a tool that works in pharo and it is not there, please add it. If you don't have a user, I can create one for you. If you are TOO lazy, you can send by email the text to me and I write it. Thanks Mariano

7 12

[Pharo-project] Inspector in 1.2
by AxiNat March 22, 2011

March 22, 2011

Hi list, First of all, I'd like to apologise just in case this is already a known issue; I checked and couldn't find it around. I've started working with 1.2 RC a couple days ago, and I noticed the inspector went back to (IIRC) several releases ago. In 1.1 we had tree navigation and were able to run code in context, now you must open a new inspector for each node and the code is always executed from the scope of the root object. I've also noticed you can't remove items from a collection straight from the UI anymore. Thanks! Bernat Romagosa.

3 5