- Pharo-dev - lists.pharo.org

[ANN] Pharo Consortium New Academic Member: Ryerson University

by Marcus Denker

The Pharo Consortium is very happy to announce that the Ryerson University has joined the Consortium as an Academic Member. About - Ryerson University: https://www.ryerson.ca <https://www.ryerson.ca/> - Pharo Consortium: http://consortium.pharo.org <http://consortium.pharo.org/> The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: - http://association.pharo.org <http://association.pharo.org/>

June 9, 2020

Re: [Pharo-dev] [Mm10s] 2020-06-08

by Sean P. DeNigris

tesonep(a)gmail.com wrote > - Missing parts in the Image to have Sista + FullBlockClosure. Yay! Thanks :) ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

June 8, 2020

Re: [Pharo-dev] [Pharo 9.0] Build #345: add-missing-method-uffi

by Sean P. DeNigris

ci-pharo-ci-jenkins2 wrote > Issue Url: https://github.com/pharo-project/pharo/issues/add The issue link in this report seems to be broken ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

June 8, 2020

[Pharo 9.0] Build #345: add-missing-method-uffi

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

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

June 8, 2020

[Pharo 9.0] Build #344: enable-full-block-closures

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

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

June 8, 2020

[Pharo 9.0] Build #343: 6500-Cleanups

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

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

June 8, 2020

Re: [Pharo-dev] [Mm10s] 2020-06-08

by tesonep＠gmail.com

### Last week: - Monday Holiday - Multiple images test runners - [VM] Writing tests for JIT generation - Idle VM with Esteban: Gtk - Missing parts in the Image to have Sista + FullBlockClosure. - Reviewing PR & Issues ### This week (starting 2020-06-08): - Releasing VM with LibGit 1.0.0 - Multiple images test runners - [VM] Writing tests for JIT generation - Idle VM with Esteban: Gtk On Mon, Jun 8, 2020 at 10:03 AM Esteban Lorenzano <estebanlm(a)netc.eu> wrote: > > > ### Last week: > > > * [Idle-VM] w/Pablo. Worker problem with delays > worker version was not interrupting the aio. We spent some time here and this was a non existing > problem at the end (but we found and fix a bug on Spec2-Gtk). > * [Idle-VM] problem when save&quit image with gtk backend > fix a bug happening when application was shutting down and some events want still happen, who > causes a callback that is alredy discarded to be executed. > * [Idle-VM] new version of memory access > test, bench and merge of new memory access primitive > (lowcode didn't applied, finally) > * [spec2] preparation of a window box to make some tests there. > * [spec2] gtk backend now has an image-side based tree store, which allows much better > interoperability. Next task is to migrate the adaptors: list, table and treetable (not trivial, > but needed) > * [TFFI] added a new type: FFIBoolean32 to handle the fact that many libraries (in my case, > Gtk), do not use bool=8bit implementation. Now, users need to map their boolean (in my case, > gboolean) to this type by hand. I didn't find a better way to fix this issue :( > * [spec2] gtk backend now answers propertly to keyboard events in windows. > * [spec2] fix a (new) bug on GtkTreeView, because we do not need to unref stores manually. This > bug was introduced by my recent fix on GtkTreeView, which initialize method was not sending > super. > * [spec2] avoid the traverse of roots when releasing a GtkTreeDataStore (Gtk does that) > * [spec2] list/table/tree migrated to use the new GtkTreeDataStore (lots of simplifications, > specially on GtkTreeTableAdapter) > * [NewTools-Playground] bug: doit from toolbar does not uses interactionMode > * [Spec2-doc] Add style section (reference) to SpApplication > * [NewTools-Playground] bug: "implementors" is not working. I couldnât reproduce the problem. > Maybe is fixed now? > > ### This week (starting 2020-06-08): > > > - Mostly cleanups and re-organisations on Spec2 (preparing v0.7 for Pharo9) > - Preparing v0.1 of NewTools (also, to prepare an integration to Pharo9) > - Building VM on Fedora linux > - Testing Idle-VM on Windows > > > -- Pablo Tesone. tesonep(a)gmail.com

June 8, 2020

Re: [Pharo-dev] [Cuis-dev] PROPOSAL: UN-St (United Nations of Smalltalk)

by Jonathan van Alteren

Hi Sean, I just wanted to say that I share your vision about the need to unleash the true power of computing and evolving humanity (not just the mind, I hope). The Smalltalk community, in all its rich diversity, has so much potential. It deserves to grow and be united in collaboration, which I think could be helped by your proposal. I'm still very much a junior in Pharo and Smalltalk in general, and my time is very limited. I think others will be far better suited to support your initiative. However, you're welcome to send me a PM if you think I can help, it's always good to talk. Kind regards, Jonathan van Alteren Founding Member | Object Guild B.V. Sustainable Software for Purpose-Driven Organizations jvalteren(a)objectguild.com On 4 Jun 2020, 18:17 +0200, Sean DeNigris via Cuis-dev <cuis-dev(a)cuis-smalltalk.org>, wrote: > I believe that the Squeak/Pharo/Cuis communit(ies) share one very special thing, which most of the world has completely missed, and which the world sorely needs if the true power of computing to unleash and evolve the human mind is ever to be realized: a love and appreciation for personal technological augmentation/amplification available to all as represented by the Dynabook and/or its prototype software (Smalltalk as a concept, not any version/implementation e.g. Smalltalk-80). > > Like a few survivors after the sinking of Atlantis, we can pick up the remnants of this dream and resume marching toward the objective (or at least keep its memory alive until an auspicious time when it can be realized)â¦ or, like most groups of human beings throughout history who start with a common aim, we can bicker among ourselves about e.g. historical discrepancies, personal slights, and conflicting subgoals, and allow those squabbles to distract us and derail our primary mission. This would be disappointing but not surprising: it is how every war is started. > > I have contributed, hacked, conferenced, and visited with many members of our wider community for over a decade now and, maybe because I had the âluxuryâ of finding Smalltalk after some of the political lines had been well-drawn, I can clearly see that we are fundamentally united. I cringe every time I see cynical, caustic exchanges - both for my participating colleagues who are obviously in pain - probably exacerbated by their passion for our shared endevour - and for the counterproductive effect the antagonism is sure to have on our common goal. Virtually every exchange is between two people who I personally know to be good and competent. > > Here is my proposal: Letâs form an informal committee - a United Nations of Smalltalk if you will - including at least one member of each community, who will collaborate on cooperation between the dialects and mediate any friction before it boils over. > > Iâd be happy to participate, I guess as a representative of the Pharo community. Although I have no official role in the Pharo leadership, I have much of my professional life invested there. I often wish I had the time to keep all my projects compatible with Squeak, but I usually feel like Iâm barely keeping up as it is! > > I hope Iâm not alone in these feelings and look forward to the response of our community (most emphatically singular). This message is being cross-posted to Pharo-Dev, Squeak-Dev, and Cuis MLs (I think Iâm still a member of all three - fingers crossedâ¦) > > - Sean (DeNigris) > _______________________________________________ > Cuis-dev mailing list > Cuis-dev(a)cuis-smalltalk.org > http://cuis-smalltalk.org/mailman/listinfo/cuis-dev_cuis-smalltalk.org

June 8, 2020

[Mm10s] 2020-06-08

by Esteban Lorenzano

### Last week: * [Idle-VM] w/Pablo. Worker problem with delays worker version was not interrupting the aio. We spent some time here and this was a non existing problem at the end (but we found and fix a bug on Spec2-Gtk). * [Idle-VM] problem when save&quit image with gtk backend fix a bug happening when application was shutting down and some events want still happen, who causes a callback that is alredy discarded to be executed. * [Idle-VM] new version of memory access test, bench and merge of new memory access primitive (lowcode didn't applied, finally) * [spec2] preparation of a window box to make some tests there. * [spec2] gtk backend now has an image-side based tree store, which allows much better interoperability. Next task is to migrate the adaptors: list, table and treetable (not trivial, but needed) * [TFFI] added a new type: FFIBoolean32 to handle the fact that many libraries (in my case, Gtk), do not use bool=8bit implementation. Now, users need to map their boolean (in my case, gboolean) to this type by hand. I didn't find a better way to fix this issue :( * [spec2] gtk backend now answers propertly to keyboard events in windows. * [spec2] fix a (new) bug on GtkTreeView, because we do not need to unref stores manually. This bug was introduced by my recent fix on GtkTreeView, which initialize method was not sending super. * [spec2] avoid the traverse of roots when releasing a GtkTreeDataStore (Gtk does that) * [spec2] list/table/tree migrated to use the new GtkTreeDataStore (lots of simplifications, specially on GtkTreeTableAdapter) * [NewTools-Playground] bug: doit from toolbar does not uses interactionMode * [Spec2-doc] Add style section (reference) to SpApplication * [NewTools-Playground] bug: "implementors" is not working. I couldnât reproduce the problem. Maybe is fixed now? ### This week (starting 2020-06-08): - Mostly cleanups and re-organisations on Spec2 (preparing v0.7 for Pharo9) - Preparing v0.1 of NewTools (also, to prepare an integration to Pharo9) - Building VM on Fedora linux - Testing Idle-VM on Windows

June 8, 2020

[Pharo 9.0] Build #342: [Flaky Test] Rely on SUnit time limit in recursion stopper tests.

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

There is a new Pharo build available! The status of the build #342 was: FAILURE. The Pull Request #6501 was integrated: "[Flaky Test] Rely on SUnit time limit in recursion stopper tests. " Pull request url: https://github.com/pharo-project/pharo/pull/6501 Issue Url: https://github.com/pharo-project/pharo/issues/recursionStopperTests Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 8, 2020