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

[ANN] Iceberg 1.5.7 (pharo6 is back)
by Guillermo Polito Feb. 18, 2019

Feb. 18, 2019

Hi all, I'm on vacations, so I've produced a new patch version of Iceberg :). This version restores compatibility with Pharo6, which was broken since latest changes done for Pharo7 64bit support. https://github.com/pharo-vcs/iceberg/releases/tag/v1.5.7 I hope people still using Pharo6 find this useful. You should be able now to use again the update script to use latest iceberg on it. I've updated the doc to point to the latest supported version: "load iceberg"Metacello new baseline: 'Iceberg'; repository: 'github://pharo-vcs/iceberg:v1.5.?'; onWarningLog; load. On this same direction, we have been discussing that v1.5.* will be the latest minor version supporting Pharo6. Still, we will keep integrating bugfixes and patches as they come. New versions (>= 1.6) will host the new features and will be available and maintained for both the stable Pharo7 and the in-development Pharo8 versions. Enjoy, Guille

1 0

[Pharo 8.0] Build #87: Fix `Week>>year:week:` to return a correct ISO week (starting on Monday)
by ci-pharo-ci-jenkins2＠inria.fr Feb. 18, 2019

Feb. 18, 2019

There is a new Pharo build available! The status of the build #87 was: FAILURE. The Pull Request #2508 was integrated: "Fix `Week>>year:week:` to return a correct ISO week (starting on Monday)" Pull request url: https://github.com/pharo-project/pharo/pull/2508 Issue Url: https://pharo.fogbugz.com/f/cases/2455 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Esteban's ChangeLog week of 11 February 2019
by estebanlm＠gmail.com Feb. 18, 2019

Feb. 18, 2019

Hello! This is my weekly ChangeLog, from 11 February 2019 to 17 February 2019. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=11/2/2019&to=17/2/2019 ChangeLog ========= 14 February 2019: ----------------- * Small fix-a-day: [https://github.com/pharo-project/pharo/pull/2530](https://github.com/pharo-… (fix some tonel tests failing) cheers! Esteban

1 0

[Ann] TelePharo and PharoThings adopted for Pharo 7
by Denis Kudriashov Feb. 18, 2019

Feb. 18, 2019

Hi. I released new versions of TelePharo (v0.3.0) and PharoThings (v0.2.3) adopted for Pharo 7 changes. PharoThings also includes new features from Alex Oliveira: - Raspberry model B3 - water alarm example And few models of Arduino from @gaterfy. Best regards, Denis

2 2

[Pharo 8.0] Build #86: 2579-Update-deleteAll-comments
by ci-pharo-ci-jenkins2＠inria.fr Feb. 17, 2019

Feb. 17, 2019

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

1 0

[Pharo 8.0] Build #85: 2552 Lint problem in #allUnreferencedInstanceVariables
by ci-pharo-ci-jenkins2＠inria.fr Feb. 16, 2019

Feb. 16, 2019

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

1 0

[Pharo 8.0] Build #84: 2571-RBPatternWrapperBlockNode-missing-sentMessages
by ci-pharo-ci-jenkins2＠inria.fr Feb. 16, 2019

Feb. 16, 2019

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

1 0

[Pharo 8.0] Build #83: 2562 Remove unused cache from TermInfoCharacter
by ci-pharo-ci-jenkins2＠inria.fr Feb. 16, 2019

Feb. 16, 2019

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

1 0

[Pharo 8.0] Build #82: 2554 Epicea: EpApplyPreviewer sourceEntries and logBrowserModel ivars not used
by ci-pharo-ci-jenkins2＠inria.fr Feb. 16, 2019

Feb. 16, 2019

There is a new Pharo build available! The status of the build #82 was: FAILURE. The Pull Request #2555 was integrated: "2554 Epicea: EpApplyPreviewer sourceEntries and logBrowserModel ivars not used" Pull request url: https://github.com/pharo-project/pharo/pull/2555 Issue Url: https://pharo.fogbugz.com/f/cases/2554 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

DisplayableObject
by Pavel Krivanek Feb. 16, 2019

Feb. 16, 2019

Hi Stef, I think that the inclusion of DisplayableObject or something like that will not help in better system design. The only thing that should really know about how to generate forms for icons, should be the UI framework. Imagine that we will want to use something like GTK framework with vector icons. The model classes should ideally never produce icons themselves. We should have maybe some class, an icon description. In the standard case, it will only hold the selector for the icon, but then it may add some additional data (like information about the small progress bar embedded in the icon). In the worst case it could provide as an additional property the form for the icon but then it will limit to use such thing effectively with other UI frameworks (like HTML rendering). If we will add a DisplayableObject, we will only make easier to make models that are not strictly separated from the UI. Cheers, -- Pavel

2 1