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

[Pharo 7.0-dev] Build #978: 22010-Integrate-Iceberg-v100
by ci-pharo-ci-jenkins2＠inria.fr May 29, 2018

May 29, 2018

There is a new Pharo build available! The status of the build #978 was: FAILURE. The Pull Request #1452 was integrated: "22010-Integrate-Iceberg-v100" Pull request url: https://github.com/pharo-project/pharo/pull/1452 Issue Url: https://pharo.fogbugz.com/f/cases/22010 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Pharo 7 on SqueakJS (demo)
by Pavel Krivanek May 29, 2018

May 29, 2018

Hi, with some tweaks mostly related to FFI and fonts, we are able to run Pharo 7 on SqueakJS VM. Do not expect blazing performance. Currently, it is about two orders of magnitude slower than the native VM. https://pavel-krivanek.github.io/pharo/pharo.html Cheers, -- Pavel

7 6

Horrible mess in keyboard modifiers processing
by Pavel Krivanek May 29, 2018

May 29, 2018

On Linux and Windows, the keyboard usage is very limited, especially in combination with the mouse. There is no way how to invoke any key corresponding to Mac command key (â). As result there are is no option how on these platforms select several nonadjacent methods in Calypso to display them at once and you cannot click on a method selector to reach the implementation. I tried to log modifiers on input events on all three platforms and this is the sad result: Mac: shift 0 1 1 0 ctrl 0 2 2 0 option (â¥) 0 4 4 0 command (â) 0 8 8 0 The numbers are in order: - modifier key pressed - mouse down - mouse up - modifier key released So on Mac the mouse events are processed correctly but the events related keyboard have no modifiers flags. Linux: shift 0 1 1 0 ctrl 0 0 2 0 win - 0 0 - alt 0 - - 0 altgr - 0 0 - So on Linux the Shift key is processed correctly, The Ctrl key does not have correct modifier flag when the mouse is pressed (which is strange because the combination of Shift+Ctrl returns 0 3 3 0). Win key changes click behavior to right mouse button. For Alt the mouse events are not detected at all and AltGr behaves as Win except the right mouse button simulation. The keyboard event modifiers are not set. Windows: shift 16 1 1 1 16 ctrl 17 2 2 2 17 win - 0 0 0 - alt 18 8 8 8 18 altgr 18 8 8 8 18 Windows as the only platform set modifiers for keyboard events. The mouse button release generates two events, Win key changes behavior to right mouse button, and Alt behaves the same way as AltGr. Cheers, -- Pavel

5 4

[Pharo 7.0-dev] Build #977: 21951-Deprecate-FileDoesNotExist
by ci-pharo-ci-jenkins2＠inria.fr May 29, 2018

May 29, 2018

There is a new Pharo build available! The status of the build #977 was: FAILURE. The Pull Request #1447 was integrated: "21951-Deprecate-FileDoesNotExist" Pull request url: https://github.com/pharo-project/pharo/pull/1447 Issue Url: https://pharo.fogbugz.com/f/cases/21951 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #976: 22000-Click-on-the-taskbar-empty-space-should-open-the-world-menu
by ci-pharo-ci-jenkins2＠inria.fr May 29, 2018

May 29, 2018

There is a new Pharo build available! The status of the build #976 was: SUCCESS. The Pull Request #1454 was integrated: "22000-Click-on-the-taskbar-empty-space-should-open-the-world-menu" Pull request url: https://github.com/pharo-project/pharo/pull/1454 Issue Url: https://pharo.fogbugz.com/f/cases/22000 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

IMPORTANT: ML Etiquette
by Sean P. DeNigris May 29, 2018

May 29, 2018

Dear all, There were several posts in the "Beacon for Pharo 7" thread which top-posted on top of massive unsnipped quotes that were several-previous-posts deep. IMHO this made the conversation impossible to follow. This issue has cropped up from time to time in other threads. Please adhere to basic ML etiquette [1] to maximize our effectiveness. Two essential guidelines are: 1) snip quoted material to just what's necessary to understand what's being replied to 2) Post reply /after/ the quote from the OP, not before. 1. https://www.freebsd.org/doc/en_US.ISO8859-1/articles/mailing-list-faq/etiqu… ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

7 7

[Pharo 7.0-dev] Build #975: 21959-Package-Slot-Traits-is-empty-and-can-be-removed
by ci-pharo-ci-jenkins2＠inria.fr May 28, 2018

May 28, 2018

There is a new Pharo build available! The status of the build #975 was: FAILURE. The Pull Request #1414 was integrated: "21959-Package-Slot-Traits-is-empty-and-can-be-removed" Pull request url: https://github.com/pharo-project/pharo/pull/1414 Issue Url: https://pharo.fogbugz.com/f/cases/21959 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #974: 22006-add-startUsingOverlayForDevelopment-stopUsingOverlayForDevelopment
by ci-pharo-ci-jenkins2＠inria.fr May 28, 2018

May 28, 2018

There is a new Pharo build available! The status of the build #974 was: SUCCESS. The Pull Request #1449 was integrated: "22006-add-startUsingOverlayForDevelopment-stopUsingOverlayForDevelopment" Pull request url: https://github.com/pharo-project/pharo/pull/1449 Issue Url: https://pharo.fogbugz.com/f/cases/22006 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Curious context change latency experiment results (wrt DelayScheduler)
by Ben Coman May 28, 2018

May 28, 2018

One of the key parts of Delay scheduling is setting the resumption time. There are two places this could be done. a. In Delay>>#schedule, running (for example) at userSchedulingPriority=40 b. In DelayMicrosecondScheduler>>#handleTImerEvent:, running at timingPriority=80 When we were using the millisecond clock for delay scheduling, it made sense to use (b.) since the clock might(?) roll over between when resumption time was set, and when #handleTImerEvent: expires delays. This should not be a problem now that we are using the microsecond clock, so I wondered what the latency penalty might be between (a.) and (b.). I ran a little experiment that indicates the cost/latency of switching threads, and was curious if anyone can comment on the validity of the experiment and interpretation of results. I made the following three changes... DelayScheduler subclass: #DelayMicrosecondScheduler instanceVariableNames: 'latencyStart countSinceLastZero' classVariableNames: 'LatencyCounts' poolDictionaries: '' category: 'Kernel-Processes' DelayMicrosecondScheduler>>#schedule: aDelay latencyStart:= Time primUTCMicrosecondsClock. "This is position (a.)" aDelay schedulerBeingWaitedOn ifTrue: [^self error: 'This Delay has already been scheduled.']. accessProtect critical: [ scheduledDelay := aDelay. timingSemaphore signal. "#handleTimerEvent: sets scheduledDelay:=nil" ]. DelayMicrosecondScheduler>>#handleTimerEvent: microsecondNowTick | microsecondNextTick | "Process any schedule requests" "This is position (b.)" scheduledDelay ifNotNil: [ |latency| latency := Time primUTCMicrosecondsClock - latencyStart. LatencyCounts ifNil: [ LatencyCounts := Bag new ]. LatencyCounts add: latency. latency = 0 ifTrue: [ countSinceLastZero := 1 + (countSinceLastZero ifNil: [0])] ifFalse: [Transcript crShow: 'zero latency count ' , countSinceLastZero printString ; show: ' before latency ', latency printString. countSinceLastZero := 0]. "Schedule the given delay." scheduledDelay scheduler: self resumptionTime: microsecondNowTick + (1000 * scheduledDelay millisecondDelayDuration). self scheduleDelay: scheduledDelay. scheduledDelay := nil ]. <snip> rest of method unchanged Then opened the Transcript and in Playground evaluated... Delay delaySchedulerClass: DelayMicrosecondScheduler. The Transcript results are shown below with some comments inserted. Now I guess the latency is affected by garbage collection. But one thing I was curious about is why the latency's were quantised in 1000s. Another interesting thing is that vast majority of the latency's were zero, which was a nice surprise, but can it be true? Or is it a consequence of the quantitisation rounding down? It seems that the idle-ness of the image affected how often a non-zero latency occurred. After I left the house for a while, the count of zero latency was very high, but a few still occurred. It would make sense there was less GC while idle. What is a good snippet of code to stress GC. I presume the latency might increase. zero latency count 2273 before latency 1000 zero latency count 943 before latency 1000 zero latency count 3666 before latency 1000 zero latency count 1643 before latency 1000 zero latency count 27 before latency 1000 "Left house for 20 minutes" zero latency count 12022 before latency 1000 zero latency count 15195 before latency 1000 zero latency count 41998 before latency 1000 "Returned from outing" zero latency count 128 before latency 1000 zero latency count 116 before latency 1000 zero latency count 555 before latency 1000 zero latency count 2377 before latency 1000 zero latency count 5423 before latency 1000 zero latency count 3178 before latency 1000 zero latency count 47 before latency 1000 zero latency count 2276 before latency 1000 "Left house to go shopping" zero latency count 6708 before latency 3000 zero latency count 4896 before latency 1000 zero latency count 433 before latency 1000 zero latency count 7106 before latency 1000 zero latency count 2195 before latency 1000 zero latency count 12397 before latency 1000 zero latency count 4815 before latency 2000 zero latency count 3480 before latency 1000 zero latency count 5690 before latency 1000 zero latency count 1670 before latency 1000 zero latency count 320 before latency 1000 zero latency count 1641 before latency 2000 zero latency count 290 before latency 1000 zero latency count 3835 before latency 1000 zero latency count 3818 before latency 1000 zero latency count 1132 before latency 1000 "Returned from shopping." zero latency count 2045 before latency 1000 zero latency count 671 before latency 1000 zero latency count 167 before latency 1000 zero latency count 147 before latency 1000 >From the System Browser, inspecting the class variable LatencyCounts showed... 0 171329 3000 1 2000 3 1000 49 cheers -ben

2 4

[Pharo 7.0-dev] Build #973: 22008-Move-GTPlaygroundBasicTest-cleaning-to-tearDown
by ci-pharo-ci-jenkins2＠inria.fr May 28, 2018

May 28, 2018

There is a new Pharo build available! The status of the build #973 was: SUCCESS. The Pull Request #1451 was integrated: "22008-Move-GTPlaygroundBasicTest-cleaning-to-tearDown" Pull request url: https://github.com/pharo-project/pharo/pull/1451 Issue Url: https://pharo.fogbugz.com/f/cases/22008 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0