- Pharo-dev - lists.pharo.org

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

by pharo＠googlecode.com

Comment #2 on issue 3461 by jannik.l...(a)gmail.com: [Failing Test] Tests.Release.ReleaseTest.testObsoleteClasses http://code.google.com/p/pharo/issues/detail?id=3461 same here. There is 14 entries in Undeclared

Jan. 21, 2011

Re: [Pharo-project] Issue 3489 in pharo: Pharo 1.2-dev still uses Preferences in BaseSoundSystem

by pharo＠googlecode.com

Comment #18 on issue 3489 by jannik.l...(a)gmail.com: Pharo 1.2-dev still uses Preferences in BaseSoundSystem http://code.google.com/p/pharo/issues/detail?id=3489 It is in a Slice-3489 in PharoInbox. But is integrated in pharo-dev. Should not be integrated in Pharo-Core.

Jan. 21, 2011

Re: [Pharo-project] Issue 3361 in pharo: CompiledMethod's copy

by pharo＠googlecode.com

Updates: Status: Closed Comment #4 on issue 3361 by stephane...(a)gmail.com: CompiledMethod's copy http://code.google.com/p/pharo/issues/detail?id=3361 (No comment was entered for this change.)

Jan. 21, 2011

[Pharo-project] [update 1.2] #12318

by Marcus Denker

12318 ----- Issue 3563: PCCByCompilationTest tests sometimes fail randomly (workaround) - fix the MC unload failure -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 21, 2011

Re: [Pharo-project] Issue 3361 in pharo: CompiledMethod's copy

by pharo＠googlecode.com

Comment #3 on issue 3361 by stephane...(a)gmail.com: CompiledMethod's copy http://code.google.com/p/pharo/issues/detail?id=3361 in 13010

Jan. 21, 2011

Re: [Pharo-project] Issue 2350 in pharo: Duration parsing nanos

by pharo＠googlecode.com

Updates: Status: Invalid Comment #2 on issue 2350 by npapoyl...(a)gmail.com: Duration parsing nanos http://code.google.com/p/pharo/issues/detail?id=2350 It doesn't seem to be a bug since in hh:mm:ss.[0-9]+ the part after the second actually denotes the fractional part of the second and NOT the number of nanoseconds. The code actually has a nanoseconds variable which is rather misleading but it actually does what it is supposed to do: From Time>>print24:showSeconds:on: [(s + (self nanoSecond / NanosInSecond) asFloat) printOn: aStream]]. Now for '4:02:55.520 pm' self nanoSecond returns 520000000, which does the right thing in the above computation. The only reason it is used that way is because in smalltalk the fractional part of a second has accuracy up to nanoseconds so: (Time readFrom: '4:02:55.99999999999999999999 pm' readStream) printString does correctly give: '4:02:55.999999999 pm' (fractional accuracy of nanoseconds) so do the examples above since 0.520 == 0.52

Jan. 21, 2011

Re: [Pharo-project] Issue 3489 in pharo: Pharo 1.2-dev still uses Preferences in BaseSoundSystem

by pharo＠googlecode.com

Updates: Status: Fixed Comment #17 on issue 3489 by jannik.l...(a)gmail.com: Pharo 1.2-dev still uses Preferences in BaseSoundSystem http://code.google.com/p/pharo/issues/detail?id=3489 fixed in a slice

Jan. 21, 2011

Re: [Pharo-project] Issue 3179 in pharo: Failing Tests for Monticello

by pharo＠googlecode.com

Comment #7 on issue 3179 by cy.delau...(a)gmail.com: Failing Tests for Monticello http://code.google.com/p/pharo/issues/detail?id=3179 I join a change set to fix the failing test in hudson Tests.Monticello.MCPackageTest.testUnload. To solve the problem, I added the following setUp method in MCPackageTest: setUp "here we have to make sure that there is no packae named Monticellomock left, so that no old package interfer with the test." MCWorkingCopy registry removeKey: (MCPackage new name: 'Monticellomocks') ifAbsent:[]. PackageOrganizer default unregisterPackageNamed: 'Monticellomocks'. Attachments: FixingMonticelloTestFailingInHudson.1.cs 1.5 KB

Jan. 21, 2011

[Pharo-project] Adding settings to an existing group

by Henrik Sperre Johansen

Sorry I haven't really had time to learn the settings framework yet, does anyone know how to do this? Updating the Sound package, I'd like to add a few to the existing category Appearance -> sound (strange place for it, btw...) in a package one can load from the repository. I tried code like: quickStartSoundSettingOn: aBuilder <systemsettings> (aBuilder group: #appearance) with: [ (aBuilder setting: #soundEnabled) with: [ (aBuilder setting: #soundQuickStart) label: 'Play sounds immediately if possible'; target: SoundPlayer; targetSelector: #soundQuickStart]] but that's apparently far off the mark... Cheers, Henry

Jan. 21, 2011

Re: [Pharo-project] Issue 3489 in pharo: Pharo 1.2-dev still uses Preferences in BaseSoundSystem

by pharo＠googlecode.com

Updates: Blockedon: 3566 Comment #16 on issue 3489 by ryd...(a)gmail.com: Pharo 1.2-dev still uses Preferences in BaseSoundSystem http://code.google.com/p/pharo/issues/detail?id=3489 (No comment was entered for this change.)

Jan. 21, 2011