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

Re: [Pharo-project] Issue 3635 in pharo: [Hudson] reuse images downstream

by pharo＠googlecode.com

Comment #2 on issue 3635 by marcus.d...(a)gmail.com: [Hudson] reuse images downstream http://code.google.com/p/pharo/issues/detail?id=3635 There is a plugin to copy files to the slave. http://wiki.hudson-ci.org//display/HUDSON/Copy+To+Slave+Plugin Sady, our version of Hudson is to old for installing this.

Feb. 1, 2011

Re: [Pharo-project] Issue 3635 in pharo: [Hudson] reuse images downstream

by pharo＠googlecode.com

Comment #1 on issue 3635 by marcus.d...(a)gmail.com: [Hudson] reuse images downstream http://code.google.com/p/pharo/issues/detail?id=3635 It seems the last successful build are not availale on the build slave the script searches for them in some /lastSuccessful/ directory: elif [ -n "$WORKSPACE" ] ; then INPUT_IMAGE=`find -L "$WORKSPACE/../.." -name "$OPTARG.image" | grep "/lastSuccessful/" | head -n 1` fi

Feb. 1, 2011

Re: [Pharo-project] about Sound and setting :(

by Igor Stasenko

On 1 February 2011 12:36, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: > Again, you are using the wrong version of Sound, sorry I couldn't tell you sooner. > Work has been busy :( > > Remember part2 of my mail of what needed to be done? > > "Update MetacelloConfiguration to use PharoSound instead of PharoNonCorePackages" > guys lets just clean up/move files between repositories to avoid future confusion. I don't know if this can be done easily, but i think that it would be good that if you moving package to different repository, then remove/move all versions from old repository at once.. So i prefer to see 'i cannot load package' instead 'i loaded package and it doesn't works ... yes because you loaded it from wrong place'. :) > :) > > Cheers, > Henry > > > > On Jan 30, 2011, at 6:29 58PM, StÃ©phane Ducasse wrote: > >> Hi guys >> >> loadSoundEnabled >> Â Â Â Â Â Â Â self loadSetting: #soundEnabled withBlock: [SoundService soundEnabled: nil]. >> >> >> since mariano is away and I do not know what was done in Sound, I'm trying but this is not simple when you do not know >> what was the intention. >> >> >> The method is: >> >> resumePlaying: aSound quickStart: quickStart >> Â Â Â "Start playing the given sound without resetting it; it will resume playing from where it last stopped. If quickStart is true, then try to start playing the given sound immediately." >> >> Â Â Â | doQuickStart | >> Â Â Â SoundSettings soundsEnabled ifFalse: [^ self]. >> Â Â Â doQuickStart := quickStart. >> Â Â Â SoundSettings soundQuickStart ifFalse: [doQuickStart := false]. >> Â Â Â PlayerProcess == nil ifTrue: [ >> Â Â Â Â Â Â Â self canStartPlayer ifFalse: [^ self]. >> Â Â Â Â Â Â Â ^self startUpWithSound: aSound]. >> >> Â Â Â PlayerSemaphore critical: [ >> Â Â Â Â Â Â Â (ActiveSounds includes: aSound) >> Â Â Â Â Â Â Â Â Â Â Â ifTrue: [doQuickStart := false] >> Â Â Â Â Â Â Â Â Â Â Â ifFalse: [ >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â doQuickStart ifFalse: [ActiveSounds add: aSound]]]. >> >> Â Â Â "quick-start the given sound, unless the sound player has just started" >> Â Â Â doQuickStart ifTrue: [self startPlayingImmediately: aSound]. >> >> >> it refers to SoundSettings and there is no such a thing. There is no implementors of soundsEnabled >> So I tried to understand the changes made in Slice-3566 >> >> Now the question is do we want SoundService to play the role of a setting provider? >> Originally I thought to put it in BaseSoundSystem. >> >> But the code of henrik seems to use SoundService. Now BaseSoundSystem register itself as the default sound service. >> So I'm confused! >> >> Help is welcome. >> >> Stef >> >> >> >> >> >> >> >> >> >> > > > -- Best regards, Igor Stasenko AKA sig.

Feb. 1, 2011

Re: [Pharo-project] Tracing bugs/corrections/regressions ... in Pharo

by Henrik Johansen

On Feb 1, 2011, at 8:58 37AM, Nicolas Cellier wrote: > 2011/2/1 Marcus Denker <marcus.denker(a)inria.fr>: >> >> On Feb 1, 2011, at 8:01 AM, Nicolas Cellier wrote: >> >>> 2011/2/1 Marcus Denker <marcus.denker(a)inria.fr>: >>>>> >>>>> Maybe I had some bad luck with >>>>> http://code.google.com/p/pharo/issues/detail?id=3468 >>>>> Or is there many examples of issues closed without a clue ? >>>> >>>> In a case like that, the changeset was just merged in the release. >>>> >>>> The test is failing, as you can see: >>>> >>>> https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.3/lastCompleted… >>>> >>>> >>> >>> This is probably because you must >>> (Object recompile: #perform:withArguments:) >>> >> >> The 1.3 core image was recompiled completely around 13020... >> >> Marcus >> >> >> -- >> Marcus Denker -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> > > Strange, the change worked for me in Squeak once I recompiled. > > Nicolas > #perform:withArguments: works in Pharo as well, Igor's fix for it was applied back in May: http://code.google.com/p/pharo/issues/detail?id=2443 What it doesn't fix (and which the test in 3468 highlights), are arbitrary sends to #perform: withArguments: inSuperclass: (Ie. the compiler does not expand frame size of all senders, nor does the test run on a VM which does not error with many arguments) #perform:withArguments: just happend to be the most likely sender to run into it. Cheers, Henry

Feb. 1, 2011

[Pharo-project] Automatic One-Click VM

by Geert Claes

Can we replace the Croquet VM exe file that is bundled in the one-click images generated using Hudson with a with a Pharo branded one? -- View this message in context: http://forum.world.st/Automatic-One-Click-VM-tp3251164p3251164.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 1, 2011

Re: [Pharo-project] react on low space

by Schwab,Wilhelm K

Max, #isSpaceLow will be of value only if it is called on some type of event (from the gc?) or polled in some way. When my Dolphin images have crashed due to low space, it has invariably been due to one of two things: (1) early on, improper clean up of ODBC statements; (2) loops over very large numbers of objects serialized from disk without proper attention to #release. Object Arts often insisted that finalization water marks would save the day in such situations; experience tells me otherwise. As a general rule, I am in favor of having the system leave behind information of how it failed. In the case of low space, one *might* have to settle for knowing when a low-space condition arose; a complete set of callstacks might be helpful, assuming the system can write it under such cirumstances. The computation that goes over the cliff could easily be unrelated to the resource hog that caused the problem. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Max Leske [maxleske(a)gmail.com] Sent: Tuesday, February 01, 2011 6:00 AM To: pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] react on low space I'm bumping this message. I think it's an important question and could help other developers who might have the same problem one day. The low space watcher is cool but if you don't get the chance to actually look at the stack it's pretty useless. Max On 30.01.2011, at 13:10, Max Leske wrote: Hi guys Is there an easy way to react on low space? Something like: SmalltalkImage isSpaceLow ifTrue: [ <suspend my process> ] The reason I'm asking is that I have a background process running that causes a low space condition but I never get around to opening the debugger and the image crashes on me. So for debugging purposes I'd like to periodically check the space that is left or alternatively be notified if low space is signalled. Any ideas? Thanks, Max

Feb. 1, 2011

Re: [Pharo-project] about Sound and setting :(

by Henrik Johansen

Again, you are using the wrong version of Sound, sorry I couldn't tell you sooner. Work has been busy :( Remember part2 of my mail of what needed to be done? "Update MetacelloConfiguration to use PharoSound instead of PharoNonCorePackages" :) Cheers, Henry On Jan 30, 2011, at 6:29 58PM, StÃ©phane Ducasse wrote: > Hi guys > > loadSoundEnabled > self loadSetting: #soundEnabled withBlock: [SoundService soundEnabled: nil]. > > > since mariano is away and I do not know what was done in Sound, I'm trying but this is not simple when you do not know > what was the intention. > > > The method is: > > resumePlaying: aSound quickStart: quickStart > "Start playing the given sound without resetting it; it will resume playing from where it last stopped. If quickStart is true, then try to start playing the given sound immediately." > > | doQuickStart | > SoundSettings soundsEnabled ifFalse: [^ self]. > doQuickStart := quickStart. > SoundSettings soundQuickStart ifFalse: [doQuickStart := false]. > PlayerProcess == nil ifTrue: [ > self canStartPlayer ifFalse: [^ self]. > ^self startUpWithSound: aSound]. > > PlayerSemaphore critical: [ > (ActiveSounds includes: aSound) > ifTrue: [doQuickStart := false] > ifFalse: [ > doQuickStart ifFalse: [ActiveSounds add: aSound]]]. > > "quick-start the given sound, unless the sound player has just started" > doQuickStart ifTrue: [self startPlayingImmediately: aSound]. > > > it refers to SoundSettings and there is no such a thing. There is no implementors of soundsEnabled > So I tried to understand the changes made in Slice-3566 > > Now the question is do we want SoundService to play the role of a setting provider? > Originally I thought to put it in BaseSoundSystem. > > But the code of henrik seems to use SoundService. Now BaseSoundSystem register itself as the default sound service. > So I'm confused! > > Help is welcome. > > Stef > > > > > > > > > >

Feb. 1, 2011

Re: [Pharo-project] Issue 3482 in pharo: InterimSoundMorph references to SketchMorph

by pharo＠googlecode.com

Comment #10 on issue 3482 by ryd...(a)gmail.com: InterimSoundMorph references to SketchMorph http://code.google.com/p/pharo/issues/detail?id=3482 Wait what? This makes no sense whatsover... There's one setting in SoundSystem, namely soundEnabled. Why would you delegate that to the installed soundsystem? So sound is automatically turned on/off when you change what sounds to use? That's not a good use-case imho...

Feb. 1, 2011

Re: [Pharo-project] SoundSettings reference in Sound?

by Henrik Johansen

Yes, you were using the wrong version of Sound. Use the one in PharoSound, not NonCorePackages. Cheers, Henry On Jan 30, 2011, at 5:09 20PM, StÃ©phane Ducasse wrote: > Hi guy > > when I take 1.2 latest version I see that there are reference to SoundSetting in SoundPlayer. > Now I cannot find any definition of this setting. > > Henrik I saw that you work on setting in sounds. > Does it ring a bell for you? > > Stef > > > > resumePlaying: aSound quickStart: quickStart > "Start playing the given sound without resetting it; it will resume playing from where it last stopped. If quickStart is true, then try to start playing the given sound immediately." > > | doQuickStart | > SoundSettings soundsEnabled ifFalse: [^ self]. > doQuickStart := quickStart. > SoundSettings soundQuickStart ifFalse: [doQuickStart := false]. > PlayerProcess == nil ifTrue: [ > self canStartPlayer ifFalse: [^ self]. > ^self startUpWithSound: aSound]. > > PlayerSemaphore critical: [ > (ActiveSounds includes: aSound) > ifTrue: [doQuickStart := false] > ifFalse: [ > doQuickStart ifFalse: [ActiveSounds add: aSound]]]. > > "quick-start the given sound, unless the sound player has just started" > doQuickStart ifTrue: [self startPlayingImmediately: aSound]. > >

Feb. 1, 2011

Re: [Pharo-project] Sound package fixes

by Henrik Johansen

On Jan 31, 2011, at 6:18 23PM, StÃ©phane Ducasse wrote: > Hi > > we merged all the squeak fixes to Sound and published them in > PharoNonCorePackages > > It will be loaded in 1.3 dev but you can load them if you want to try. > > Stef > Why? http://www.squeaksource.com/PharoSound Cheers, Henry

Feb. 1, 2011