December 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3454 in pharo: DNU when looking for implementors in OB on 1.2dev

by pharo＠googlecode.com

Comment #4 on issue 3454 by luc.fabresse: DNU when looking for implementors in OB on 1.2dev http://code.google.com/p/pharo/issues/detail?id=3454 Concerning the 4 failing tests. The running test case OBKeyBindingsTest register itself as the model of a OBPluggableTextMorph to check if it receives the callback messages (implementorsOfIt:, ...) when a shortcut is pressed. And it didn't. Events seem to propagate well but at the end the callback messages are sent to a SmalltalkEditor not the model. Not sure it is clear ;-) To sum up, probably there is something wrong with event management.

Dec. 20, 2010

Re: [Pharo-project] Issue 3466 in pharo: Display the leading zero while printing the hexadecimal version of a Character

by pharo＠googlecode.com

Comment #1 on issue 3466 by geo.couprie: Display the leading zero while printing the hexadecimal version of a Character http://code.google.com/p/pharo/issues/detail?id=3466 Fix in PharoInbox: SLICE-Issue-3466-Display-the-leading-zero-while-printing-the-hexadecimal-version-of-a-Character-GeoffroyCouprie.1.mcz

Dec. 20, 2010

[Pharo-project] Issue 3466 in pharo: Display the leading zero while printing the hexadecimal version of a Character

by pharo＠googlecode.com

Status: New Owner: ---- New issue 3466 by geo.couprie: Display the leading zero while printing the hexadecimal version of a Character http://code.google.com/p/pharo/issues/detail?id=3466 Pharo image: Pharo | Pharo-core Pharo core version: Pharo1.2beta Virtual machine used: pharo-vm-4.0.2-win32 Steps to reproduce: 1.(Character value:15) printStringHex -> 'F' it should return '0F'. Character>>hex returns '16rF' and should not be fixed, but printStringHex must display the leading zero, because the smallest representation of a Character is a byte. Additionally, String>>asHex should use Character>>printStringHex instead of Character>>hex.

Dec. 20, 2010

Re: [Pharo-project] Issue 3454 in pharo: DNU when looking for implementors in OB on 1.2dev

by pharo＠googlecode.com

Comment #3 on issue 3454 by luc.fabresse: DNU when looking for implementors in OB on 1.2dev http://code.google.com/p/pharo/issues/detail?id=3454 I don't think that it is related. If I modify like that: OBTextMorphEditorWithShout>>send: aSelector toModelWith: args orDo: aBlock "self terminateAndInitializeAround: <--- COMMENTED BECAUSE DNU" [(model respondsTo: aSelector) ifTrue: [(model perform: aSelector withArguments: args) ifFalse: [self flash]] ifFalse: [aBlock value]] value it works! I can show implementors with cmd-m ... without any error but the 4 tests on OB are still yellow.

Dec. 20, 2010

[Pharo-project] Issue 3465 in pharo: Hundson OneClick: Does not show Mac menues

by pharo＠googlecode.com

Status: Accepted Owner: marcus.denker Labels: Milestone-1.2-DevImage New issue 3465 by marcus.denker: Hundson OneClick: Does not show Mac menues http://code.google.com/p/pharo/issues/detail?id=3465 The Hundson OneClick does not show Mac menues.

Dec. 20, 2010

Re: [Pharo-project] Issue 3205 in pharo: monticello's error on Linux

by pharo＠googlecode.com

Comment #2 on issue 3205 by sanchezlsp: monticello's error on Linux http://code.google.com/p/pharo/issues/detail?id=3205 Thank you. That works.

Dec. 20, 2010

Re: [Pharo-project] Issue 3462 in pharo: [Failing Test] SHParserST80Test.testNumbers

by pharo＠googlecode.com

Updates: Summary: [Failing Test] SHParserST80Test.testNumbers Comment #1 on issue 3462 by marcus.denker: [Failing Test] SHParserST80Test.testNumbers http://code.google.com/p/pharo/issues/detail?id=3462 (No comment was entered for this change.)

Dec. 20, 2010

Re: [Pharo-project] Issue 3463 in pharo: [Failing Test] HelpBrowserTest.testOpen

by pharo＠googlecode.com

Updates: Summary: [Failing Test] HelpBrowserTest.testOpen Comment #1 on issue 3463 by marcus.denker: [Failing Test] HelpBrowserTest.testOpen http://code.google.com/p/pharo/issues/detail?id=3463 (No comment was entered for this change.)

Dec. 20, 2010

Re: [Pharo-project] Issue 3464 in pharo: [Failing Test] ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory

by pharo＠googlecode.com

Updates: Summary: [Failing Test] ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory Comment #1 on issue 3464 by marcus.denker: [Failing Test] ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory http://code.google.com/p/pharo/issues/detail?id=3464 (No comment was entered for this change.)

Dec. 20, 2010

[Pharo-project] Issue 3464 in pharo: [Failing Test] Tests.Release.ReleaseTest.testObsoleteClasses

by pharo＠googlecode.com

Status: Accepted Owner: marcus.denker Labels: Milestone-1.2-DevImage New issue 3464 by marcus.denker: [Failing Test] Tests.Release.ReleaseTest.testObsoleteClasses http://code.google.com/p/pharo/issues/detail?id=3464 MethodWrappers.Tests.ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory

Dec. 20, 2010