Re: [Pharo-dev] PharoLauncher : Image version determination error

Hi Julien, On Mon, 20 Aug 2018 at 18:22, Julien wrote: > > When starting the image by hand in normal mode (like this): > > "/Users/julien/Documents/Pharo/vms/private/68021/Pharo.app/Contents/MacOS/Pharo" > "/Users/julien/Documents/Pharo/images/DrTest/DrTest.image » > > The image starts but I get

[Pharo-dev] [Pharo 7.0-dev] Build #1185: 22347-Prama-ivar-keyword-should-be-selector

There is a new Pharo build available! The status of the build #1185 was: SUCCESS. The Pull Request #1705 was integrated: "22347-Prama-ivar-keyword-should-be-selector" Pull request url: https://github.com/pharo-project/pharo/pull/1705 Issue Url: https://pharo.fogbugz.com/f/cases/22347 Bu

[Pharo-dev] [Pharo 7.0-dev] Build #1184: 22349-add-test-for-argsAsArray

There is a new Pharo build available! The status of the build #1184 was: FAILURE. The Pull Request #1706 was integrated: "22349-add-test-for-argsAsArray" Pull request url: https://github.com/pharo-project/pharo/pull/1706 Issue Url: https://pharo.fogbugz.com/f/cases/22349 Build Url: http

[Pharo-dev] [Pharo 7.0-dev] Build #1183: 22327-Add-a-rule-to-check-the-use-of-printString-inside-printOnaStream

There is a new Pharo build available! The status of the build #1183 was: SUCCESS. The Pull Request #1691 was integrated: "22327-Add-a-rule-to-check-the-use-of-printString-inside-printOnaStream" Pull request url: https://github.com/pharo-project/pharo/pull/1691 Issue Url: https://pharo.f

[Pharo-dev] [Pharo 7.0-dev] Build #1182: 22330-PluggableSliderMorph-does-not-respect-theme-

There is a new Pharo build available! The status of the build #1182 was: SUCCESS. The Pull Request #1694 was integrated: "22330-PluggableSliderMorph-does-not-respect-theme-" Pull request url: https://github.com/pharo-project/pharo/pull/1694 Issue Url: https://pharo.fogbugz.com/f/cases/2

[Pharo-dev] [Pharo 7.0-dev] Build #1181: 22346-mustBeBooleanDeOptimizeIn-needs-to-clean-semantic-annotation-before-recompile

There is a new Pharo build available! The status of the build #1181 was: FAILURE. The Pull Request #1704 was integrated: "22346-mustBeBooleanDeOptimizeIn-needs-to-clean-semantic-annotation-before-recompile" Pull request url: https://github.com/pharo-project/pharo/pull/1704 Issue Url: ht

[Pharo-dev] Pharo and Docker (some steps)

For those interested in Docker: I recently played with Pharo and Docker and summarized some of my steps in a small tutorial in my Pharo wiki: http://wiki.astares.com/pharo/613 There is also a page following Mike Filonovs suggestions on the Pharo docker file: http://wiki.astares.com/ph

[Pharo-dev] [Pharo 7.0-dev] Build #1180: 22308-Cleaning-baseClassclassClass-leftovers

There is a new Pharo build available! The status of the build #1180 was: SUCCESS. The Pull Request #1689 was integrated: "22308-Cleaning-baseClassclassClass-leftovers" Pull request url: https://github.com/pharo-project/pharo/pull/1689 Issue Url: https://pharo.fogbugz.com/f/cases/22308 B

[Pharo-dev] [Pharo 7.0-dev] Build #1179: 22338 Tag Kernel Manifests

There is a new Pharo build available! The status of the build #1179 was: SUCCESS. The Pull Request #1697 was integrated: "22338 Tag Kernel Manifests" Pull request url: https://github.com/pharo-project/pharo/pull/1697 Issue Url: https://pharo.fogbugz.com/f/cases/22338 Build Url: https://

[Pharo-dev] [Pharo 7.0-dev] Build #1178: 22345 Tag Manifests in IssueTracking and IssueTracking-Tests

There is a new Pharo build available! The status of the build #1178 was: SUCCESS. The Pull Request #1703 was integrated: "22345 Tag Manifests in IssueTracking and IssueTracking-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/1703 Issue Url: https://pharo.fogbugz.com

Re: [Pharo-dev] A new rule to implement in Pharo ?

Thanks Marcus, Guille. I look at it. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

[Pharo-dev] [Pharo 7.0-dev] Build #1177: 22339 Cleanup canZapMethodDictionary

There is a new Pharo build available! The status of the build #1177 was: FAILURE. The Pull Request #1698 was integrated: "22339 Cleanup canZapMethodDictionary" Pull request url: https://github.com/pharo-project/pharo/pull/1698 Issue Url: https://pharo.fogbugz.com/f/cases/22339 Build Url:

Re: [Pharo-dev] Reducing the cost of documentation

Hi Alistair, I don't think the contribution process hold people back from writing documentation since providing a contribution is easy to do now (see [1] and [2]). And (even when more cumbersome) I like the review process - as it helped several times in the past to discuss contributions or even