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

[Pharo 8.0] Build #627: 4194-Missing-refactoring-Abstract-instance-variable

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

There is a new Pharo build available! The status of the build #627 was: SUCCESS. The Pull Request #4199 was integrated: "4194-Missing-refactoring-Abstract-instance-variable" Pull request url: https://github.com/pharo-project/pharo/pull/4199 Issue Url: https://github.com/pharo-project/pharo/issues/4194 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 13, 2019

Re: [Pharo-dev] Information on Spec development

by Cyril Ferlicot

On Thu, Jun 20, 2019 at 5:29 PM Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > Hello everyone! > > This is an important update about the development of Spec. > > As you might have heard, we are working on Spec to release a new > version in Pharo 8. One goal is to unify all Pharo interfaces behind > one GUI framework and a second goal is to allow multiple back-ends > (Morphic but also GTK, Bloc, ...). To reach those goals we have been > updating the current version of Spec. We see now, however, that > updating Spec directly creates troubles with migration. For example, > we currently have a lot of deprecation warnings in Iceberg, because we > can't update it without breaking Pharo 7 compatibility. > > After some discussions between the engineers working on Spec, here is > our plan to improve the situation: We will copy all classes of Spec > and rename them with the "Sp" prefix. (We will also ensure that every > class of Spec started with the same prefix for consistency). For > extensions methods, we will rename them to have a version different > from Spec 1 (The spec from Pharo 7). Once done we will integrate this > new version in Pharo 8. From there we will wait some weeks to let > users who started to use the updated Spec change their projects to use > this new Spec2. Finally, we will revert all changes that happened on > Spec 1 and deprecate the packages. We hope this will make things > easier for everyone. > > Have a nice day! Hi, The revert of changes of Spec 1 is now done in Pharo 8. Spec 1 is now in the same state than in Pharo 7 and Spec2 can live next to it. All classes of Spec2 start with the Sp or TSp prefix. Have a nice day. > > -- > Cyril Ferlicot > https://ferlicot.fr -- Cyril Ferlicot https://ferlicot.fr

Aug. 13, 2019

[Pharo 8.0] Build #626: 4298-Calypso-does-not-show-empty-protocols

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

There is a new Pharo build available! The status of the build #626 was: SUCCESS. The Pull Request #4299 was integrated: "4298-Calypso-does-not-show-empty-protocols" Pull request url: https://github.com/pharo-project/pharo/pull/4299 Issue Url: https://github.com/pharo-project/pharo/issues/4298 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 13, 2019

[Pharo 8.0] Build #625: Update-manually-resolved-dependencies

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

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

Aug. 13, 2019

Re: [Pharo-dev] Impossible to create new protocol?

by Cyril Ferlicot

On Tue, Aug 13, 2019 at 9:18 AM ducasse <stepharo(a)netcourrier.com> wrote: > > Tx pavel. > I ask cyril to fix it :) > https://github.com/pharo-project/pharo/pull/4299 > > -- Cyril Ferlicot https://ferlicot.fr

Aug. 13, 2019

[Pharo 8.0] Build #624: Update order of method list (RBPushDownPreview and RBPushUpPreview )

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

There is a new Pharo build available! The status of the build #624 was: FAILURE. The Pull Request #4296 was integrated: "Update order of method list (RBPushDownPreview and RBPushUpPreview )" Pull request url: https://github.com/pharo-project/pharo/pull/4296 Issue Url: https://github.com/pharo-project/pharo/issues/ChangeToAlphabeticalOrder Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 13, 2019

Re: [Pharo-dev] Impossible to create new protocol?

by ducasse

Tx pavel. I ask cyril to fix it :) > On 13 Aug 2019, at 09:09, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > yes, the tagsForAllMethods method now hides protocols without methods: > allProtocols select: [ :each | each methods anySatisfy: ... > > Ãºt 13. 8. 2019 v 9:05 odesÃlatel Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>> napsal: > introduced in build.613. This is probably the source of this issue: https://github.com/pharo-project/pharo/commit/a0706a080383be50fde8aa90d1709… <https://github.com/pharo-project/pharo/commit/a0706a080383be50fde8aa90d1709…> > Ãºt 13. 8. 2019 v 8:53 odesÃlatel Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>> napsal: > on three days old image (build.610) it worked > > Ãºt 13. 8. 2019 v 8:50 odesÃlatel Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>> napsal: > I'm confirming this issue > > po 12. 8. 2019 v 21:55 odesÃlatel ducasse <stepharo(a)netcourrier.com <mailto:stepharo@netcourrier.com>> napsal: > Hi > > In latest pharo version (we broke a bit iceberg and it will be fixed) I cannot add a new protocol. > Nothing happen once I type a new name. > > Is it something that only happen to me? > > S > > >

Aug. 13, 2019

Re: [Pharo-dev] Impossible to create new protocol?

by Pavel Krivanek

yes, the tagsForAllMethods method now hides protocols without methods: allProtocols select: [ :each | each methods anySatisfy: ... Ãºt 13. 8. 2019 v 9:05 odesÃlatel Pavel Krivanek <pavel.krivanek(a)gmail.com> napsal: > introduced in build.613. This is probably the source of this issue: > https://github.com/pharo-project/pharo/commit/a0706a080383be50fde8aa90d1709… > > Ãºt 13. 8. 2019 v 8:53 odesÃlatel Pavel Krivanek <pavel.krivanek(a)gmail.com> > napsal: > >> on three days old image (build.610) it worked >> >> Ãºt 13. 8. 2019 v 8:50 odesÃlatel Pavel Krivanek <pavel.krivanek(a)gmail.com> >> napsal: >> >>> I'm confirming this issue >>> >>> po 12. 8. 2019 v 21:55 odesÃlatel ducasse <stepharo(a)netcourrier.com> >>> napsal: >>> >>>> Hi >>>> >>>> In latest pharo version (we broke a bit iceberg and it will be fixed) I >>>> cannot add a new protocol. >>>> Nothing happen once I type a new name. >>>> >>>> Is it something that only happen to me? >>>> >>>> S >>>> >>>> >>>> >>>>

Aug. 13, 2019

[Pharo 8.0] Build #623: Do-not-flush-all-caches-when-a-class-is-removed

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

There is a new Pharo build available! The status of the build #623 was: FAILURE. The Pull Request #4205 was integrated: "Do-not-flush-all-caches-when-a-class-is-removed" Pull request url: https://github.com/pharo-project/pharo/pull/4205 Issue Url: https://github.com/pharo-project/pharo/issues/Do Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 13, 2019

Re: [Pharo-dev] Impossible to create new protocol?

by Pavel Krivanek

introduced in build.613. This is probably the source of this issue: https://github.com/pharo-project/pharo/commit/a0706a080383be50fde8aa90d1709… Ãºt 13. 8. 2019 v 8:53 odesÃlatel Pavel Krivanek <pavel.krivanek(a)gmail.com> napsal: > on three days old image (build.610) it worked > > Ãºt 13. 8. 2019 v 8:50 odesÃlatel Pavel Krivanek <pavel.krivanek(a)gmail.com> > napsal: > >> I'm confirming this issue >> >> po 12. 8. 2019 v 21:55 odesÃlatel ducasse <stepharo(a)netcourrier.com> >> napsal: >> >>> Hi >>> >>> In latest pharo version (we broke a bit iceberg and it will be fixed) I >>> cannot add a new protocol. >>> Nothing happen once I type a new name. >>> >>> Is it something that only happen to me? >>> >>> S >>> >>> >>> >>>

Aug. 13, 2019