December 2017 - Pharo-dev - lists.pharo.org

Epicea feedback - save points

by Ben Coman

When I'm in need Epicea, the common scenario is that I've working in the same session of an Image most of the day, or even days, and I've done something stupid to lock up the UI, and its only been an hour since my last save point (force of habit). When I review Epicea, "Filter > Show latest changes" its still ahrd to determine which changes I'm missing. What I've just realised is I miss the visibility of the Save Point in the old changes system. I'd find it really useful for the save points to be show in the changes list, and also a filter I'd find really useful is "Shows latest changes since last save". cheers -ben

Dec. 13, 2017

Re: [Pharo-dev] spurious characters in class comments

by Norbert Hartl

IMHO this would be the case if the sourde code is written in utf-8 but read in latin1. Norbert > Am 12.12.2017 um 23:41 schrieb Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: > > Take a look at Dictionary.class.st for example > > https://github.com/pharo-project/pharo/blob/bc8b9658958f4464189cf3e7fffd8c9… > > on line 10: > > IÃÆÃÆÃâÃâÃÆÃâÃâÃ am use when we need a collection of objects which I can access with a key. For example if you associate some words with a definition, the word will be the key and the definition will be the value. Both of them can be any kind of objects. > > At each commit, the number of odd characters increases...

Dec. 13, 2017

odd behaviour dragging method between protocols

by Ben Coman

I could just be having a brain freeze, but just sharing in case anyone else is similarly going mad... a few times recently in Nautilus I've dragged a method from the fourth pane and dropped it on a protocol in the third pane and the method disappeared from the system. Luckily its easily recovered from Tools > Code Changes, where it shows as deleted. But its weird that a delete could be triggered from the action I (thought I) performed. I've yet to detect a pattern. Unfortunately its kind of blink-and-you-miss-it. Its not until a second later when selecting the target protocol that the behaviour becomes apparent. This is in 60527-64, Unix built on Jul 20 2017 20:40:36 Compiler: 4.6.3 cheers -ben

Dec. 13, 2017

spurious characters in class comments

by Nicolas Cellier

Take a look at Dictionary.class.st for example https://github.com/pharo-project/pharo/blob/bc8b9658958f4464189cf3e7fffd8c9… on line 10: IÃÆÃÆÃâÃâÃÆÃâÃâÃ am use when we need a collection of objects which I can access with a key. For example if you associate some words with a definition, the word will be the key and the definition will be the value. Both of them can be any kind of objects. At each commit, the number of odd characters increases...

Dec. 12, 2017

[Pharo 7.0-dev] Build #378: 20866-revert-retryTimes-parameter-on-CI

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

There is a new Pharo build available! The status of the build #378 was: SUCCESS. The Pull Request #600 was integrated: "20866-revert-retryTimes-parameter-on-CI" Pull request url: https://github.com/pharo-project/pharo/pull/600 Issue Url: https://pharo.fogbugz.com/f/cases/20866 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 12, 2017

Re: [Pharo-dev] better name for #aggregateRuns:

by Todd Blanchard

I'm kind of trying to figure out when I'd want that operation. groupsWithSeparatorsWhereSeparatatorsMatch: feels like it says what it does > On Dec 12, 2017, at 10:19 AM, Ben Coman <btc(a)openinworld.com> wrote: > > > > On 12 December 2017 at 20:03, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com <mailto:nicolas.cellier.aka.nice@gmail.com>> wrote: > > > 2017-12-12 13:01 GMT+01:00 Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no <mailto:henrik.s.johansen@veloxit.no>>: > Ben Coman wrote > > > > But after pondering a while for a better name, I wonder what is wrong with > > the existing? > > Googling "define aggregate" provides... > > aggregate (noun) = a whole formed by combining several separate > > elements. > > aggregate (verb) = form or group into a class or cluster. > > > > The separate elements are runs defined by the block. > > The existing name seems quite precise to me. > > > > cheers -ben > > When I read aggregateRuns:, I think the opposite; something combining > different runs into a single entity, not something that splits a single > collection into constituent runs... > > okay. I can understand that perspective. > > > Something like (split/collect)runsAccordingTo: sounds more descriptive to my > ears, at least. > > Cheers, > Henry > > > > I like groupBy: but in Squeak groupBy: produces a dictionary with unique keys ignoring the multiple sequences... > split already carries the meaning of preserving the sequences, but we have to tell to split at a change of value.... > Run is also quite explicit... > > groupByRuns: / splitRuns: > > +1 > groupByRuns: is good. > > cheers -ben

Dec. 12, 2017

Re: [Pharo-dev] Does pharo build not retry anymore?

by Pavel Krivanek

The variable value was reverted to the original value. Thanks. -- Pavel 2017-12-12 20:13 GMT+01:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: > Yes, with Marcus we decreased the retryTimes variable two weeks ago to 1 > because in that time the validations were in really bad shape and literally > every validation failed on some random issue and the retries caused > enormous build times. It was producing more troubles than profit. It > probably can be reverted now because the main problem of the validation > instability was suppressed. I will prepare a PR. > > -- Pavel > > 2017-12-12 18:52 GMT+01:00 Guillermo Polito <guillermopolito(a)gmail.com>: > >> I see that we are retrying tests only once, which is causing most (if not >> all) pull requests to fail sporadically... >> >> Maybe it got lost because of a mistake? >> >> Also, I'd like that changes in the build process are discussed in the >> mailing list from time to time... I've put a lot of effort into making it >> work and if we have regressions I'd like to understand them... >> >> Guille >> >> -- >> >> >> >> 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 <+33%206%2052%2070%2066%2013> >> > >

Dec. 12, 2017

Re: [Pharo-dev] I love the launcher!!!!

by Alexandre Bergel

Your email made me try Pharo Launcher. I love it too! It replaces all my scripts to download the VM and the last images. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Nov 23, 2017, at 5:51 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Hi > > I love the PharoLauncher. > It helps me to manage my parallel development and projects. > > We should put a link on the Pharo web site because > > http://files.pharo.org/platform/launcher/ > > is arcane. > > Stef >

Dec. 12, 2017

Re: [Pharo-dev] Does pharo build not retry anymore?

by Pavel Krivanek

Yes, with Marcus we decreased the retryTimes variable two weeks ago to 1 because in that time the validations were in really bad shape and literally every validation failed on some random issue and the retries caused enormous build times. It was producing more troubles than profit. It probably can be reverted now because the main problem of the validation instability was suppressed. I will prepare a PR. -- Pavel 2017-12-12 18:52 GMT+01:00 Guillermo Polito <guillermopolito(a)gmail.com>: > I see that we are retrying tests only once, which is causing most (if not > all) pull requests to fail sporadically... > > Maybe it got lost because of a mistake? > > Also, I'd like that changes in the build process are discussed in the > mailing list from time to time... I've put a lot of effort into making it > work and if we have regressions I'd like to understand them... > > Guille > > -- > > > > 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 <+33%206%2052%2070%2066%2013> >

Dec. 12, 2017

Re: [Pharo-dev] better name for #aggregateRuns:

by Ben Coman

On 12 December 2017 at 20:03, Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com> wrote: > > > 2017-12-12 13:01 GMT+01:00 Henrik Sperre Johansen < > henrik.s.johansen(a)veloxit.no>: > >> Ben Coman wrote >> > >> > But after pondering a while for a better name, I wonder what is wrong >> with >> > the existing? >> > Googling "define aggregate" provides... >> > aggregate (noun) = a whole formed by combining several separate >> > elements. >> > aggregate (verb) = form or group into a class or cluster. >> > >> > The separate elements are runs defined by the block. >> > The existing name seems quite precise to me. >> > >> > cheers -ben >> >> When I read aggregateRuns:, I think the opposite; something combining >> different runs into a single entity, not something that splits a single >> collection into constituent runs... >> > okay. I can understand that perspective. > >> Something like (split/collect)runsAccordingTo: sounds more descriptive >> to my >> ears, at least. >> >> Cheers, >> Henry >> >> >> > I like groupBy: but in Squeak groupBy: produces a dictionary with unique > keys ignoring the multiple sequences... > split already carries the meaning of preserving the sequences, but we have > to tell to split at a change of value.... > Run is also quite explicit... > > groupByRuns: / splitRuns: > +1 groupByRuns: is good. cheers -ben

Dec. 12, 2017