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

[Pharo 8.0] Build #408: 3698-Improve-LastSpacePosition-comment-in-class-String

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

There is a new Pharo build available! The status of the build #408 was: SUCCESS. The Pull Request #3699 was integrated: "3698-Improve-LastSpacePosition-comment-in-class-String" Pull request url: https://github.com/pharo-project/pharo/pull/3699 Issue Url: https://github.com/pharo-project/pharo/issues/3698 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 29, 2019

[Pharo 8.0] Build #407: More improves in the speed of Spotter.

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

There is a new Pharo build available! The status of the build #407 was: FAILURE. The Pull Request #3694 was integrated: "More improves in the speed of Spotter." Pull request url: https://github.com/pharo-project/pharo/pull/3694 Issue Url: https://github.com/pharo-project/pharo/issues/more Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 29, 2019

[Pharo 8.0] Build #406: 3663-Integrate-Spec-2

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

There is a new Pharo build available! The status of the build #406 was: SUCCESS. The Pull Request #3667 was integrated: "3663-Integrate-Spec-2" Pull request url: https://github.com/pharo-project/pharo/pull/3667 Issue Url: https://github.com/pharo-project/pharo/issues/3663 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 29, 2019

[Pharo 8.0] Build #405: 3661-simplify-allUnreferencedClassVariables

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

There is a new Pharo build available! The status of the build #405 was: FAILURE. The Pull Request #3691 was integrated: "3661-simplify-allUnreferencedClassVariables" Pull request url: https://github.com/pharo-project/pharo/pull/3691 Issue Url: https://github.com/pharo-project/pharo/issues/3661 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 29, 2019

[Pharo 8.0] Build #404: fixed a typo "runn" -> "run"

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

There is a new Pharo build available! The status of the build #404 was: FAILURE. The Pull Request #3697 was integrated: "fixed a typo "runn" -> "run"" Pull request url: https://github.com/pharo-project/pharo/pull/3697 Issue Url: https://github.com/pharo-project/pharo/issues/patch Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 29, 2019

Re: [Pharo-dev] A small game: do one trivial improvement every day

by Marcus Denker

> > Trivial improvement of the day: > > simplify #allSelectorsInProtocol: > https://github.com/pharo-project/pharo/pull/3647 > has been merged. > > > Trivial thing to do for someone else: > > #zapAllMethods can be removed > https://github.com/pharo-project/pharo/issues/3656 > was done (not by me!) and merged! Trivial thing done today: simplify allUnreferencedClassVariables https://github.com/pharo-project/pharo/issues/3661 this is a nice example how other trivial unimportant changes make things trivial that where not trivial before. After - adding #isReferenced for class variables (https://github.com/pharo-project/pharo/pull/3653) - adding #allClassVariables for classes (https://github.com/pharo-project/pharo/pull/3658) this was trivial. So I guess doing trivial things (that you might think are not important because they are oh so trivial) actually have the effect to make something trivial that was not trivial before? That is oddâ¦ Trivial thing for someone else to do: fix typo in Welcome bot message: ârunnâ https://github.com/pharo-project/pharo/issues/3696 One of the welcome bot messages has a typo: ârunn" should be ârun" This needs to be fixed here: https://github.com/pharo-project/pharo/blob/Pharo8.0/.github/config.yml the file can be edited right from the GitHub interface Marcus

June 28, 2019

[Pharo 8.0] Build #403: 3656-zapAllMethods-can-be-removed

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

There is a new Pharo build available! The status of the build #403 was: FAILURE. The Pull Request #3689 was integrated: "3656-zapAllMethods-can-be-removed" Pull request url: https://github.com/pharo-project/pharo/pull/3689 Issue Url: https://github.com/pharo-project/pharo/issues/3656 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 28, 2019

Re: [Pharo-dev] Loading project with Pharo

by Jannik Laval

Interesting, I will try that. Cheers, > Le 27 juin 2019 Ã 16:59, Christopher Fuhrman <christopher.fuhrman(a)inria.fr> a Ã©crit : > > On Thu, 27 Jun 2019 at 16:31, Ben Coman <btc(a)openinworld.com <mailto:btc@openinworld.com>> wrote: > > > On Thu, 27 Jun 2019 at 21:41, Jannik Laval <jannik.laval(a)gmail.com <mailto:jannik.laval@gmail.com>> wrote: > Dear pharoers, > > I use Pharo in Windows 10 and MacOS. > I find a big difference of loading time between the 2 systems. > > For loading Moose for example, In MacOS, it takes few minutes, but in Windows 10 it takes more than 15 minutes. > Also when I load Voyage, in MacOS, all loads correctly, but on Windows the path length is too long and generate an error. > > I expect the repo is in FIleTree format which has two problems on Windows: > * "file per method" produces a massive number of small files which the system struggles with > * long pathnames exceed Windows 256 character limit. > > Tonel "file per class" format was designed to resolve both these problems on Windows (IIUC). > > > There is also the Windows Defender (virus) scanner that wants to look at all the new files coming down (you'll see it chewing more than 30% of the CPU when you pull down Moose). You can luckily create Exclusions for your Pharo image directory, or the Pharo.exe process. That helps a lot I found. > > Cheers, > > Cris

June 28, 2019

[Pharo 8.0] Build #402: Cleanup refactoring tests

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

There is a new Pharo build available! The status of the build #402 was: SUCCESS. The Pull Request #3687 was integrated: "Cleanup refactoring tests" Pull request url: https://github.com/pharo-project/pharo/pull/3687 Issue Url: https://github.com/pharo-project/pharo/issues/FixTestsRefactoring Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 28, 2019

[Pharo 8.0] Build #401: 3652-we-have-isReferenced-for-Behavior-add-the-same-to-Variables

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

There is a new Pharo build available! The status of the build #401 was: FAILURE. The Pull Request #3653 was integrated: "3652-we-have-isReferenced-for-Behavior-add-the-same-to-Variables" Pull request url: https://github.com/pharo-project/pharo/pull/3653 Issue Url: https://github.com/pharo-project/pharo/issues/3652 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 28, 2019