May 2016 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60019 Home: https://github.com/pharo-project/pharo-core

May 18, 2016

[pharo-project/pharo-core] 2e3347: 60019

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 2e33473541b3c4497a1e6c1e10384d35e3341758 https://github.com/pharo-project/pharo-core/commit/2e33473541b3c4497a1e6c1e… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-05-18 (Wed, 18 May 2016) Changed paths: A Morphic-Base.package/StringMorph.class/instance/accessing/stringBounds.st A Morphic-Base.package/StringMorph.class/instance/accessing/stringColor.st M Morphic-Base.package/StringMorph.class/instance/drawing/drawOn_.st M Morphic-Widgets-Basic.package/LabelMorph.class/class/examples/example.st M Morphic-Widgets-Basic.package/LabelMorph.class/class/examples/exampleDisable.st A Morphic-Widgets-Basic.package/LabelMorph.class/class/examples/exampleDisableInset.st A Morphic-Widgets-Basic.package/LabelMorph.class/instance/accessing/stringColor.st M Morphic-Widgets-Basic.package/LabelMorph.class/instance/drawing/drawOn_.st A Polymorph-Widgets.package/extension/LabelMorph/instance/themeChanged.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60018.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60019.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60018.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60019.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60019 18245 StringMorph and Label morph lack #themeChanged https://pharo.fogbugz.com/f/cases/18245 http://files.pharo.org/image/60/60019.zip

May 18, 2016

Re: [Pharo-dev] Problem with delay waiting (OSSubprocess code) on Pharo 5.0

by Mariano Martinez Peck

On Wed, May 18, 2016 at 2:10 PM, Ben Coman <btc(a)openinworld.com> wrote: > I don't have time to look at this properly until tomorrow. > In the meantime, could you just post the result of... > > Delay delaySchedulerClass > it should be "DelayExperimentalSpinScheduler" *** > > Yes, it is. > Also could you try a few of the other options from > World > System > Settings > System ... > > Do you know which is the "Safest" to use? Or at least which was used in say, 4.0? > > ***whoops, the Experimental tag should have been dropped for Pharo 5 > Release. Its been fine for months (unless this is a fault :) ] > > Yes, I found that strange too. > > > > Maybe it is wrong to keep and re-use same instance of Delay? (note it is > > outside the closure) (this was not a problem in the past). > > Not sure. I've heard others say Delays should only be used once. To > experiment, could you try creating a delay each time. > > Ok, I will try this. But again, it would take some some time to test and it happens to me every in while only. Thanks!! -- Mariano http://marianopeck.wordpress.com

May 18, 2016

Re: [Pharo-dev] From a mooc user: method source with it' take so long in Pharo 5

by Cyril Ferlicot D.

Le 18/05/2016 19:12, stepharo a Ã©crit : > I am wondering why does the search 'method source with it' take so long > in Pharo 5? On my PC, When I select the text 'menu' and search for all > 'method source with it', in Squeak 5 it takes 3 seconds. In Pharo 5 it > takes 21 seconds. > > Did you try with the same computer? It depends a lot of the OS. On my Mac it takes 20sec, on my windows it takes 7-8sec and on my linux it takes 3-5sec. -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

May 18, 2016

From a mooc user: method source with it' take so long in Pharo 5

by stepharo

I am wondering why does the search 'method source with it' take so long in Pharo 5? On my PC, When I select the text 'menu' and search for all 'method source with it', in Squeak 5 it takes 3 seconds. In Pharo 5 it takes 21 seconds.

May 18, 2016

Re: [Pharo-dev] Problem with delay waiting (OSSubprocess code) on Pharo 5.0

by Ben Coman

I don't have time to look at this properly until tomorrow. In the meantime, could you just post the result of... Delay delaySchedulerClass it should be "DelayExperimentalSpinScheduler" *** Also could you try a few of the other options from World > System > Settings > System ... ***whoops, the Experimental tag should have been dropped for Pharo 5 Release. Its been fine for months (unless this is a fault :) ] On Wed, May 18, 2016 at 11:49 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Hi guys, > > I am seeing a problem in Pharo 5.0 regarding Delay >> wait. I cannot explain > how this could happened but it does, and it happened to me a couple of times > (but not fully reproducible). > > In OSSubprocess I have this child watcher: > > initializeChildWatcher > "This is a process which waits for the death of a child processes. Use > SIGCHLD events rather than a Delay to poll." > > | processSynchronizationDelay | > processSynchronizationDelay := Delay forMilliseconds: 20. > childWatcher ifNil: [ > childWatcher := [[ > "OSProcess authors suspected that there were various ways in which OS > signals > could be missed under conditions of heavy load. For that reason, we use > #waitTimeoutMSecs: with the semaphore, so that if a signal is missed, > we time out and rescan occasionally anyway > (#updateActiveChildrenAndNotifyDead > sends queryExitStatus which sends waitpid() ) > " > self sigChldSemaphore waitTimeoutMSecs: 1000. > processSynchronizationDelay wait. "Avoids lost signals in heavy process > switching" > self updateActiveChildrenAndNotifyDead. > ] repeat] newProcess. > > childWatcher resume. > "name selected to look reasonable in the process browser" > childWatcher name: ((ReadStream on: childWatcher hash asString) next: 5) > , ': the OSSubprocess child watcher' > ] > > > The problem is that now above process is hung on the > "processSynchronizationDelay wait.". At least that's what I can see from the > process browser. That should not hung, of course, and should stop waiting > after 20 ms. > > If I inspect the Delay instance in question (doing the wait) I see that the > print string is bad.... "a Delay(20 msecs; 3641032396485 msecs remaining)". > WTF? 20ms and you remain 3641032396485 to wait??? I attach an screenshot of > the Delay instance in case there could be something wrong. > > Maybe it is wrong to keep and re-use same instance of Delay? (note it is > outside the closure) (this was not a problem in the past). Not sure. I've heard others say Delays should only be used once. To experiment, could you try creating a delay each time. cheers -ben

May 18, 2016

TEXT drag and drop

by lb

Hi, I have made a little tool for draging and dropping text selection. like windows Word. It can work in Pharo 40 50 and 60. Have a fun! LiangBing MCHttpRepository location: 'http://www.smalltalkhub.com/mc/liangbing/Text-DragDrop/main' user: '' password: ''

May 18, 2016

Scrollable Spec Model

by Peter UhnÃ¡k

Hi, anyone has any experience with scrollable (arbitrary) Spec Model? e.g. I have a long list of buttons and fixed outer container windowâ¦ â As far as I can see scrolling is only available on morphic side, so I am not sure how to augment itâ¦ (Although we should probably allow scrolling on Spec side in some way) Thanks, Peter

May 18, 2016

Problem with delay waiting (OSSubprocess code) on Pharo 5.0

by Mariano Martinez Peck

Hi guys, I am seeing a problem in Pharo 5.0 regarding Delay >> wait. I cannot explain how this could happened but it does, and it happened to me a couple of times (but not fully reproducible). In OSSubprocess I have this child watcher: initializeChildWatcher "This is a process which waits for the death of a child processes. Use SIGCHLD events rather than a Delay to poll." | processSynchronizationDelay | *processSynchronizationDelay := Delay forMilliseconds: 20.* childWatcher ifNil: [ childWatcher := [[ "OSProcess authors suspected that there were various ways in which OS signals could be missed under conditions of heavy load. For that reason, we use #waitTimeoutMSecs: with the semaphore, so that if a signal is missed, we time out and rescan occasionally anyway (#updateActiveChildrenAndNotifyDead sends queryExitStatus which sends waitpid() ) " self sigChldSemaphore waitTimeoutMSecs: 1000. *processSynchronizationDelay wait. "Avoids lost signals in heavy process switching"* self updateActiveChildrenAndNotifyDead. ] repeat] newProcess. childWatcher resume. "name selected to look reasonable in the process browser" childWatcher name: ((ReadStream on: childWatcher hash asString) next: 5) , ': the OSSubprocess child watcher' ] The problem is that now above process is hung on the "*processSynchronizationDelay wait.". *At least that's what I can see from the process browser. That should not hung, of course, and should stop waiting after 20 ms. If I inspect the Delay instance in question (doing the wait) I see that the print string is bad.... "a Delay(20 msecs; 3641032396485 msecs remaining)". WTF? 20ms and you remain 3641032396485 to wait??? I attach an screenshot of the Delay instance in case there could be something wrong. Maybe it is wrong to keep and re-use same instance of Delay? (note it is outside the closure) (this was not a problem in the past). Thanks in advance for any clue. -- Mariano http://marianopeck.wordpress.com

May 18, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60018 Home: https://github.com/pharo-project/pharo-core

May 18, 2016