April 2018 - Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #817: 21774 Cleanup MethodClassifierTest

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

There is a new Pharo build available! The status of the build #817 was: SUCCESS. The Pull Request #1248 was integrated: "21774 Cleanup MethodClassifierTest" Pull request url: https://github.com/pharo-project/pharo/pull/1248 Issue Url: https://pharo.fogbugz.com/f/cases/21774 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 30, 2018

Re: [Pharo-dev] self-backporting from P7 to P6.1

by Guillermo Polito

On Mon, Apr 30, 2018 at 12:19 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > The idea is that people should do the opposite: code for Pharo7, while >> being in Pharo 6. >> > > Exactly. Several times I was put off contributing to P7, because I needed > a solution now, and not in year when P7 comes out... so I hacked a > workaround instead of a proper fix... which is not good. > > > Peter, I want your file dialog into pharo! > > >> Me too !! >> > > Me too. :-D > > But I'm finishing my degree in ~45 days so it won't be before that... > Finish your degree, that's important too :) > > Peter > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

April 30, 2018

Re: [Pharo-dev] self-backporting from P7 to P6.1

by Peter UhnÃ¡k

> > > The idea is that people should do the opposite: code for Pharo7, while > being in Pharo 6. > Exactly. Several times I was put off contributing to P7, because I needed a solution now, and not in year when P7 comes out... so I hacked a workaround instead of a proper fix... which is not good. > Peter, I want your file dialog into pharo! > Me too !! > Me too. :-D But I'm finishing my degree in ~45 days so it won't be before that... Peter

April 30, 2018

Re: [Pharo-dev] self-backporting from P7 to P6.1

by Sven Van Caekenberghe

> On 30 Apr 2018, at 11:41, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Esteban did some work on making a forward compatibility package for spec. > > github://pharo-contributions/Spec70Compatibility:v1.0.0/src > > The idea is that people should do the opposite: code for Pharo7, while being in Pharo 6. > > But that covers only Spec. We have to think if there is some automatic solution for all the stream/file changes also. > > Peter, I want your file dialog into pharo! Me too !! > On Mon, Apr 30, 2018 at 11:37 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > Hi, > > are there some recommended practices / tooling for custom backporting from P7 to P6.1? > > Thanks, > Peter > > > > -- > > Guille Polito > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > CRIStAL - UMR 9189 > French National Center for Scientific Research - http://www.cnrs.fr > > Web: http://guillep.github.io > Phone: +33 06 52 70 66 13

April 30, 2018

Re: [Pharo-dev] self-backporting from P7 to P6.1

by Guillermo Polito

Esteban did some work on making a forward compatibility package for spec. github://pharo-contributions/Spec70Compatibility:v1.0.0/src The idea is that people should do the opposite: code for Pharo7, while being in Pharo 6. But that covers only Spec. We have to think if there is some automatic solution for all the stream/file changes also. Peter, I want your file dialog into pharo! On Mon, Apr 30, 2018 at 11:37 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > Hi, > > are there some recommended practices / tooling for custom backporting from > P7 to P6.1? > > Thanks, > Peter > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

April 30, 2018

self-backporting from P7 to P6.1

by Peter UhnÃ¡k

Hi, are there some recommended practices / tooling for custom backporting from P7 to P6.1? Thanks, Peter

April 30, 2018

[Pharo 7.0-dev] Build #816: 21801 Class comments on some system tests

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

There is a new Pharo build available! The status of the build #816 was: SUCCESS. The Pull Request #1271 was integrated: "21801 Class comments on some system tests" Pull request url: https://github.com/pharo-project/pharo/pull/1271 Issue Url: https://pharo.fogbugz.com/f/cases/21801 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 30, 2018

[Pharo 7.0-dev] Build #815: 21803 Cleanups in Tool-CriticBrowser

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

There is a new Pharo build available! The status of the build #815 was: FAILURE. The Pull Request #1272 was integrated: "21803 Cleanups in Tool-CriticBrowser" Pull request url: https://github.com/pharo-project/pharo/pull/1272 Issue Url: https://pharo.fogbugz.com/f/cases/21803 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 30, 2018

Esteban's ChangeLog week of 23 April 2018

by estebanlm＠gmail.com

Hello! This is my weekly ChangeLog, from 23 April 2018 to 29 April 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=23/4/2018&to=29/4/2018 ChangeLog ========= 24 April 2018: -------------- * I released [v0.7.3 of iceberg](https://github.com/pharo-vcs/iceberg/releases/tag/v0.7.3) List of changes is big, as this are the first stabilisation releases after the huge refactor we did... * I just released libgit [v1.3.1](https://github.com/pharo-vcs/libgit2-pharo-bindings/releases/tag/v1… which simplifies initialisation mechanism. 23 April 2018: -------------- * Lots of meetings, but I managed to work today in [https://github.com/pharo-vcs/iceberg/issues/667](https://github.com/pharo-v… . Guille needs to finish it but that means 0.7.3 is almost ready. cheers! Esteban

April 30, 2018

Fix for 21809

by Hilaire

Hi, More freedom in the text color for tooltips for a better visibilityÂ (see screenshot). https://pharo.fogbugz.com/f/cases/21809/Both-tooltips-text-and-background-c… Change set fix attached to the bug ticket. I don't learn yet the current procedure to integrate fixes so I let it for someone with the know how. Hilaire -- Dr. Geo http://drgeo.eu

April 29, 2018