- Pharo-dev - lists.pharo.org

[Pharo-project] Adding settings to an existing group
by Henrik Sperre Johansen Jan. 21, 2011

Jan. 21, 2011

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

3 3

[Pharo-project] Issue 3501 in pharo: Remove 1.1 deprecated methods and publish them in a separate package
by pharo＠googlecode.com Jan. 21, 2011

Jan. 21, 2011

Status: Fixed Owner: stephane.ducasse Labels: Milestone-1.3 New issue 3501 by stephane.ducasse: Remove 1.1 deprecated methods and publish them in a separate package http://code.google.com/p/pharo/issues/detail?id=3501 1.1 deprecated methods should be packaged in a separate package and unloaded from 1.3

1 5

[Pharo-project] [update 1.3] #13013
by StÃ©phane Ducasse Jan. 21, 2011

Jan. 21, 2011

13013 ----- - Categorization of deprecated methods.

1 0

[Pharo-project] Issue 3440 in pharo: Cycle in Monticello removed
by pharo＠googlecode.com Jan. 21, 2011

Jan. 21, 2011

Status: Accepted Owner: alexandre.bergel CC: stephane.ducasse Labels: Difficulty-Easy New issue 3440 by alexandre.bergel: Cycle in Monticello removed http://code.google.com/p/pharo/issues/detail?id=3440 A cycle is due to a dependency of Monticello-Chunk Format to Monticello-Storing. Monticello-FelipeValverde.472 in the inBox fixes this. DSM was used for this. Result of the CC68S lecture

1 4

[Pharo-project] OB failing tests in Pharo 1.2
by Mariano Martinez Peck Jan. 21, 2011

Jan. 21, 2011

Hi Lukas. I was checking the 4 failing tests in Pharo 1.2: http://code.google.com/p/pharo/issues/detail?id=3470 The problem seems related to the changes with the SmalltalkEditor/ParagraphEditor and friends. The tests fails because the instVar "message" is nil, because nobody call OBKeyBindingsTest >> browseIt: aSelector nor its friends. This was called in Pharo 1.1 from OBTextMorphEditor because it was a subclass of ParagraphEditor. Now, I have no idea how to make it work in Pharo 1.2 Cheers mariano

3 3

Re: [Pharo-project] Issue 1487 in pharo: DateAndTime/TimeStamp can't handle times with nanoseconds
by pharo＠googlecode.com Jan. 21, 2011

Jan. 21, 2011

Updates: Status: Invalid Comment #3 on issue 1487 by npapoyl...(a)gmail.com: DateAndTime/TimeStamp can't handle times with nanoseconds http://code.google.com/p/pharo/issues/detail?id=1487 DateAndTime and subclasses simply do not deal with nanoseconds, the above code does not fail, but does not take the nanoseconds into account either. This seems to be intented.

1 0

[Pharo-project] Issue 3361 in pharo: CompiledMethod's copy
by pharo＠googlecode.com Jan. 21, 2011

Jan. 21, 2011

Status: Accepted Owner: gbarbuto New issue 3361 by gbarbuto: CompiledMethod's copy http://code.google.com/p/pharo/issues/detail?id=3361 Pharo image: core Pharo core version: Pharo1.2a Latest update: #12264 Virtual machine used: <any Steps to reproduce: 1. Try to completely copy a CompiledMethod and the copy still have references to the original CompiledMethod.

1 4

[Pharo-project] [update 1.2] #12318
by Marcus Denker Jan. 21, 2011

Jan. 21, 2011

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.

1 0

Re: [Pharo-project] Issue 2350 in pharo: Duration parsing nanos
by pharo＠googlecode.com Jan. 21, 2011

Jan. 21, 2011

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

1 0

Re: [Pharo-project] Issue 3566 in pharo: Changes needed to update Sound for 1.2
by pharo＠googlecode.com Jan. 21, 2011

Jan. 21, 2011

Issue 3566: Changes needed to update Sound for 1.2 http://code.google.com/p/pharo/issues/detail?id=3566 This issue is now blocking issue 3489. See http://code.google.com/p/pharo/issues/detail?id=3489 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0