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

Re: [Pharo-dev] [ANN] Grouper

by Esteban Maringolo

Hi Julien, The code is not public and was done for a former customer, so not readily shareable in public. We can talk in Discord to share some ideas, but as customizable as Grouper is, I could use my own "group" objects as nodes. Once I get back to modify something in that part of my code, I'll see how to integrate into what you've done. Regards! Esteban A. Maringolo On Mon, Dec 9, 2019 at 3:52 PM Julien Delplanque <julien.delplanque(a)inria.fr> wrote: > > Hello Esteban, > > Le 9/12/19 Ã 19:22, Esteban Maringolo a Ã©crit : > > Hi Julien, > > > > Interesting, in the last years I've been using a similar set of > > classes that build groups, and can also nest them, but yours seems > > more customizable. > Cool! Is your code available somewhere? Maybe our ideas are different so > Grouper could profit from that? > > > > Thank you for sharing it. > > > > I'll give it a try! > > Cool. :-) > > Julien > >

Dec. 9, 2019

[Pharo 8.0] Build #1058: 5273-RBScanner-contain-strange-methods

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1058 was: FAILURE. The Pull Request #5351 was integrated: "5273-RBScanner-contain-strange-methods" Pull request url: https://github.com/pharo-project/pharo/pull/5351 Issue Url: https://github.com/pharo-project/pharo/issues/5273 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 9, 2019

Re: [Pharo-dev] [ANN] Grouper

by Julien Delplanque

Hello Esteban, Le 9/12/19 Ã 19:22, Esteban Maringolo a Ã©critÂ : > Hi Julien, > > Interesting, in the last years I've been using a similar set of > classes that build groups, and can also nest them, but yours seems > more customizable. Cool! Is your code available somewhere? Maybe our ideas are different so Grouper could profit from that? > > Thank you for sharing it. > > I'll give it a try! Cool. :-) Julien

Dec. 9, 2019

Re: [Pharo-dev] [ANN] Grouper

by Esteban Maringolo

Hi Julien, Interesting, in the last years I've been using a similar set of classes that build groups, and can also nest them, but yours seems more customizable. Thank you for sharing it. I'll give it a try! Esteban A. Maringolo On Mon, Dec 9, 2019 at 11:10 AM Julien Delplanque <julien.delplanque(a)inria.fr> wrote: > > 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

Dec. 9, 2019

[Pharo 8.0] Build #1057: Adding additional version for comparing with the catalog tags.

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1057 was: FAILURE. The Pull Request #5347 was integrated: "Adding additional version for comparing with the catalog tags." Pull request url: https://github.com/pharo-project/pharo/pull/5347 Issue Url: https://github.com/pharo-project/pharo/issues/2296 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 9, 2019

[ANN] Grouper

by Julien Delplanque

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

Dec. 9, 2019

[Pharo 8.0] Build #1056: 5344-DrTests-Allow-one-to-prioritise-tree-view

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1056 was: SUCCESS. The Pull Request #5345 was integrated: "5344-DrTests-Allow-one-to-prioritise-tree-view" Pull request url: https://github.com/pharo-project/pharo/pull/5345 Issue Url: https://github.com/pharo-project/pharo/issues/5344 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 9, 2019

Re: [Pharo-dev] [ANN] Roadmap progress report November 2019

by Esteban Lorenzano

Hi, > On 9 Dec 2019, at 13:51, Alexandre Bergel <abergel(a)dcc.uchile.cl> wrote: > >> Hello, >> >> I am sorry for the delay, last week was very chaotic :) > > No problem! This is super cool! > > Your report is amazing! Keep going! > >> >> >> VM >> --- >> - Work on Worker VM (allow VM to run in a worker thread). >> - Merged with headless trunk >> - Merged with AIO interrupt >> - Now can be tested (but still some interruptions missing) > > Just wondering. A worker VM will have its own image right? Can it be otherwise? I am just curious whether two VMs can run on the same image. Maybe this is a stupid question, but I am wondering :-) Worker VM just describes the capability of the VM to run in a worker thread (which means we can keep the main thread to other stuff, like running the event loop). Now, while I know there is some work/experiments to revive something like the hydra (running several images in one VM, or several copies of same image), I do not know the opposite :) And this Worker VM (we call it âogreâ, because it has two heads :P) will work with the regular image, nothing changed there. Esteban > > Cheers, > Alexandre >

Dec. 9, 2019

[Pharo 8.0] Build #1055: Adding halt to the list of captured exceptions when single stepping

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1055 was: SUCCESS. The Pull Request #5289 was integrated: "Adding halt to the list of captured exceptions when single stepping" Pull request url: https://github.com/pharo-project/pharo/pull/5289 Issue Url: https://github.com/pharo-project/pharo/issues/5280 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 9, 2019

[Pharo 8.0] Build #1054: 5339-Double-clicking-on-each-should-not-select-the-characte--only-each

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1054 was: FAILURE. The Pull Request #5341 was integrated: "5339-Double-clicking-on-each-should-not-select-the-characte--only-each" Pull request url: https://github.com/pharo-project/pharo/pull/5341 Issue Url: https://github.com/pharo-project/pharo/issues/5339 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 9, 2019