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

[Pharo-project] Help (perfect for newcomers) migrating a technical FAQ
by Mariano Martinez Peck April 10, 2011

April 10, 2011

Hi folks. I had a good idea and and it perfect for someone that wants to help and don't know how. It is not the most entertained task, but I promise you will learn a lot. Mostly, if you are newcomer. The idea is basically to migrate the FAQ that is here: http://scg.unibe.ch/wiki/faq/pharofaq to a new section in the collaborative Pharo book: http://book.pharo-project.org/ So....any takers ? Let us know so that we generate a new user in the Book The idea is also to check whether what is says is still correct for pharo or if it needs an update. Or even how to improve it (from the view of a newcomer). Thanks Mariano

2 4

Re: [Pharo-project] Issue 330 in pharo: recordLoop has bug that affects recording on macintosh
by pharo＠googlecode.com April 10, 2011

April 10, 2011

Updates: Status: FixProposed Labels: Milestone-1.3 Comment #7 on issue 330 by stephane...(a)gmail.com: recordLoop has bug that affects recording on macintosh http://code.google.com/p/pharo/issues/detail?id=330 (No comment was entered for this change.) Attachments: recordLoop.1.cs 1.0 KB

1 1

[Pharo-project] Issue 3789 in pharo: convert MenuMorph reference to invoke UIManager
by pharo＠googlecode.com April 10, 2011

April 10, 2011

Status: Accepted Owner: stephane...(a)gmail.com Labels: Milestone-1.3 New issue 3789 by stephane...(a)gmail.com: convert MenuMorph reference to invoke UIManager http://code.google.com/p/pharo/issues/detail?id=3789 subMenu := MenuMorph new defaultTarget: self. should be turned into subMenu := UIManager default newMenuIn: self for: self. newMenuIn: <owner> like a pane for example for: receiver of the menu actions. This is related to issue: 3728

1 5

Re: [Pharo-project] Issue 2559 in pharo: Senders of #ifNotNil: do not show
by pharo＠googlecode.com April 9, 2011

April 9, 2011

Comment #2 on issue 2559 by marcus.d...(a)gmail.com: Senders of #ifNotNil: do not show http://code.google.com/p/pharo/issues/detail?id=2559 Issue 2911 has been merged into this issue.

1 11

[Pharo-project] Issue 3849 in pharo: ExternalSettings should be cleaned
by pharo＠googlecode.com April 9, 2011

April 9, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com New issue 3849 by marcus.d...(a)gmail.com: ExternalSettings should be cleaned http://code.google.com/p/pharo/issues/detail?id=3849 When Issue 3638 is closed, MC will be the only client of ExternalSettings. ExternalSettings was a Preferences Framework that was only used by three clients: etoys, setting http proxy and MC. I vote for removing it.

1 3

[Pharo-project] Issue 3692 in pharo: Default line-end convention fix
by pharo＠googlecode.com April 9, 2011

April 9, 2011

Status: Accepted Owner: siguc...(a)gmail.com New issue 3692 by siguc...(a)gmail.com: Default line-end convention fix http://code.google.com/p/pharo/issues/detail?id=3692 Multibyte filestream guess about line endings was apparently wrong. Should use CR for MacOS and LF for rest unixes, not vise verse. Attachments: fix-line-ends.1.cs 678 bytes

1 7

[Pharo-project] Issue 3788 in pharo: Should fix all the menu category of ToolRegistry and deprecate the methods.
by pharo＠googlecode.com April 8, 2011

April 8, 2011

Status: Accepted Owner: siguc...(a)gmail.com Labels: Milestone-1.3 New issue 3788 by siguc...(a)gmail.com: Should fix all the menu category of ToolRegistry and deprecate the methods. http://code.google.com/p/pharo/issues/detail?id=3788 The category 'menu' is just for backward compatibility. The methods should be deprecated.

1 2

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

[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