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

[Pharo 7.0-dev] Build #1380: 22206-NautilusRefactoring-should-have-the-tests-in-a-separate-package
by ci-pharo-ci-jenkins2＠inria.fr Nov. 12, 2018

Nov. 12, 2018

There is a new Pharo build available! The status of the build #1380 was: FAILURE. The Pull Request #1974 was integrated: "22206-NautilusRefactoring-should-have-the-tests-in-a-separate-package" Pull request url: https://github.com/pharo-project/pharo/pull/1974 Issue Url: https://pharo.fogbugz.com/f/cases/22206 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1379: Added Interval>>sort: method that raises a "you can not sort an interâ¦
by ci-pharo-ci-jenkins2＠inria.fr Nov. 12, 2018

Nov. 12, 2018

There is a new Pharo build available! The status of the build #1379 was: SUCCESS. The Pull Request #1922 was integrated: "Added Interval>>sort: method that raises a "you can not sort an interâ¦" Pull request url: https://github.com/pharo-project/pharo/pull/1922 Issue Url: https://pharo.fogbugz.com/f/cases/22588 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1378: 22651-URL-color-is-hardcoded-in-welcome-window
by ci-pharo-ci-jenkins2＠inria.fr Nov. 12, 2018

Nov. 12, 2018

There is a new Pharo build available! The status of the build #1378 was: FAILURE. The Pull Request #1972 was integrated: "22651-URL-color-is-hardcoded-in-welcome-window" Pull request url: https://github.com/pharo-project/pharo/pull/1972 Issue Url: https://pharo.fogbugz.com/f/cases/22651 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1377: 22649-Remove DelaySpinScheduler
by ci-pharo-ci-jenkins2＠inria.fr Nov. 12, 2018

Nov. 12, 2018

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

1 0

Esteban's ChangeLog week of 5 November 2018
by estebanlm＠gmail.com Nov. 12, 2018

Nov. 12, 2018

Hello! This is my weekly ChangeLog, from 5 November 2018 to 11 November 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=5/11/2018&to=11/11/2018 ChangeLog ========= 5 November 2018: ---------------- * I just [announced](http://forum.world.st/ANN-Pharo-v7-0-0-rc1-released-td5088221.html) Pharo v7.0.0-rc1. Now the real work begins... :P * I worked on [case: 22628](https://pharo.fogbugz.com/f/cases/22628): merge latest FFI-Kernel changes. Thing is, now there is some overlapping between FFI-Kernel and UnifiedFFI, because they changed it in some things we already solved in UFFI, but well... we will have to see this in the future :) * I made a small PR to add a fix that Eliot contributed to it: [https://github.com/pharo-vcs/tonel/pull/60](https://github.com/pharo-vcs/to… . Is an error that happens when a snapshot contains *only* method extensions. cheers! Esteban

1 0

[Pharo 7.0-dev] Build #1376: 22656-Improve-ImageReadWriter-comments
by ci-pharo-ci-jenkins2＠inria.fr Nov. 11, 2018

Nov. 11, 2018

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

1 0

Streams and FileDialog in Pharo 6 and 7
by Torsten Bergmann Nov. 11, 2018

Nov. 11, 2018

Hi, A question to those who worked on the new streams for Pharo 7: In PHARO 6 I used the following expression to open a file dialog and let the user choose a binary file: s := UITheme builder fileOpen: 'Choose a file' extensions: #('exe'). This returned - either nil (when file dialog was canceled) - a "MultiByteFileStream" instance when a file was selected The MultiByteFileStream instance already had the name of the file (= full path) and I was able to query it for further use: s := UITheme builder fileOpen: 'Choose a file' extensions: #('exe'). s name inspect (for instance to display which file is processed in a window by showing the full path) Now in PHARO 7 same expression returns an instance of ZnCharacterReadStream (as MultiByteFileStream is deprecated): s := UITheme builder fileOpen: 'Choose a file' extensions: #('exe'). and ZnCharacterReadStream does not understand #name - and in fact the info about the name is totally lost/not available. To me this looks missing/broken. So what is the recommended way in Pharo 7 to open a file dialog, let the use choose a file and get a file stream but also the name? IMHO this is either broken or missing... Thanks T.

6 10

[Pharo 7.0-dev] Build #1375: 22561-uFFI-should-not-require-decompilation-to-extract-sender-selector
by ci-pharo-ci-jenkins2＠inria.fr Nov. 10, 2018

Nov. 10, 2018

There is a new Pharo build available! The status of the build #1375 was: SUCCESS. The Pull Request #1897 was integrated: "22561-uFFI-should-not-require-decompilation-to-extract-sender-selector" Pull request url: https://github.com/pharo-project/pharo/pull/1897 Issue Url: https://pharo.fogbugz.com/f/cases/22561 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

WELL512 PRNG
by Sven Van Caekenberghe Nov. 9, 2018

Nov. 9, 2018

Hi, By accident I came across a pseudo random number generator that I never heard off before. It is supposed to be pretty good and had a very simple implementation. So I ported it to Pharo. <class comment> I am RandomWELL512, a random number generator. I use the PRNG (Pseudo Randon Number Generator) WELL (Well equidistributed long-period linear) with a 512 bit state. https://en.wikipedia.org/wiki/Well_equidistributed_long-period_linear http://www.iro.umontreal.ca/~lecuyer/myftp/papers/wellrng.pdf Implementation algorithm (See #nextUInt32) http://www.lomont.org/Math/Papers/2008/Lomont_PRNG_2008.pdf (Chris Lomont, www.lomont.org) Usage RandomWELL512 new in: [ :r | (1 to: 10) collect: [ :i | r nextUInt32 ] ]. RandomWELL512 new useUnixRandomGeneratorSeed; in: [ :r | (1 to: 10) collect: [ :i | r next ] ]. RandomWELL512 new in: [ :r | (1 to: 10) collect: [ :i | r nextInt: 1000 ] ]. RandomWELL512 new in: [ :random | | count all | random useUnixRandomGeneratorSeed. count := 1024 * 1024. all := Array new: count streamContents: [ :out | count timesRepeat: [ out nextPut: random next ] ]. { all min. all max. all average. all stdev } ]. [ RandomWELL512 new in: [ :random | 1 to: 1e6 do: [ :i | random next ] ] ] timeToRun. Note that you should create one instance, seed it properly, and keep using it. </class comment> It is acceptably fast, generating 1M [0,1) Floats in about 0.1s. I compared the output with a fixed initial state to the C code that I started from and I got the same numbers. Maybe some people find this interesting. I attached a file out. Sven

4 4

Action list for Pharo 70 release
by Stephane Ducasse Nov. 9, 2018

Nov. 9, 2018

Hi The team got a meeting about the final points to address before the release. Here is the summary of action points one and to do to the meeting next month. Done: Release - version info from tag Calypso - Traits (In calypso repository, not yet in Pharo) - Extensions (In calypso repository, not yet in Pharo) Doing: Release - File name / repository should take tag information => Esteban - Launcher should be updated automatically without having to touch it => Christophe - Update Zeronconf => Esteban + Vincent Calypso - Review refactorings => Vincent - Integrated Spotter shortcut => Esteban - Selection/Navigation => ??? Selection glitches (see why sometimes focus is broken and cmd+W is wrong) => Pavel FFI recompilation of Structures => Guille Backport Unicode Support from Launcher => Guille FT2 bug, update Freetype library => Esteban Cleaning pharo-scripts repository => ??? Start preparing changes log => Marcus >From what I understood the window 64 bits is to unstable to be proposed. Stef

1 0