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

[Pharo-project] [COTDC] 44 - ColorChanged
by laurent laffont April 8, 2011

April 8, 2011

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

1 1

[Pharo-project] RPackage not updated when adding a category
by Cyrille Delaunay April 8, 2011

April 8, 2011

This is maybe related to SystemOrganizer>>addCategory:before: which seems to never notify that a category has been added (whereas SystemOrganizer>>addCategory: does it). I opened an issue : http://code.google.com/p/pharo/issues/detail?id=3974

1 0

[Pharo-project] Issue 3974 in pharo: [RPackage] rpackage do not update when adding a category
by pharo＠googlecode.com April 8, 2011

April 8, 2011

Status: Accepted Owner: cy.delau...(a)gmail.com New issue 3974 by cy.delau...(a)gmail.com: [RPackage] rpackage do not update when adding a category http://code.google.com/p/pharo/issues/detail?id=3974 In a 1.3 image, When I add a category to the default browser, RPackage is not updated accordingly, it does not register the new package. Adding a category in the default browser will send addCategory:before: to SystemOrganizer , which never emit any event (contrary to SystemOrganizer>>addCategory:). Therefore RPackage is never aware of any change. Should add a notification in SystemOrganizer>>addCategory?

1 0

[Pharo-project] Issue 3544 in pharo: Rename Morphic-Themes into Themes
by pharo＠googlecode.com April 8, 2011

April 8, 2011

Status: Accepted Owner: stephane...(a)gmail.com Labels: Milestone-1.2 New issue 3544 by stephane...(a)gmail.com: Rename Morphic-Themes into Themes http://code.google.com/p/pharo/issues/detail?id=3544 we should rename the Morphic-Themes package into what: Themes?

1 3

[Pharo-project] [update 1.3] #13136
by Marcus Denker April 8, 2011

April 8, 2011

13136 ----- Issue 3969: MorphTreeMorph performance Issue 3870: [Failing Test] 1.3 KernelTests.Methods.CompiledMethodTest.testNew -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3940 in pharo: BlockNode has undeclared ivar optimizedMessageNode
by pharo＠googlecode.com April 8, 2011

April 8, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3940 by marcus.d...(a)gmail.com: BlockNode has undeclared ivar optimizedMessageNode http://code.google.com/p/pharo/issues/detail?id=3940 accessed in noteOptimizedIn: analyseTempsWithin: scopeBlock "<BlockNode>" rootNode: rootNode "<MethodNode>" assignmentPools: assignmentPools

1 3

[Pharo-project] Issue 3870 in pharo: [Failing Test] 1.3 KernelTests.Methods.CompiledMethodTest.testNew
by pharo＠googlecode.com April 8, 2011

April 8, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3870 by marcus.d...(a)gmail.com: [Failing Test] 1.3 KernelTests.Methods.CompiledMethodTest.testNew http://code.google.com/p/pharo/issues/detail?id=3870 >>> KernelTests.Methods.CompiledMethodTest.testNew 0.0 1

1 5

Re: [Pharo-project] Issue 3969 in pharo: MorphTreeMorph performance
by pharo＠googlecode.com April 8, 2011

April 8, 2011

Updates: Status: FixProposed Comment #3 on issue 3969 by marcus.d...(a)gmail.com: MorphTreeMorph performance http://code.google.com/p/pharo/issues/detail?id=3969 (No comment was entered for this change.)

1 2

April 8, 2011

Hi guys here is a new version of the metacello chapter. So we wrote it, rewrote it, rerewrote it. Now if this is of interest for you you can read it. But if you don't it means that I'm losing my time and I should stop writing and like that you can cry that there is no doc about Pharo. Stef

8 20

[Pharo-project] A step toward reducing complexity
by DougEdmunds April 8, 2011

April 8, 2011

Reduce the complexity of user interface themes In general, user interface themes should inherit directly from UITheme, not from a chain of themes. When you have a chain of themes, you are stuck with the intermediate themes, whether you need/use them or not. Consider GLMUITheme. Currently it is under UIThemeWatery2, which is under UIThemeWatery, which is under UITheme. Some characteristics inherited from the chain are missing, but in principal, GLMUITheme can be moved directly under UITheme with just 3 changes. 1. Add an instanceVariable 'windowActiveDropShadowStyle' UITheme subclass: #GLMUITheme instanceVariableNames: 'windowActiveDropShadowStyle' classVariableNames: '' poolDictionaries: '' category: 'Glamour-Morphic-Theme' 2. Add a class method isAbstract "Answer whether the receiver is considered to be abstract." ^false 3. Add an instance method windowActiveDropShadowStyle: anObject "Set the value of windowActiveDropShadowStyle" windowActiveDropShadowStyle := anObject Because GLMOrangeUITheme inherits these changes, it does not need modification. -- View this message in context: http://forum.world.st/A-step-toward-reducing-complexity-tp3404504p3404504.h… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

4 10