- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] machine learning for code completion
by ducasse Aug. 15, 2019

Aug. 15, 2019

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 > >

5 5

[Pharo 8.0] Build #633: Delete warnings of references between classes that will be remove
by ci-pharo-ci-jenkins2＠inria.fr Aug. 15, 2019

Aug. 15, 2019

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…

1 0

[Pharo 8.0] Build #632: 2540-self-theme-settings-fadedBackgroundWindows-is-overzealous-violation-of-LOD
by ci-pharo-ci-jenkins2＠inria.fr Aug. 15, 2019

Aug. 15, 2019

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…

1 0

[Pharo 8.0] Build #631: Improve-stability-of-menubar
by ci-pharo-ci-jenkins2＠inria.fr Aug. 15, 2019

Aug. 15, 2019

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…

1 0

machine learning for code completion
by Myroslava Romaniuk Aug. 14, 2019

Aug. 14, 2019

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

1 0

[Pharo 7.0] Build #168: BackPort Pharo7: Moved becomeForward from Object to ProtoObject where it belongs
by ci-pharo-ci-jenkins2＠inria.fr Aug. 13, 2019

Aug. 13, 2019

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…

1 0

[Pharo 7.0] Build #167: BackPort Pharo7: Moved becomeForward from Object to ProtoObject where it belongs
by ci-pharo-ci-jenkins2＠inria.fr Aug. 13, 2019

Aug. 13, 2019

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…

1 0

Re: [Pharo-dev] problem with pushing to github
by milton mamani Aug. 13, 2019

Aug. 13, 2019

+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 >

1 0

Information on Spec development
by Cyril Ferlicot Aug. 13, 2019

Aug. 13, 2019

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! -- Cyril Ferlicot https://ferlicot.fr

6 10

[Pharo 8.0] Build #630: 4302-Code-completion-fix-extended-completion-for-NECController
by ci-pharo-ci-jenkins2＠inria.fr Aug. 13, 2019

Aug. 13, 2019

There is a new Pharo build available! The status of the build #630 was: SUCCESS. The Pull Request #4303 was integrated: "4302-Code-completion-fix-extended-completion-for-NECController" Pull request url: https://github.com/pharo-project/pharo/pull/4303 Issue Url: https://github.com/pharo-project/pharo/issues/4302 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0