- Pharo-dev - lists.pharo.org

will be Cargo in Pharo 7?

by Peter UhnÃ¡k

Hi, I remember at ESUG someone saying that cargo ought to be added to P7 around the end of the year (2017/2018). But considering there was no development on Cargo in over half a year, this doesn't seem to be a likely scenario even in the near future. Are there any new plans in regards to cargo? Thanks, Peter

Feb. 11, 2018

[Pharo 7.0-dev] Build #524: 21309 Remove unnecessary "self run:" in SemaphoreTest

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

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

Feb. 11, 2018

[Pharo 7.0-dev] Build #523: 21313 Remove unnecessary "self run:" in DelayTest

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

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

Feb. 11, 2018

[Pharo 7.0-dev] Build #522: 21283 Improve TimeZone offset: comment

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

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

Feb. 11, 2018

[Pharo 7.0-dev] Build #521: 21282 Use "utilities" category in FileStream

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

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

Feb. 11, 2018

Re: [Pharo-dev] About method comments

by lb

Hi, Stef I have an idea for this problem, 1. method should have it's comment like class comment 2. method comment has two versions, one for developer another for reader 3. developder's comment will be saved in source or changes file 4. reader's comment will be saved in its own file 5. system browser can load reader's comment of method when you want to read or write reader can write his comment using his native language, we can share all reader's comments on internet. Best regards Bing Liang

Feb. 11, 2018

Re: [Pharo-dev] Iceberg experience report - synchronising README change made on github

by Ben Coman

On 11 February 2018 at 02:28, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > > > P.P.S. I think more thought needs to be given to whether mixing > > updates from both the remote and disk working directory in the one > > pane is beneficial? > > As an alternative, perhaps some side-scrolling GTInspector-like panes > > Image <--> Working Directory <--> Remote <--> Server(github) > > would better represent the git model. > > Or maybe statically position those panes in one window with buttons on > > directed lines showing which way and how far a commit moves when that > > button is pushed. > > > I was saying to esteban that the UI should let the user understand > where the code is so I like you > > > Image <--> Working Directory <--> Remote <--> Server(github) > > Mine was > > > Image <--> Local repository <--> Remote > > Stef > > Actually the fourth one might be redundant. The way you find out about the fourth one is you Fetch into the third one. cheers -ben

Feb. 11, 2018

[Pharo 7.0-dev] Build #520: 21280 Remove double dots in #cleanUpChangeSetForClassNames:

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

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

Feb. 10, 2018

[Pharo 7.0-dev] Build #519: 21277 Improve comment for byteToUnicodeSpec and typo fix

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

There is a new Pharo build available! The status of the build #519 was: SUCCESS. The Pull Request #831 was integrated: "21277 Improve comment for byteToUnicodeSpec and typo fix" Pull request url: https://github.com/pharo-project/pharo/pull/831 Issue Url: https://pharo.fogbugz.com/f/cases/21277 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 10, 2018

[Pharo 7.0-dev] Build #518: 21268 Cleanup AST-Tests-Core package

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

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

Feb. 10, 2018