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

[Pharo 8.0] Build #633: Delete warnings of references between classes that will be remove

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

There is a new Pharo build available! The status of the build #633 was: FAILURE. The Pull Request #4295 was integrated: " Delete warnings of references between classes that will be remove" Pull request url: https://github.com/pharo-project/pharo/pull/4295 Issue Url: https://github.com/pharo-project/pharo/issues/Removeclasses Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 15, 2019

[Pharo 8.0] Build #632: 2540-self-theme-settings-fadedBackgroundWindows-is-overzealous-violation-of-LOD

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

There is a new Pharo build available! The status of the build #632 was: FAILURE. The Pull Request #4312 was integrated: "2540-self-theme-settings-fadedBackgroundWindows-is-overzealous-violation-of-LOD" Pull request url: https://github.com/pharo-project/pharo/pull/4312 Issue Url: https://github.com/pharo-project/pharo/issues/2540 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 15, 2019

[Pharo 8.0] Build #631: Improve-stability-of-menubar

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

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

Aug. 15, 2019

Re: [Pharo-dev] machine learning for code completion

by ducasse

hello miroslava you take a NLP approach and I do not know if it will be working Now people like proksch and mezini took a statiscal approach. I would really like to see if we can apply the same technics to Pharo completion and measure the difference. It could be a really nice master (even from a data scientist point of view) > On 15 Aug 2019, at 00:01, Myroslava Romaniuk <romaniuk(a)ucu.edu.ua> wrote: > > > From: Myroslava Romaniuk <romaniuk(a)ucu.edu.ua> > Subject: machine learning for code completion > Date: 15 August 2019 at 00:01:23 CEST > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > > > for anyone interested, made a blog post about researching some of the existing approaches of combining ML to improve code completion. in pharo we want to try training the n-gram model. have a slight idea of how it might be implemented in practice but mostly still trying to figure it out, so if anyone else has some suggestions/ideas/tips that would be great > > link for the blog post : https://medium.com/@myroslavarm/machine-learning-for-code-completion-258379… <https://medium.com/@myroslavarm/machine-learning-for-code-completion-258379…> > > cheers, > myroslava > >

Aug. 15, 2019

machine learning for code completion

by Myroslava Romaniuk

for anyone interested, made a blog post about researching some of the existing approaches of combining ML to improve code completion. in pharo we want to try training the n-gram model. have a slight idea of how it might be implemented in practice but mostly still trying to figure it out, so if anyone else has some suggestions/ideas/tips that would be great link for the blog post : https://medium.com/@myroslavarm/machine-learning-for-code-completion-258379… cheers, myroslava

Aug. 14, 2019

[Pharo 7.0] Build #168: 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 #168 was: SUCCESS. 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…

Aug. 13, 2019

[Pharo 7.0] Build #167: 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 #167 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…

Aug. 13, 2019

Re: [Pharo-dev] problem with pushing to github

by milton mamani

+1 MacOS pharo8x64 El mar., 13 ago. 2019 a las 13:31, Myroslava Romaniuk via Pharo-dev (< pharo-dev(a)lists.pharo.org>) escribiÃ³: > Hi > > saw there's a lot going on with iceberg and spec today so likely this is > related. Just created (20 mins ago) a new image to push a PR to pharo, and > usually in a new image you have to fill in your credentials and you had > 'accept' and 'ok' buttons (ok - to accept credentials, accept - to push). > Now there's no 'accept' button and it doesn't push my changes anymore. Am i > doing something wrong or is this a bug? > > P.S. i'm on windows, latest pharo 8. > > Best regards, > Myroslava >

Aug. 13, 2019

Re: [Pharo-dev] [Pharo-users] Information on Spec development

by Cyril Ferlicot

On Tue, Aug 13, 2019 at 3:25 PM Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > No, you are not :) > #asSpAdapter will be removed. > > You are looking for SpMorphPresenter (and/or the method SpPresenter>>newMorph) > In the Spec repository I deprecated #asSpAdapter with a mesage explaining SpMorphPresenter should be used. It will be integrated in next Spec integration. > Esteban > > -- Cyril Ferlicot https://ferlicot.fr

Aug. 13, 2019

Re: [Pharo-dev] [Pharo-users] Information on Spec development

by Esteban Lorenzano

> On 13 Aug 2019, at 15:19, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > On Tue, Aug 13, 2019 at 2:59 PM Norbert Hartl <norbert(a)hartl.name> wrote: >> >> >> Ah yes, I just wrote on discord. I did a tool in spec2 which I cannot use in the newest pharo. The #asSpecAdapter uses still MorphicGenericAdapter instead of SpMorphicGenericAdapter. Iceberg needs the former, my tool the latter. What is the strategy for that. For now I did a #asSpec2Adapter in my image that return the SpMorphic.. class. >> > Hi, > > The extensions in Spec2 are renamed to not conflict with Spec 1. You > are looking for #asSpAdapter ;) No, you are not :) #asSpAdapter will be removed. You are looking for SpMorphPresenter (and/or the method SpPresenter>>newMorph) Esteban > >> Norbert >> >> > > > -- > Cyril Ferlicot > https://ferlicot.fr >

Aug. 13, 2019