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

Re: [Pharo-project] Issue 3447 in pharo: Do we need to menu entry "Shout Workspace"?

by pharo＠googlecode.com

Comment #3 on issue 3447 by guillermopolito: Do we need to menu entry "Shout Workspace"? http://code.google.com/p/pharo/issues/detail?id=3447 Why not removing that method from scratch?

Dec. 20, 2010

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

by pharo＠googlecode.com

Comment #1 on issue 3461 by guillermopolito: [Failing Test] Tests.Release.ReleaseTest.testObsoleteClasses http://code.google.com/p/pharo/issues/detail?id=3461 I cannot reproduce it with the last dev image from hudson :S... In my image #testUndeclared is failing instead of that.... Can someone check it?

Dec. 20, 2010

Re: [Pharo-project] Issue 3460 in pharo: [Failing Test] ToolsTest.Inspector.WeakSetInspectorTest.testSymbolTableM6812

by pharo＠googlecode.com

Updates: Status: WontFix Comment #2 on issue 3460 by guillermopolito: [Failing Test] ToolsTest.Inspector.WeakSetInspectorTest.testSymbolTableM6812 http://code.google.com/p/pharo/issues/detail?id=3460 It's Ok with the normal inspector :). It was a NewInspector issue.

Dec. 20, 2010

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

by pharo＠googlecode.com

Comment #3 on issue 3463 by guillermopolito: [Failing Test] HelpBrowserTest.testOpen http://code.google.com/p/pharo/issues/detail?id=3463 The config isn't referencing ConfigurationOfPharo.. It's breaking while doing #prepareDebuggerExample with a InMidstOfFileinNotification I don't quite understand why...

Dec. 20, 2010

Re: [Pharo-project] Printing hexadecimal values of a string

by Max Leske

Hi Stef Sorry, I should have been more specific. This is a method I use in my own application. I'm not sure if I did test the method but I could have a look if you like. Max On 20.12.2010, at 09:11, StÃ©phane Ducasse wrote: > max on which class do you define it? > > do you have some tests? > > Stef > > On Dec 19, 2010, at 11:40 PM, Max Leske wrote: > >> I know how your feel. My code: >> >> hexHashFrom: aByteString >> "#hex will omit a leading 0. If that's the case insert leading 0." >> ^aByteString asByteArray hex asLowercase forceTo: 40 paddingStartWith: $0 >> >> Max >> >> >> On 19.12.2010, at 22:54, Sven Van Caekenberghe wrote: >> >>> Hi Geoffroy, >>> >>> On 19 Dec 2010, at 21:55, Geoffroy Couprie wrote: >>> >>>> Hello all, >>>> >>>> I get a strange behaviour while trying to print hexadecimal values of a string. >>>> >>>> Context: I get a SHA1 hash from a binary stream, store it into a >>>> string, and I want to display that string (using asHex). >>>> >>>> Problem: for values inferior to 16, the leading zero is ignored. (15 >>>> -> 'F' instead of '0F'). >>>> >>>> I could modify SmallInteger>>printStringBase: to always include the >>>> leading zero, but I fear I'm going to break a lot of code doing that. >>>> Is there a better way to fix my problem? apart from using directly the >>>> following: >>>> aStream do:[:val | val printStringBase:16 nDigits:2] >>>> >>>> Best regards, >>>> >>>> Geoffroy >>> >>> Why would you not use the ByteArray>>#hex method ? >>> >>> #(0 1 2 253 254 255) asByteArray hex >>> >>> '000102fdfeff' >>> >>> Sven >>> >>> >> >> > >

Dec. 20, 2010

Re: [Pharo-project] Issue 3460 in pharo: [Failing Test] ToolsTest.Inspector.WeakSetInspectorTest.testSymbolTableM6812

by pharo＠googlecode.com

Comment #1 on issue 3460 by guillermopolito: [Failing Test] ToolsTest.Inspector.WeakSetInspectorTest.testSymbolTableM6812 http://code.google.com/p/pharo/issues/detail?id=3460 It relies on NewInspector. I'll try with an image without it.

Dec. 20, 2010

Re: [Pharo-project] Issue 3410 in pharo: Remove NEwInspector from Dev

by pharo＠googlecode.com

Updates: Status: Fixed Comment #3 on issue 3410 by guillermopolito: Remove NEwInspector from Dev http://code.google.com/p/pharo/issues/detail?id=3410 Done :)

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 #6 on issue 3454 by guillermopolito: DNU when looking for implementors in OB on 1.2dev http://code.google.com/p/pharo/issues/detail?id=3454 I mean, SmalltalkEditor does not use it.

Dec. 20, 2010

Re: [Pharo-project] 1.2 Dev and Hudson

by Guillermo Polito

Great! We have to be careful since #lastVersion seems to be deprecated, to use #bleedingEdge or something else I don't know... Maybe it's just fine to rely on it by now. On Mon, Dec 20, 2010 at 5:55 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On Dec 20, 2010, at 9:41 AM, Marcus Denker wrote: > > > On Dec 20, 2010, at 9:31 AM, Mariano Martinez Peck wrote: > > Yes, as Guille said, using #lastVersion would be more interesting here: > > "Dev image" > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfPharo'; > load. > > ((Smalltalk at: #ConfigurationOfPharo) project lastVersion) perform: > #silently: with: true; perform: #load. > > > I will put that in. > > > Done. next build will use that. > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

Dec. 20, 2010

Re: [Pharo-project] Are we tagging 1.2 dev issues?

by Guillermo Polito

Reviewing issues... :) On Mon, Dec 20, 2010 at 7:20 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On Dec 20, 2010, at 8:38 AM, Marcus Denker wrote: > > > On Dec 20, 2010, at 4:27 AM, Guillermo Polito wrote: > > I found only 5 in the issue tracker, hehe. Maybe those are the only > reported by now, maybe not. > > I added tracker entries for all failing tests that are not yet entries for > 1.2Core: > > > http://code.google.com/p/pharo/issues/list?cursor=3462&q=milestone%3D1.2-De… > > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

Dec. 20, 2010