- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #765: 21692-StdioStream-incorrectly-delegates-atEnd-and-position-to-file
by ci-pharo-ci-jenkins2＠inria.fr April 13, 2018

April 13, 2018

There is a new Pharo build available! The status of the build #765 was: SUCCESS. The Pull Request #1193 was integrated: "21692-StdioStream-incorrectly-delegates-atEnd-and-position-to-file" Pull request url: https://github.com/pharo-project/pharo/pull/1193 Issue Url: https://pharo.fogbugz.com/f/cases/21692 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #764: Fix Case 21686 Setting background images doesn't work on Pharo 7.0
by ci-pharo-ci-jenkins2＠inria.fr April 13, 2018

April 13, 2018

There is a new Pharo build available! The status of the build #764 was: SUCCESS. The Pull Request #1197 was integrated: "Fix Case 21686 Setting background images doesn't work on Pharo 7.0" Pull request url: https://github.com/pharo-project/pharo/pull/1197 Issue Url: https://pharo.fogbugz.com/f/cases/21686 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #763: 21691-update-iceberg-to-072
by ci-pharo-ci-jenkins2＠inria.fr April 13, 2018

April 13, 2018

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

1 0

Why can't we use * in protocol for package extension?
by Stephane Ducasse April 13, 2018

April 13, 2018

in calypso. * was simple and nice. Now if I create a protocol with a star it got eaten and no protocol will be created. Stef

5 14

[TechTalk] April 12: GIT with Iceberg
by Marcus Denker April 12, 2018

April 12, 2018

Hi, There next TechTalk will be April 12: GIT with Iceberg https://association.pharo.org/event-2797068 A regular chat about Pharo. Happens on Discord. The Tech talks are open to both members and non-members! Topic: GIT with Iceberg. Demo of improved UI We will send an information to all subscribers some hours before the talk starts.

4 4

TechTalk on Iceberg will start in 30min (link inside)
by Esteban Lorenzano April 12, 2018

April 12, 2018

here: https://www.youtube.com/estebanlorenzano/live <https://www.youtube.com/estebanlorenzano/live> see you there, Esteban

1 0

[Pharo 7.0-dev] Build #762: 21684-Integrate-Iceberg-0.7.1
by ci-pharo-ci-jenkins2＠inria.fr April 12, 2018

April 12, 2018

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

1 0

[Pharo 7.0-dev] Build #761: 21684-Integrate-Iceberg-0.7.1
by ci-pharo-ci-jenkins2＠inria.fr April 12, 2018

April 12, 2018

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

1 0

How to remove the extra protocol in Calypso
by Stephane Ducasse April 12, 2018

April 12, 2018

Hi There are too much information by default I'm overhelmed. I would like to remove the following protocols critiques

1 3

Why String do not implement #displayString?
by Denis Kudriashov April 12, 2018

April 12, 2018

Hi. According to the comment of #displayString it should be used as default textual representation of objects in the UI: "While printString is about to give a detailled information about an object, displayString is a message that should return a short string-based representation to be used by list and related UI frameworks. By default, simply return printString." "asString should not be implemented in Object, and kept for conversion between strings, symbols, text and characters." But String itself does not respect this message: 'some string' displayString " ==> '''someString''' " Is it bug? Or is there any reason for this? Best regards, Denis

5 13