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

[Pharo 8.0] Build #563: simplify some lazy read accessors

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

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

July 25, 2019

Re: [Pharo-dev] Why do we have 2 VTermOutputDriver?

by ducasse

I do not remember but indeed cleanly this part is good. Stef > On 24 Jul 2019, at 22:54, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > > Hi, > > In the image we currently have two VTermOutputDriver. > > The second one is not used but I have the impression that it was a WIP. > > Does someone knows what it the state of this class? Should we remove the > second? Should the second be used instead of the first? > > -- > Cyril Ferlicot > https://ferlicot.fr >

July 25, 2019

[Pharo 8.0] Build #562: Fix recently-introduced portability problems

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

There is a new Pharo build available! The status of the build #562 was: FAILURE. The Pull Request #4090 was integrated: "Fix recently-introduced portability problems" Pull request url: https://github.com/pharo-project/pharo/pull/4090 Issue Url: https://github.com/pharo-project/pharo/issues/cleanup Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 25, 2019

[Pharo 7.0] Build #166: BackPort Pharo7: Moved becomeForward from Object to ProtoObject where it belongs

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

There is a new Pharo build available! The status of the build #166 was: FAILURE. The Pull Request #4084 was integrated: "BackPort Pharo7: Moved becomeForward from Object to ProtoObject where it belongs" Pull request url: https://github.com/pharo-project/pharo/pull/4084 Issue Url: https://pharo.fogbugz.com/f/cases/Pharo7.0 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 24, 2019

Why do we have 2 VTermOutputDriver?

by Cyril Ferlicot D.

Hi, In the image we currently have two VTermOutputDriver. The second one is not used but I have the impression that it was a WIP. Does someone knows what it the state of this class? Should we remove the second? Should the second be used instead of the first? -- Cyril Ferlicot https://ferlicot.fr

July 24, 2019

Re: [Pharo-dev] Menu missing translation rule

by ducasse

I totally agree. The translation should not be the responsibility of the client! Stef > On 24 Jul 2019, at 17:15, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > Hi, > > I usually get really annoyed by the "Menu missing translation" rule > because it has a huge false positive rate. > > I am the only one get many false positives? Does it make sense to keep > this rule? > > What do you think? > > If all menus should be translated, maybe it's the menu itself that > should send #translate to the argument. > > -- > Cyril Ferlicot > https://ferlicot.fr >

July 24, 2019

[Pharo 8.0] Build #561: move setModel: out of completionAround:keyStroke:

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

There is a new Pharo build available! The status of the build #561 was: FAILURE. The Pull Request #4083 was integrated: "move setModel: out of completionAround:keyStroke:" Pull request url: https://github.com/pharo-project/pharo/pull/4083 Issue Url: https://github.com/pharo-project/pharo/issues/BetterSetModel Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 24, 2019

[Pharo 8.0] Build #560: Fix typo : annoucement => announcement

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

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

July 24, 2019

[Pharo 8.0] Build #559: Add tests for LargePositiveInteger&LargeNegativeInteger from last version of Squeak

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

There is a new Pharo build available! The status of the build #559 was: SUCCESS. The Pull Request #4081 was integrated: "Add tests for LargePositiveInteger&LargeNegativeInteger from last version of Squeak" Pull request url: https://github.com/pharo-project/pharo/pull/4081 Issue Url: https://github.com/pharo-project/pharo/issues/clean Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 24, 2019

Menu missing translation rule

by Cyril Ferlicot

Hi, I usually get really annoyed by the "Menu missing translation" rule because it has a huge false positive rate. I am the only one get many false positives? Does it make sense to keep this rule? What do you think? If all menus should be translated, maybe it's the menu itself that should send #translate to the argument. -- Cyril Ferlicot https://ferlicot.fr

July 24, 2019