December 2019 - Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #1082: CleanupASTCache
by ci-pharo-ci-jenkins2＠inria.fr Dec. 19, 2019

Dec. 19, 2019

There is a new Pharo build available! The status of the build #1082 was: SUCCESS. The Pull Request #5393 was integrated: "CleanupASTCache" Pull request url: https://github.com/pharo-project/pharo/pull/5393 Issue Url: https://github.com/pharo-project/pharo/issues/CleanupASTCache Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

TaskIt
by Santiago Bragagnolo Dec. 17, 2019

Dec. 17, 2019

Hi everybody! We are starting to discuss with norbert about letting taskit to leave my incubator (my github account to go elsewhere). I have being thinking about it since long time, since i would like it to allow taskit to evolve into more than just my needs and wishes. The sidequestion i am bringing today it may seem (or even be) almost scholastic at this point, but i think it should have some space. The question is if to move it to pharo-contributions, or if to create a new pharo-processing. During the ESUG i came up with the idea/feeling/etc that it would be nice to have a group of people interested into processing (as hobby, duty, etc) for being able to push further this project and what-ever-other related project. During the conference i addressed norbert, tomohiro, mariano, matteo, guille, pablo, noury, (people for whom processing directly or indirectly is a primary concern) and i think there is even more people interested in this kind of general problematic, for what i sensed specially during my esug presentation. I think that to build a kind of team or group for discussing and working on this subject is a step in a direction that search to solve many modern daily problems that pushes us out of larger models of business and interaction (cloud and derivatives). Having this points in mind i think that the choice of this new github project could be a good point to start a to work on this goal (as a first place of gathering). Still, i would like to hear other's opinion, in order to be able to deal with this maybe before new year :). Thanks for your time and reading :) Santiago

5 5

[Mm10s] 2019-12-16
by Esteban Lorenzano Dec. 17, 2019

Dec. 17, 2019

### Last week: - [Release] Open Pharo 9.0 branch to start sending PRs not included in P8 there. - [Release] Organise issues that will enter in P8 (WIP). - [Release] Move GT-EventRecorder legacy to a branch, so is easier to reload it. - [Spec2] Better search feature for Lists/Trees/Tables - [Spec2] Add bold/italic properties to styles - [Spec2] Add âactivationâ property to ComponentList - [TFFI] Add better information when registering callbacks to facilitate debugging. - [TFFI] Make latest version to compile on macOS (libffi compilation was wrong) - [VM] Work with Pablo on AIO Interrupt VM (still fixing glitches, still WIP). - [GTK] Enhance Form to GtkPixbuf conversion, avoiding double conversions (resulting image is a lot more precise) - [GTK] Fix a bug on number input fields and ranges. ### This week (starting 2019-12-16): - [Release] Organise issues that will enter in P8. - [Release] Prepare release notes. - [Spec2] Fix radio buttons. - [Spec2] TechTalk Thursday ### Pipeline - [Release] Pharo 8 Release. - [VM] debug AIO and worker thread VMs on linux and windows.

3 3

[Pharo 8.0] Build #1081: 5343-Inconsistency-in-the-rules-relating-to-checking-the-code-of-methods
by ci-pharo-ci-jenkins2＠inria.fr Dec. 17, 2019

Dec. 17, 2019

There is a new Pharo build available! The status of the build #1081 was: SUCCESS. The Pull Request #5358 was integrated: "5343-Inconsistency-in-the-rules-relating-to-checking-the-code-of-methods" Pull request url: https://github.com/pharo-project/pharo/pull/5358 Issue Url: https://github.com/pharo-project/pharo/issues/5343 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Pharo TechTalk December 19th
by Marcus Denker Dec. 17, 2019

Dec. 17, 2019

A regular chat about Pharo. Topic: âWorking with Spec2 and GTKâ https://association.pharo.org/event-3419547 There is a Discord channel where everything else will be organised (e.g. youtube life streaming if needed).

1 0

[ANN] Next Pharo Sprint: Dec 20
by Marcus Denker Dec. 17, 2019

Dec. 17, 2019

We will organize a Pharo sprint / Moose dojo Dec 20, starting at 10:00am. (Local Time Paris). Goals of this sprint: - Pharo 8: Fix issues from tracker https://github.com/pharo-project/pharo/issues <https://github.com/pharo-project/pharo/issues> Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contribute-events <http://pharo.org/contribute-events> We have added a Board to coordinate the work: https://github.com/orgs/pharo-project/projects/9 <https://github.com/orgs/pharo-project/projects/9> Known Local Sprint meetings - Lille/France: It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come A list of all Pharo Event of the year an be found here: https://association.pharo.org/events <https://association.pharo.org/events>

1 0

[Pharo 8.0] Build #1080: 5372-Completion-failure-when-using-super-in-a-trait
by ci-pharo-ci-jenkins2＠inria.fr Dec. 17, 2019

Dec. 17, 2019

There is a new Pharo build available! The status of the build #1080 was: SUCCESS. The Pull Request #5385 was integrated: "5372-Completion-failure-when-using-super-in-a-trait" Pull request url: https://github.com/pharo-project/pharo/pull/5385 Issue Url: https://github.com/pharo-project/pharo/issues/5372 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1079: Improving the FreeTypeCache mutex.
by ci-pharo-ci-jenkins2＠inria.fr Dec. 16, 2019

Dec. 16, 2019

There is a new Pharo build available! The status of the build #1079 was: SUCCESS. The Pull Request #5384 was integrated: "Improving the FreeTypeCache mutex." Pull request url: https://github.com/pharo-project/pharo/pull/5384 Issue Url: https://github.com/pharo-project/pharo/issues/improving Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1078: DebugSession modification for DebuggerSelector
by ci-pharo-ci-jenkins2＠inria.fr Dec. 16, 2019

Dec. 16, 2019

There is a new Pharo build available! The status of the build #1078 was: FAILURE. The Pull Request #5365 was integrated: "DebugSession modification for DebuggerSelector" Pull request url: https://github.com/pharo-project/pharo/pull/5365 Issue Url: https://github.com/pharo-project/pharo/issues/DebugSession Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Grouper
by Julien Delplanque Dec. 15, 2019

Dec. 15, 2019

Hello, I made a small library that reify grouping (that one does via #groupBy: usually): Grouper https://github.com/juliendelplanque/Grouper It is designed in the same spirit as SortFunction, but for grouping. Quick example: The following code snippet using Grouper: (10 to: 50)groupUsing: [:integer | integer asString first ]. "an OrderedDictionary( $1->#(10 11 12 13 14 15 16 17 18 19) $2->#(20 21 22 23 24 25 26 27 28 29) $3->#(30 31 32 33 34 35 36 37 38 39) $4->#(40 41 42 43 44 45 46 47 48 49) $5->#(50))" is equivalent to the following code snippet using built-in|#groupedBy:|method: (10 to: 50)groupedBy: [:integer | integer asString first ] "an OrderedDictionary( $1->#(10 11 12 13 14 15 16 17 18 19) $2->#(20 21 22 23 24 25 26 27 28 29) $3->#(30 31 32 33 34 35 36 37 38 39) $4->#(40 41 42 43 44 45 46 47 48 49) $5->#(50))" The advantage of using it is that it allows one to compose grouper objects. Thus, it is easy to describe grouping on 2 or 3 levels. Fore example: The power of Grouper is that group description are first-class objects. Thus, it is possible to compose group descriptions in order to group a flat collection on multiple levels. For example: groupComposition:= [:integer | integer asString first ] grouper , [:integer | integer asString second ]. (10 to: 50)groupUsing: groupComposition. "an OrderedDictionary( $1->an OrderedDictionary( $0->#(10) $1->#(11) $2->#(12) $3->#(13) $4->#(14) $5->#(15) $6->#(16) $7->#(17) $8->#(18) $9->#(19)) $2->an OrderedDictionary( $0->#(20) $1->#(21) $2->#(22) $3->#(23) $4->#(24) $5->#(25) $6->#(26) $7->#(27) $8->#(28) $9->#(29)) $3->an OrderedDictionary( $0->#(30) $1->#(31) $2->#(32) $3->#(33) $4->#(34) $5->#(35) $6->#(36) $7->#(37) $8->#(38) $9->#(39)) $4->an OrderedDictionary( $0->#(40) $1->#(41) $2->#(42) $3->#(43) $4->#(44) $5->#(45) $6->#(46) $7->#(47) $8->#(48) $9->#(49)) $5->an OrderedDictionary($0->#(50)))" On the github, there are more example showing how to build trees with custom objects. Any feedback for this library is welcome. I would like to propose it to Pharo in the near future because it would simplify a lot of code in DrTests (related to result tree views, the tree on the right of the UI). I don't know if it will be possible before next release as we are in feature freeze. Cheers, Julien

4 5