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

[Pharo 8.0] Build #133: 2803-parseErrorNode-should-fill-value-for-the-case-of-expecting-a-
by ci-pharo-ci-jenkins2＠inria.fr March 13, 2019

March 13, 2019

There is a new Pharo build available! The status of the build #133 was: SUCCESS. The Pull Request #2804 was integrated: "2803-parseErrorNode-should-fill-value-for-the-case-of-expecting-a-" Pull request url: https://github.com/pharo-project/pharo/pull/2804 Issue Url: https://pharo.fogbugz.com/f/cases/2803 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #132: recoverRub2Client
by ci-pharo-ci-jenkins2＠inria.fr March 12, 2019

March 12, 2019

There is a new Pharo build available! The status of the build #132 was: SUCCESS. The Pull Request #2789 was integrated: "recoverRub2Client" Pull request url: https://github.com/pharo-project/pharo/pull/2789 Issue Url: https://pharo.fogbugz.com/f/cases/recoverRub2Client Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #131: 2797-Fix-comment-on-OSWindow--startTextInput
by ci-pharo-ci-jenkins2＠inria.fr March 12, 2019

March 12, 2019

There is a new Pharo build available! The status of the build #131 was: SUCCESS. The Pull Request #2798 was integrated: "2797-Fix-comment-on-OSWindow--startTextInput" Pull request url: https://github.com/pharo-project/pharo/pull/2798 Issue Url: https://pharo.fogbugz.com/f/cases/2797 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #130: 2546 Small cleanup UFFI to better distinguish architecture type
by ci-pharo-ci-jenkins2＠inria.fr March 12, 2019

March 12, 2019

There is a new Pharo build available! The status of the build #130 was: FAILURE. The Pull Request #2547 was integrated: "2546 Small cleanup UFFI to better distinguish architecture type" Pull request url: https://github.com/pharo-project/pharo/pull/2547 Issue Url: https://pharo.fogbugz.com/f/cases/2546 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #153: Fix comment on OSWindow >> startTextInput
by ci-pharo-ci-jenkins2＠inria.fr March 12, 2019

March 12, 2019

There is a new Pharo build available! The status of the build #153 was: FAILURE. The Pull Request #2781 was integrated: "Fix comment on OSWindow >> startTextInput" Pull request url: https://github.com/pharo-project/pharo/pull/2781 Issue Url: https://pharo.fogbugz.com/f/cases/patch Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #129: 2777-classbuilder-copyClassSlotsFromExistingClass-needs-to-be-done-by-the-classInstaller-by-default
by ci-pharo-ci-jenkins2＠inria.fr March 12, 2019

March 12, 2019

There is a new Pharo build available! The status of the build #129 was: SUCCESS. The Pull Request #2778 was integrated: "2777-classbuilder-copyClassSlotsFromExistingClass-needs-to-be-done-by-the-classInstaller-by-default" Pull request url: https://github.com/pharo-project/pharo/pull/2778 Issue Url: https://pharo.fogbugz.com/f/cases/2777 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #128: 2751-rename-RBBLintRuleTests-to-RBBLintRuleTestData-and-add-comment
by ci-pharo-ci-jenkins2＠inria.fr March 12, 2019

March 12, 2019

There is a new Pharo build available! The status of the build #128 was: FAILURE. The Pull Request #2758 was integrated: "2751-rename-RBBLintRuleTests-to-RBBLintRuleTestData-and-add-comment" Pull request url: https://github.com/pharo-project/pharo/pull/2758 Issue Url: https://pharo.fogbugz.com/f/cases/2751 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Pharo Consortium New Academic Member: CIRAD
by Marcus Denker March 11, 2019

March 11, 2019

The Pharo Consortium is very happy to announce that CIRAD has joined the Consortium as an Academic Member. About - CIRAD, the French Agricultural Research Centre for International Development: https://www.cirad.fr/en/home-page - 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

5 5

[Pharo 8.0] Build #127: 2740-do-not-zap-method-dict-when-making-classes-obsolete
by ci-pharo-ci-jenkins2＠inria.fr March 11, 2019

March 11, 2019

There is a new Pharo build available! The status of the build #127 was: SUCCESS. The Pull Request #2741 was integrated: "2740-do-not-zap-method-dict-when-making-classes-obsolete" Pull request url: https://github.com/pharo-project/pharo/pull/2741 Issue Url: https://pharo.fogbugz.com/f/cases/2740 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Esteban's ChangeLog week of 4 March 2019
by estebanlm＠gmail.com March 11, 2019

March 11, 2019

Hello! This is my weekly ChangeLog, from 4 March 2019 to 10 March 2019. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=4/3/2019&to=10/3/2019 ChangeLog ========= 6 March 2019: ------------- * I spent last two days trying approaches to make the introduction of +Application+ concept less intrusive. Thing is, since several applications can be alive at the same time (in general at least two: Pharo and the application the user is developing, but there can be more), when you create a window, is mandatory to know the application it belongs to. And this is a problem. Why? Well, because there are two ways to do it: It can be: ---- MyWindowClass newApplication: myApplication. ---- or: ---- myApplication new: MyWindowClass. ---- And well... both approaches require that you are in possesion of an application when you create a window. In an application of certain complexity (not to talk about Pharo complexity itself), this can be a problem (hello, singletons!). I explored the approach of having one active application at a time... but what happens when you are running application A and you need to pop a debugger? How to choose the right application? After some consideration, I came to the conclusion that is not possible, and that decision needs to be binded to the development itself. So, how to solve this? Is a matter of each application. * It is possible for some applications to pass the application between components. One can arwe UI decisions need to be taken at UI level, and is fine to have the application available at that level. * Is possible to have *for your application* a "runningApplication"... a class variable in your SpecApplication override. This is a singleton, yes, but sometimes you need it... Maybe Pharo will go this way. 4 March 2019: ------------- * Today I completed the first step on the introduction of +Application+ for Spec2. As we have told, an application is the entry point of any Spec Application. It will handle the creation and flow of windows and the resources used by it (long term goal: no more UIManager, UITheme, ThemeIcons and other singletons that pollute the system). Anyway, for now I just managed to introduce a generic application and refactored the +ComposablePresenter+, extracting the window functionality from them and moving it to a default +Application+. It sounds simple, but it was a big change. A diagram of how this has changed: ---- Before: ComposablePresenter -> WindowPresenter \ ComposablePresenter* ---- ---- Now: Application -> WindowPresenter -> ComposablePresenter -> ComposablePresenter* ---- This way of handling windows allows a tight control of what is open and in what order, and a way to handle resources other tghan a singleton in the system. cheers! Esteban

3 2