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

Re: [Pharo-dev] [Pharo-users] TaskIt

by Torsten Bergmann

Santiago wrote: >What if we have links to all the groups in Pharo-project (pharo-misc, >pharo-processing, pharo-robotics, pharo-web) ? I can do the firsts steps if >we agree in here. Hi Santiago, yes - we should link the groups from the main "pharo-project" so they are easier to find. Here are the ones I know: 1. https://github.com/pharo-project 2. https://github.com/pharo-contributions (general community managed contributions) 3. https://github.com/pharo-rdbms (relational database support) 4. https://github.com/pharo-nosql (NoSQL database support) 5. https://github.com/pharo-sql (points to https://github.com/pharo-rdbms) Â 6. https://github.com/pharo-robotics (Robotics related) 7. https://github.com/pharo-brand (Brand Assets to do some marketing) 8. https://github.com/pharo-db (looks like offical DB stuff, but created by Todd Blanchard to assemble some database projects) Not existing (yet), dont know why you need/mentioned them https://github.com/pharo-misc Â https://github.com/pharo-processingÂ https://github.com/pharo-we For TaskIt maybe you start in "pharo-contributions" and if Pharo has more projects in similar directions an own separate group could be created. I'm not sure if an own mailinglist other than "Pharo-users" makes sense but https://lists.pharo.org now also meanwhile got an additional "Pharo-iot" and "Workflow-engine" mailinglist. Thanks T.Â

Dec. 17, 2019

[Pharo 8.0] Build #1081: 5343-Inconsistency-in-the-rules-relating-to-checking-the-code-of-methods

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

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…

Dec. 17, 2019

Pharo TechTalk December 19th

by Marcus Denker

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

Dec. 17, 2019

Re: [Pharo-dev] [Pharo-users] TaskIt

by Santiago Bragagnolo

El mar., 17 dic. 2019 a las 9:40, Norbert Hartl (<norbert(a)hartl.name>) escribiÃ³: > Hi, > > > Am 16.12.2019 um 11:41 schrieb Santiago Bragagnolo < > santiagobragagnolo(a)gmail.com>: > > > > ï»¿ > > 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. > > > I was asking this myself for a long time. Then I just started to move > things to pharo-contributions because I could not come up with a better > idea. Iâm not convinced that having more organizations on github will help. > > > 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). > > > I personally wouldnât do it from the start. Usually this is kind of a > premature optimization to put groups and permissions and all of that on the > table. > If it comes to groups it comes to permissions and the management of them. > You might try to solve a problem that might not even have. But you put the > burden of managing memberships and permissions and that prevents > collaboration to some extent > > So my golden rule to this is that if you donât have real good reason to > add something like this organization, just donât. Wait until there is a > problem. At that point you know what problem you have and you might have an > appropriate idea how to solve it. This is very hard to do a priori. > wowowo, i never spoke about memberships nor access, it would be a nice reason to me to not do it hahahaha. I am speaking only about drawing a box where we put the discussions on processing. Ii am naming people is just to remark the fact that there is people not only interested on this, but also working on this, meaning that to have a place for having this punctual disussions could be nice (just as a way of organising the discussions and having only informtion relevant to the processing thing. Still, i am aware that when we organise like this we are not organising for that, losing some freedom, and adding a complexity when gathering general information). What if we have links to all the groups in Pharo-project (pharo-misc, pharo-processing, pharo-robotics, pharo-web) ? I can do the firsts steps if we agree in here. > But we need indeed a general approach how to handle that. Every time > someone asks me to be added to pharo-contributions Iâm thinking about if > the setup is ok. > > Norbert > > > 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. 17, 2019

[ANN] Next Pharo Sprint: Dec 20

by Marcus Denker

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>

Dec. 17, 2019

Re: [Pharo-dev] [Pharo-users] TaskIt

by Norbert Hartl

Hi, > Am 16.12.2019 um 11:41 schrieb Santiago Bragagnolo <santiagobragagnolo(a)gmail.com>: > > ï»¿ > 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. > I was asking this myself for a long time. Then I just started to move things to pharo-contributions because I could not come up with a better idea. Iâm not convinced that having more organizations on github will help. > 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). > I personally wouldnât do it from the start. Usually this is kind of a premature optimization to put groups and permissions and all of that on the table. If it comes to groups it comes to permissions and the management of them. You might try to solve a problem that might not even have. But you put the burden of managing memberships and permissions and that prevents collaboration to some extent So my golden rule to this is that if you donât have real good reason to add something like this organization, just donât. Wait until there is a problem. At that point you know what problem you have and you might have an appropriate idea how to solve it. This is very hard to do a priori. But we need indeed a general approach how to handle that. Every time someone asks me to be added to pharo-contributions Iâm thinking about if the setup is ok. Norbert > 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. 17, 2019

Re: [Pharo-dev] [Mm10s] 2019-12-16

by tesonep＠gmail.com

My report, some are the same than Esteban, as we work a lot together :D ### Last week: - (Pair Programming with Esteban) Modifying the TFFI callbacks to include information about the Smalltalk block in the plugin data structure. This improves the debugging experience and the detection of errors when a Callback in the image side is garbage collected. - (Pair Programming with Esteban) Compiling the Queue based ThreaddedFFI plugin to use the latest libffi version. This is required to build in Catalina. - (Pair Programming with Esteban) Adding synchronization code to correctly interrupt the AIO waiting idle loop. This is still work in progress as we have to test more scenarios. This modification allows us to extend enormously the idle time of the relinquish processor primitive without losing events nor delays. - (Pair Programming with Esteban) Fixing a glitch in GTK with the keyboard input and event handling when the GTK windows opened by Spec2 is the topmost of the application - Detection and fix of the GCC 8.3+ optimization glitch that prevented the built of the VM in newer Linux distributions. - Another iteration on the FreeTypeFont glitch issue. - Detecting all the requirements to use the Sista bytecode in the default image. This modification requires some changes in Fuel. There is a need for more changes in the debugger if we want to integrate full block closures. - Fixing small issues and reviewing PR for Pharo8 - Supporting Students in their modifications of the VM and experiments they are doing (Theo & Pierre here in Lille, and Federico in Buenos Aires): if you have problems just call :D. ### This week (starting 2019-12-16): - Pushing Pharo 8 release (Release Notes / PR / fixes) - Adding tests to the interruptable AIO and main thread worker of the headless VM. - Clean-up of code of the VM to allow to compile with MUSL and different libc implementations. This will allow us to run in Alpine Linux, improving the experience of Pharo running in containers. For doing so the correct way is to extend the debugging functions to allow different streams and outputs (today it is done through a hack, so we have to keep the behavior but implemented in a way that does not break the encapsulation of libc). - Working on GC tests with Guille. On Mon, Dec 16, 2019 at 11:00 AM Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > ### 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. > -- Pablo Tesone. tesonep(a)gmail.com

Dec. 17, 2019

[Pharo 8.0] Build #1080: 5372-Completion-failure-when-using-super-in-a-trait

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

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…

Dec. 17, 2019

[Pharo 8.0] Build #1079: Improving the FreeTypeCache mutex.

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

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…

Dec. 16, 2019

[Pharo 8.0] Build #1078: DebugSession modification for DebuggerSelector

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

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…

Dec. 16, 2019