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

[Pharo 8.0] Build #471: 3871-The-method-ClassDescriptioninstanceVariables-called-from-T2TraitWithSlotstestRedefiningSuperclass-has-been-deprecated-Please-use-instVarNames-or-slotNames-instead

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

There is a new Pharo build available! The status of the build #471 was: FAILURE. The Pull Request #3872 was integrated: "3871-The-method-ClassDescriptioninstanceVariables-called-from-T2TraitWithSlotstestRedefiningSuperclass-has-been-deprecated-Please-use-instVarNames-or-slotNames-instead" Pull request url: https://github.com/pharo-project/pharo/pull/3872 Issue Url: https://github.com/pharo-project/pharo/issues/3871 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 11, 2019

Re: [Pharo-dev] Changes proposal on Pre debugger

by Cyril Ferlicot

On Thu, Jul 11, 2019 at 7:17 AM Ben Coman <btc(a)openinworld.com> wrote: > > > I'm not sure how I feel. I usually click in the Pre-Debugger stack > rather than click the <Debug> button. > When doing TDD I'll often know that the method I want to open is four > down in the stack rather than where the library method bombed out. > But really at worst its one additional click and probably easy enough > to adapt so I'm willing to give it a go. > Hi Ben, In your case there will be no change. You will still click one time four down in the stack. Or did I miss something? > cheers -ben > -- Cyril Ferlicot https://ferlicot.fr

July 11, 2019

[Pharo 8.0] Build #470: Minimal Cleanups BalloonEngineConstants

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

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

July 11, 2019

[Pharo 8.0] Build #469: Remove unnecessary comment in BalloonEngine>>initialize

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

There is a new Pharo build available! The status of the build #469 was: FAILURE. The Pull Request #3866 was integrated: "Remove unnecessary comment in BalloonEngine>>initialize" Pull request url: https://github.com/pharo-project/pharo/pull/3866 Issue Url: https://github.com/pharo-project/pharo/issues/3865 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 11, 2019

[Pharo 8.0] Build #468: Cleanups GradienFillStyle

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

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

July 11, 2019

Re: [Pharo-dev] Changes proposal on Pre debugger

by Ben Coman

On Thu, 11 Jul 2019 at 02:22, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > > Hi, > > After talking with Steven (in copy) we agreed on possible improvements > around the pre debugger. I would like to share our vision and check if > the community agrees. > > Context: > > The pre debugger is the window opening when an exception is signalled > and not catched. This window currently has two views: > - On warnings it display a text explaining the encountered problem. You > can the proceed, abandon or debug. For example, this happens on > Deprecations. > - On other exceptions it display a short stack of the context in which > the error was raised. You can abandon, open a full debugger, ... > > Before, both views were managed via the same UI class. Yesterday I > slitted this class. > > Proposed change: > > In our opinion, the pre debugger displaying a stack is useless. All the > options it proposes are in the full debugger within one click reach. The > only value we see for the pre debugger is about warnings. > > Thus, we propose to remove the stack pre debugger and display directly > the full debugger for anything else than a warning. This will save > everyone one click each time we want to debug something. We would keep > the textual view for warnings. > > In case we do this, I wonder if we should keep the setting "Open full > debugger". I think most users of this option are using it in order to > not see the stack pre debugger and not to skip warnings. So, do someone > have an opinion about keeping or removing this setting in case we remove > the stack pre debugger? I'm not sure how I feel. I usually click in the Pre-Debugger stack rather than click the <Debug> button. When doing TDD I'll often know that the method I want to open is four down in the stack rather than where the library method bombed out. But really at worst its one additional click and probably easy enough to adapt so I'm willing to give it a go. cheers -ben

July 11, 2019

[Pharo 8.0] Build #467: 3484-Migrate-some-refactoring-UI-to-Spec-2-

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

There is a new Pharo build available! The status of the build #467 was: SUCCESS. The Pull Request #3728 was integrated: "3484-Migrate-some-refactoring-UI-to-Spec-2-" Pull request url: https://github.com/pharo-project/pharo/pull/3728 Issue Url: https://github.com/pharo-project/pharo/issues/3484 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 10, 2019

Re: [Pharo-dev] Read-only image mode

by ducasse

tx I will check. Stef > On 9 Jul 2019, at 23:15, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > Hi Stef, > > you may download the built image from CI to see the code in the live image > https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> > > -- Pavel

July 10, 2019

[Pharo 8.0] Build #466: 3863-Migrate-Reflectivity-example-to-Spec-2

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

There is a new Pharo build available! The status of the build #466 was: FAILURE. The Pull Request #3864 was integrated: "3863-Migrate-Reflectivity-example-to-Spec-2" Pull request url: https://github.com/pharo-project/pharo/pull/3864 Issue Url: https://github.com/pharo-project/pharo/issues/3863 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 10, 2019

[Pharo 8.0] Build #465: 3850-Migrate-Hiedra-to-Spec2

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

There is a new Pharo build available! The status of the build #465 was: FAILURE. The Pull Request #3851 was integrated: "3850-Migrate-Hiedra-to-Spec2" Pull request url: https://github.com/pharo-project/pharo/pull/3851 Issue Url: https://github.com/pharo-project/pharo/issues/3850 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 10, 2019