June 2020 - Pharo-dev - lists.pharo.org

[Pharo 9.0] Build #354: Move Variables to Kernel

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

There is a new Pharo build available! The status of the build #354 was: SUCCESS. The Pull Request #6545 was integrated: "Move Variables to Kernel" Pull request url: https://github.com/pharo-project/pharo/pull/6545 Issue Url: https://github.com/pharo-project/pharo/issues/MoveVariablesToKernel Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 10, 2020

[Pharo 9.0] Build #353: 6541-defaultTimeout-has-no-senders-The-method-for-tests-is-called-defaultTimeLimit

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

There is a new Pharo build available! The status of the build #353 was: FAILURE. The Pull Request #6543 was integrated: "6541-defaultTimeout-has-no-senders-The-method-for-tests-is-called-defaultTimeLimit" Pull request url: https://github.com/pharo-project/pharo/pull/6543 Issue Url: https://github.com/pharo-project/pharo/issues/6541 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 10, 2020

[Pharo 9.0] Build #352: remove-morphic-dependency-on-fonts

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

There is a new Pharo build available! The status of the build #352 was: SUCCESS. The Pull Request #6542 was integrated: "remove-morphic-dependency-on-fonts" Pull request url: https://github.com/pharo-project/pharo/pull/6542 Issue Url: https://github.com/pharo-project/pharo/issues/remove Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 10, 2020

[Pharo 9.0] Build #351: fix-dependency-freetype-morphic

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

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

June 10, 2020

Fwd: Help Needed! Survey on developer knowledge of Breakpoints/Watchpoints

by Thomas Dupriez

Hi all, As part of a research work on watchpoints, we are setting up a survey to gauge the general knowledge developers have on breakpoints/watchpoints. It should take around 10 minutes to complete. Here is the link to participate if you would be so kind: https://forms.gle/eK4HFvU1YNZZkiaHA If you are interested in the results, you can check the box at the end of the survey and we will send you feedback on the results of the survey. Additionally, we are going to set up a controlled experiment to evaluate the effectiveness of a new type of watchpoints we are developing for Pharo. The gist of it is that we will observe participants hunt some bugs, with and without the new tool, and see if their performance improve. So, if you know how to program in Pharo, and would be willing to participate, there is a question in the survey to tell us you are interested. We will get research data, and you will get a new debugging tool in Pharo. So it's a win-win. That's it! Thanks for your time! And extra thanks if you take the survey or consider participating in the experiment! Thomas Dupriez This research work is conducted by: - Eduardo A. Fontana, UniversitÃ© du QuÃ©bec Ã Chicoutimi, Canada. - Thomas Dupriez, Univ. Lille, France. And is supervised by: - Fabio Petrillo, UniversitÃ© du QuÃ©bec Ã Chicoutimi, Chicoutimi, QuÃ©bec, Canada. - Steven Costiou, Inria Lille, France. - *Yann-GaÃ«l GuÃ©hÃ©neuc*, Concordia University, Montreal, Quebec, Canada. - *StÃ©phane Ducasse*, Inria Lille, France.

June 10, 2020

[Pharo 9.0] Build #350: 6530-Job-progress-bar-is-under-the-bar

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

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

June 10, 2020

[Pharo 9.0] Build #349: 6527-Rule-Super-and-Self-Messages-sent-but-not-implemented-is-bogus

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

There is a new Pharo build available! The status of the build #349 was: FAILURE. The Pull Request #6535 was integrated: "6527-Rule-Super-and-Self-Messages-sent-but-not-implemented-is-bogus" Pull request url: https://github.com/pharo-project/pharo/pull/6535 Issue Url: https://github.com/pharo-project/pharo/issues/6527 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 10, 2020

[Pharo 9.0] Build #348: Unify Slots and LiteralVariable in single hierarchy

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

There is a new Pharo build available! The status of the build #348 was: SUCCESS. The Pull Request #6522 was integrated: "Unify Slots and LiteralVariable in single hierarchy" Pull request url: https://github.com/pharo-project/pharo/pull/6522 Issue Url: https://github.com/pharo-project/pharo/issues/variableRefactor Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 10, 2020

[Pharo 9.0] Build #347: [Disable Flaky Tests] Disable two Zinc flaky tests

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

There is a new Pharo build available! The status of the build #347 was: SUCCESS. The Pull Request #6497 was integrated: "[Disable Flaky Tests] Disable two Zinc flaky tests" Pull request url: https://github.com/pharo-project/pharo/pull/6497 Issue Url: https://github.com/pharo-project/pharo/issues/disableZnFlakyTests Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 10, 2020

Re: [Pharo-dev] should doubleclicking on symbol select # too?

by Chris Muller

Symbols are often used as arguments to #perform:, I don't know if Pharo ignores the initial hashmark (#) to allow browsing implementors but, if not, that could be a reason.. :) - Chris On Tue, Jun 9, 2020 at 2:26 PM StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi > > I would like to know what you think about the doubleclick selection on > symbol? > Right now > #foo selection will only select foo and I do not see why this is positif. > > In the past I fixed that the selection of :each selects the : was NOT > selected too so that we can access the value of the argument in a single > click > and now it is so good that we do not even see it. > So may we should do the same for #foo but in the other way. > > S. > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr / http://www.pharo.org > 03 59 35 87 52 > Assistant: Aurore Dalle > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France > >

June 10, 2020