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

TaskIt

by Santiago Bragagnolo

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

Dec. 16, 2019

[Mm10s] 2019-12-16

by Esteban Lorenzano

### 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.

Dec. 16, 2019

Re: [Pharo-dev] [ANN] Grouper

by Alexandre Bergel

Pretty cool! Alexandre http://bergel.eu > Le 9 dÃ©c. 2019 Ã 11:10, Julien Delplanque <julien.delplanque(a)inria.fr> a Ã©crit : > > ï»¿ > 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. 15, 2019

Re: [Pharo-dev] [ANN] EventRecorder legacy put online

by Alexandre Bergel

Hi! I am not sure to understand. A few weeks ago roassal was updated to not depend on the eventrecorder. Cheers, Alexandre http://bergel.eu > Le 13 dÃ©c. 2019 Ã 08:48, Esteban Lorenzano <estebanlm(a)gmail.com> a Ã©crit : > > ï»¿Hi, > > For those who need the deprecated (and removed) GT-EventRecorder, I have put the original packages in pharo-contributions/EventRecorder (legacy branch). > > To load it, you just need to execute: > > Metacello new > repository: 'github://pharo-contributions/EventRecorder:legacy'; > baseline: 'EventRecorder'; > load. > > This way you may continue loading Roassal2 (or others) until they fix the baseline :) > > (Btw, installation will still fail because Matrix has been removedâ¦ but this one was indeed deprecated in P7 (is replaced by Array2D), a problem you can overcome by executing > > Array2D subclass: #Matrix > > Previous to load Roassal2. > > I hope this solves the problems causes lasts weeks. > > Cheers, > Esteban > > >

Dec. 15, 2019

[Pharo 8.0] Build #1077: Reload BlueInk

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

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

Dec. 15, 2019

Trait subclassResponsibility

by Ben Coman

#Background I got a critique... Replaces "a >= b and: [a <= c]" by "a between: b and: c. for my code... (location >= (1@1) and: [location <= (self size @ self size)]) To test, I tried... (2@2) between: (1@1) and: (5@5) but got... Instance of Point did not understand #between:and: which it seems reasonable it should have since Point does define #>= and #<= #Questions I see #between:and: defined for TComparable and thought I maybe that trait could be added to Point, except I see also that TComparable has three "subclassReponsibility" methods: #< ; #= ; #hash and I'm curious what is the effect of such methods being added to a class? cheers -ben

Dec. 15, 2019

[Pharo 8.0] Build #1076: execution counters sometimes produce errors when uninstalling

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

There is a new Pharo build available! The status of the build #1076 was: SUCCESS. The Pull Request #5382 was integrated: "execution counters sometimes produce errors when uninstalling" Pull request url: https://github.com/pharo-project/pharo/pull/5382 Issue Url: https://github.com/pharo-project/pharo/issues/5381 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 14, 2019

Pharo 8 on SqueakJS

by Pavel Krivanek

Hi, a small update of Pharo running of SqueakJS: https://pavel-krivanek.github.io/pharo8/pharo.html FileAttributes plugin and file support generally is still not in good shape but inspectors work now and the number of changes to the image was significantly reduced ( https://github.com/pavel-krivanek/pavel-krivanek.github.io/tree/master/phar… ) Cheers, -- Pavel

Dec. 14, 2019

[Pharo 9.0] Build #1: GTDebugger modification for DebuggerSelector

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

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

Dec. 14, 2019

[Pharo 8.0] Build #1075: GTDebugger modification for DebuggerSelector

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

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

Dec. 14, 2019