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

Re: [Pharo-project] Issue 3566 in pharo: Changes needed to update Sound for 1.2

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.2-DevImage Milestone-1.2 Milestone-1.3 Comment #6 on issue 3566 by ryd...(a)gmail.com: Changes needed to update Sound for 1.2 http://code.google.com/p/pharo/issues/detail?id=3566 These are core changes needed for the external package, not DevImage specific changes.

Jan. 21, 2011

Re: [Pharo-project] Adding settings to an existing group

by Alain Plantec

----------------- quickStartSoundSettingOn: aBuilder <systemsettings> (aBuilder setting: #soundQuickStart) parent: #soundEnabled; label: 'Play sounds immediately if possible' translated; target: SoundPlayer -------------- should do it if you have SoundPlayer class>>soundQuickStart SoundPlayer class>>soundQuickStart: aBoolean btw: why this setting ? If sound is enabled, why would I set this setting to false ? I guess one always want the sound to start as quick as possible. Cheers Alain Le 21/01/2011 16:06, Henrik Sperre Johansen a Ã©crit : > 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 3440 in pharo: Cycle in Monticello removed

by pharo＠googlecode.com

Updates: Status: Closed Comment #4 on issue 3440 by stephane...(a)gmail.com: Cycle in Monticello removed http://code.google.com/p/pharo/issues/detail?id=3440 integrated in 13012

Jan. 21, 2011

Re: [Pharo-project] OB failing tests in Pharo 1.2

by Lukas Renggli

On Friday, 21 January 2011, Tudor Girba <tudor.girba(a)gmail.com> wrote: > That is not very encouraging :) Indeed. Probably somebody can figure out a patch that fixes some more of the regressions. But this will never fix the problem that the code builds on top of the old infrastructure delegating to the new infrastructure. Some time ago I started to reimplement the OB editor on top of the new editor, but that is just the first day of work of the estimated week: source.lukas-renggli.ch/pharo12. Lukas > > Cheers, > Doru > > > On 21 Jan 2011, at 15:43, Lukas Renggli wrote: > >>> 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 >> >> Yeah, me neither. OB-Morphic is totally broken and it cannot be >> quickly fixed. The editor support has to be completely rewritten on >> top of the new infrastructure to get a browser that properly works. >> >> Lukas >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> > > -- > www.tudorgirba.com > > "Next time you see your life passing by, say 'hi' and get to know her." > > > > > -- Lukas Renggli www.lukas-renggli.ch

Jan. 21, 2011

Re: [Pharo-project] Issue 3440 in pharo: Cycle in Monticello removed

by pharo＠googlecode.com

Comment #3 on issue 3440 by stephane...(a)gmail.com: Cycle in Monticello removed http://code.google.com/p/pharo/issues/detail?id=3440 the version you used does not contain the changes made in October!!!!! Please always used the latest version to propose fix

Jan. 21, 2011

Re: [Pharo-project] Reminder: change the archiving tool

by Miguel CobÃ¡

El vie, 21-01-2011 a las 13:59 +0100, Igor Stasenko escribiÃ³: > All .zip files with pharo images having an annoying Apple-ism - a > .DS_Store garbage file. > Please use a zip archiver which includes only relevant files to > archive, because obviously this garbage has no use anywhere but Macs. > +1 -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

Jan. 21, 2011

Re: [Pharo-project] OB failing tests in Pharo 1.2

by Tudor Girba

That is not very encouraging :) Cheers, Doru On 21 Jan 2011, at 15:43, Lukas Renggli wrote: >> 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 > > Yeah, me neither. OB-Morphic is totally broken and it cannot be > quickly fixed. The editor support has to be completely rewritten on > top of the new infrastructure to get a browser that properly works. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > -- www.tudorgirba.com "Next time you see your life passing by, say 'hi' and get to know her."

Jan. 21, 2011

Re: [Pharo-project] Gofer issue

by Miguel CobÃ¡

El vie, 21-01-2011 a las 11:05 +0100, Igor Stasenko escribiÃ³: > Okay, i found the solution. Use Installer ! > > Installer monticello http: 'http://www.squeaksource.com'; > project: 'VMMaker'; > install: 'CMakeVMMaker' > > > works well for me and loads correct *latest* version. That isn't a solution and open again a gratuitous discussion about gofer vs installer. The point is, in a distributed SCM system, like Monticello is, there isn't a latest version. At least not by the traditional (suversion for example) way of knowing the monotone numeric integer version number. As Lukas said, the only way to know something is latest is to compare timestamps, but not version numbers or commits id. They aren't not intended to be ordered respect to time. Cheers -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

Jan. 21, 2011

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

by pharo＠googlecode.com

Updates: Status: Fixed Labels: -Milestone-1.2 Comment #8 on issue 3179 by marcus.d...(a)gmail.com: Failing Tests for Monticello http://code.google.com/p/pharo/issues/detail?id=3179 I added it to 1.2... TODO: add FixingMonticelloTestFailingInHudson.1.cs to 1.3 (and on close tag this report 1.2 again)

Jan. 21, 2011

Re: [Pharo-project] Issue 3566 in pharo: Changes needed to update Sound for 1.2

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.2 -Milestone-1.3 Milestone-1.2-DevImage Comment #5 on issue 3566 by marcus.d...(a)gmail.com: Changes needed to update Sound for 1.2 http://code.google.com/p/pharo/issues/detail?id=3566 (No comment was entered for this change.)

Jan. 21, 2011