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

Re: [Pharo-dev] Pharo8: Advance on Spec2 and Gtk3 backend

by Esteban Lorenzano

> On 1 Jul 2019, at 18:44, Alexandre Bergel <abergel(a)dcc.uchile.cl> wrote: > > Hi! > > Thanks for this wonderful effort! > >> The consequences of this are obvious: we can, if we need it, fallback to morphic if you need to do something the backend does not allows (Roassal, I talking about you). > > Why would you need to fallback to Morphic if you wish to use Roassal3? I donât. My idea is that you will be able to fallback to Bloc or to plain Athens as you need. Morphic was just the first component. Also, I imagine someone who has already something made an investment in morphic (like someone using Roassal2 extensively). Then he will be able to benefit of it too. > Believe me, we will put the necessary resources to have R3 working very smoothly with Gtk. As soon as you feel confident for us to play with, then we will focus on this. Oh, I believe you :) Esteban > > Enjoy your well-deserved holidays! > > Cheers, > Alexandre >

July 1, 2019

Pharo8: Advance on Spec2 and Gtk3 backend

by Esteban Lorenzano

Hi, Last couple of months I have been really busy moving forward (along with Cyril and Pablo, in different places of the roadmap) what will be the backbone of Pharo 8.0 tool development: Spec 2. I worked in a lot of things and somehow the weekly reports went missing (my mistake). Now Iâm going on holidays but I will take this week to announce/release/show what I have done latest weeks (then it does not accumulates so much and resuming the weekly report when Iâm back will be smoother). Anyway, this is the status of this parts: 1) Spec 2 has move into a less immature status, and we are arriving to a status of âinternal betaâ soon. For âinternal betaâ means the features we wanted to implement are there even if still with bugs and miss-behaviours). For this, in (very) short summary we passed through: - We made a pass on all Spec components and we deprecated some and added some others. - We introduced the concept of âtransmissionâ, to partially mimic what glamour was capable of doing in a very easy way. - We introduced 5 different layouts to replace the unique âdo-it-allâ older. - We introduced the concept âApplicationâ to handle window flow and application resources. And all this was already announced, but we have moved to a more stable phase now and this is ready to be stressed. Last version of this is already integrated on Pharo 8 (we renamed the prefix to Sp, so we avoid part of the migration pain). Other point where there was a lot of movement was in the Gtk3 backend. Work has been done for stability that will affect (positively) all the system, not just backend: for example in UFFI I needed to introduce the concept of NULL and the possibility to âcastâ numeric declarations. This is because in 64bit NULL != 0 (being 6 an int32), and because 0 != 0L (and many like that). So now you can have ffi invocations of the form: self ffiCall: #(void myFunction (NULL, (long)42)). And this will be correctly parsed on the different platforms. But overall, the Gtk3 backend is also in good shape and we will put it to be tested soon(â¢) :P (I estimated it was last week, but as always there were complications). One thing I think is interesting to talk about (because we needed to change a lot of things to make it work, much more than was expected at first) was one Gtk element that you will find interesting: GtkMorphView. Basically GtkMorphView allows you to put a morph (whatever you want) into a Gtk container (the Spec component to allow this is SpMorphPresenter). This allows you to do things like this: And as I said to Stef last week: I find this screenshot very sexy because what is showing is 4 simple button morphs behaving in sync with other Gtk3 components in an external window. The consequences of this are obvious: we can, if we need it, fallback to morphic if you need to do something the backend does not allows (Roassal, I talking about you). Of course, since this is our final target, there is a BlocPresenter also on the works. Iâm sure Pavel can share some sexier screenshots of what he is doing with this. A fun fact, that drives me to the next step is this: The GtkMorphView was working smoothly in windows but crashing immediately in macOS (I found it fun because is usually the opposite). I needed to make a âstop the worldâ and jump to work on it and it tooks a couple of weeks to just figure out what was happening (debugging this kind of things is always hard). And at the end I had an approximate guess: The problem was in a not-thread safe way to handle the display in the VM side. I took a breath to decide the solution and at the end I decided to take the easiest path but maybe more time consuming at the beginning: Since we are going to move to a âheadlessâ vm (which means do not initiate a display at all, unless demanded and through the image), I did not see the point on jump and fix a code very hard to understand and debug. Instead, we moved at the top of the backlog the âmove to headless vmâ and Pablo and me started to work on that. Now, there are problems associated to that (like event loops and that)â¦ but this is not anymore Spec2+Gtk3 and then it requires a new mail to be explained :) Esteban

July 1, 2019

Added a GitHub project board for Debugger related issue

by Marcus Denker

Hi, I added a Project Board for âDebugger and Debuggingâ: https://github.com/orgs/pharo-project/projects/23 <https://github.com/orgs/pharo-project/projects/23> To edit the board, one has to be a member of the organizion, if you are not but would like to edit: I can add you. Marcus

July 1, 2019

[ANN] Pharo Consortium New Academic Member: Universidad CatÃ³lica Boliviana - Cochabamba

by Marcus Denker

The Pharo Consortium is very happy to announce that IngenierÃa de Sistemas, Universidad CatÃ³lica Boliviana - Cochabamba has joined the Consortium as an Academic Member. About - IngenierÃa de Sistemas, Universidad CatÃ³lica Boliviana - Cochabamba https://www.ucbcba.edu.bo/ - Pharo Consortium: 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

July 1, 2019

[Pharo 8.0] Build #417: FAILURE

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

There is a new Pharo build available! The status of the build #417 was: FAILURE. Could not extract further issue information from commit message: Fixing the traits implementation. When there is a diamond definition of a slot, it should not be a conflict. Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 1, 2019

Re: [Pharo-dev] A small game: do one trivial improvement every day

by Marcus Denker

> On 1 Jul 2019, at 09:59, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 1 Jul 2019, at 08:45, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> For the ones I add for other to do I put the âEasyâ tag and add them to this GitHub project (kanban board): >> >> https://github.com/orgs/pharo-project/projects/8 >> > And two issue for someone to do: - allBehaviorsDo: can now use the cached allBehaviors https://github.com/pharo-project/pharo/issues/3726 simple, but quite some impact (we should of course refactor all the senders of allBehaviorsDo: later as they now can be transformed to use collection methods and be even faster then do:â¦) and a slightly harder one: add #whichMethodsReferTo: https://github.com/pharo-project/pharo/issues/3727 nearly all clients of thoroughWhichSelectorsReferTo: are interested in the methods, not the selector. we should add #whichMethodsReferTo: and rewrite the clients to use that instead. Marcus

July 1, 2019

Re: [Pharo-dev] A small game: do one trivial improvement every day

by Marcus Denker

> On 1 Jul 2019, at 08:45, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > For the ones I add for other to do I put the âEasyâ tag and add them to this GitHub project (kanban board): > > https://github.com/orgs/pharo-project/projects/8 > Small fix Friday: ============= 3700-simplify-allUnreferencedInstanceVariables https://github.com/pharo-project/pharo/pull/3701/files same idea as the class vars, now that variables are object, bit strings, we can implement it simply as: ^self allSlots reject: [:slot | slot isReferenced] (and it will returns object, that e.g. know the class they are declared in) Saturday ======= I did one of the simple ones posted the day before: 3630-small-cleanup-traits-in-Behaviour-isComposedBy-move-to-traits https://github.com/pharo-project/pharo/pull/3704 Then I did a small (one var added, two lines changed)l, but definitely not trivial improvement: SystemDictionary: add a cache for allBehaviors https://github.com/pharo-project/pharo/issues/3702 Right now SystemDictionary caches names, we should cache Objects instead. this is the first step. And it enables Sunday =================== speedup "implementors of https://github.com/pharo-project/pharo/pull/3711 With the allBehaviors cache, we can radically simplify (and speedup!) a lot of code used very very often. [#name implementors] bench before: "'69.688 per second'" after: "'119.385 per second'" The new implementation is this: SystemNavigation>>allImplementorsOf: aSelector "Answer all the methods that implement the message aSelector." ^self allBehaviors select: [:class | class includesSelector: aSelector] thenCollect: [:class | (class>>aSelector) methodReference ] This #allBehaviors cache will allow many more simplifications (check senders of #allBehaviorsDo:) e.g. for today, I did two as part of this (isUnsentMessage: and allPrimitiveMethods): https://github.com/pharo-project/pharo/pull/3725/files Marcus

July 1, 2019

Re: [Pharo-dev] A small game: do one trivial improvement every day

by Marcus Denker

For the ones I add for other to do I put the âEasyâ tag and add them to this GitHub project (kanban board): https://github.com/orgs/pharo-project/projects/8 <https://github.com/orgs/pharo-project/projects/8> > On 29 Jun 2019, at 18:11, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > > Can we define a tag for such issues ? > > > On Fri, Jun 28, 2019 at 9:37 PM Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: > > > > > Trivial improvement of the day: > > > > simplify #allSelectorsInProtocol: > > https://github.com/pharo-project/pharo/pull/3647 <https://github.com/pharo-project/pharo/pull/3647> > > > > has been merged. > > > > > > Trivial thing to do for someone else: > > > > #zapAllMethods can be removed > > https://github.com/pharo-project/pharo/issues/3656 <https://github.com/pharo-project/pharo/issues/3656> > > > > was done (not by me!) and merged! > > Trivial thing done today: > > simplify allUnreferencedClassVariables > https://github.com/pharo-project/pharo/issues/3661 <https://github.com/pharo-project/pharo/issues/3661> > > this is a nice example how other trivial unimportant changes make things trivial that where not trivial before. > After > - adding #isReferenced for class variables (https://github.com/pharo-project/pharo/pull/3653 <https://github.com/pharo-project/pharo/pull/3653>) > - adding #allClassVariables for classes (https://github.com/pharo-project/pharo/pull/3658 <https://github.com/pharo-project/pharo/pull/3658>) > > this was trivial. So I guess doing trivial things (that you might think are not important because they are oh so trivial) actually > have the effect to make something trivial that was not trivial before? That is oddâ¦ > > Trivial thing for someone else to do: > > fix typo in Welcome bot message: ârunnâ > https://github.com/pharo-project/pharo/issues/3696 <https://github.com/pharo-project/pharo/issues/3696> > > One of the welcome bot messages has a typo: ârunn" should be ârun" > > This needs to be fixed here: > > https://github.com/pharo-project/pharo/blob/Pharo8.0/.github/config.yml <https://github.com/pharo-project/pharo/blob/Pharo8.0/.github/config.yml> > > the file can be edited right from the GitHub interface > > > Marcus > > > > > -- > Serge Stinckwicâhâ > Int. Research Unit on Modelling/Simulation of Complex Systems (UMMISCO) > âSorbonne University (SU) > French National Research Institute for Sustainable Development (IRD)â > Uâniversity of YaoundÃ© Iâ, Cameroon > "Programs must be written for people to read, and only incidentally for machines to execute." > https://twitter.com/SergeStinckwich <https://twitter.com/SergeStinckwich> > â

July 1, 2019

[Pharo 8.0] Build #416: Cleanup System-BasicCommandLineHandler-Tests

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

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

July 1, 2019

[Pharo 8.0] Build #415: 3708-cleanup-SystemNavigationTest

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

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

July 1, 2019