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

Re: [Pharo-dev] [Website] Updated Linux download instructions

by Marcus Denker

> On 13 Dec 2017, at 16:43, stephan <stephan(a)stack.nl> wrote: > > On 13-12-17 16:32, Sean P. DeNigris wrote: >> Marcus Denker-4 wrote >>> I have updated the download instructionâ¦ >> Thanks!! This seems to have been a common pain point, for new users >> especially. > > And then a newer 32 bit Linux VM needs to be build and promoted to stable as next point? > Are any of these packages automatically build after we e.g. release a new Pharo6.1 image? Marcus

Dec. 14, 2017

Re: [Pharo-dev] [Website] Updated Linux download instructions

by Marcus Denker

> On 13 Dec 2017, at 16:32, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Marcus Denker-4 wrote >> I have updated the download instructionâ¦ > > Thanks!! This seems to have been a common pain point, for new users > especially. > > Yes. What is missing is an action item for what to do to start Pharo after installing it. It does not get clear in the description where it is installed with the package manager. Marcus

Dec. 14, 2017

Re: [Pharo-dev] Moving from mc to tonel?

by Nicolas Cellier

2017-12-13 11:09 GMT+01:00 stephan <stephan(a)stack.nl>: > On 05-12-17 08:59, Peter UhnÃ¡k wrote: > >> > In my case, it turned out to be a non-UTF8 encoded character in one of >> the commit messages. >> >> I've ran into this problem in a sister project (tonel-migration), and do >> not have a proper resolution yet. I was forcing everything to be unicode, >> so I need a better way to read and write encoded strings. :< >> > > To be exact, exactly none of the older commits will be UTF8 encoded. For > most it doesn't matter as they are ASCII, but if we want to have a change > of converting older french or german code (or japanese), we need support > for what was done with WideString. That probably needs a look in the squeak > mailing list archives. > > Stephan > > > The thread would be"MC should really write snaphsot/source.st in UTF8" end of may 2013. I've made the switch in Squeak short after (june 2013). I've propsed a fix for Pharo (issues 10801 and 10811) that has been integrated in 3.0 end of june 2013. So the .mcz created before this might be problematic... As I've just reported here, I think there are problems in tonel (like if it was reading and writing with different encoding...)

Dec. 13, 2017

[Pharo 7.0-dev] Build #379: 20865-update-iceberg-to-065

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

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

Dec. 13, 2017

Re: [Pharo-dev] [Website] Updated Linux download instructions

by stephan

On 13-12-17 16:32, Sean P. DeNigris wrote: > Marcus Denker-4 wrote >> I have updated the download instructionâ¦ > > Thanks!! This seems to have been a common pain point, for new users > especially. And then a newer 32 bit Linux VM needs to be build and promoted to stable as next point? Stephan

Dec. 13, 2017

Re: [Pharo-dev] [Website] Updated Linux download instructions

by Sean P. DeNigris

Marcus Denker-4 wrote > I have updated the download instructionâ¦ Thanks!! This seems to have been a common pain point, for new users especially. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 13, 2017

Re: [Pharo-dev] Epicea feedback - save points

by Martin Dias

Hi When you "save and close" or "save as..." then next changes will go to a new log file. Then, they will have a new item of the left of the browser (as Stef said). When you just "save", I agree I'd like that. It was there originally but I disabled it because of a bug related with the announcement. Apparently now it can be re-enabled: https://pharo.fogbugz.com/f/cases/18754/Epicea-should-log-image-saving MartÃn On Wed, Dec 13, 2017 at 8:52 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Ok so we should check because it should not be complex to add that. > The model is quite nice. > > On Wed, Dec 13, 2017 at 11:47 AM, Ben Coman <btc(a)openinworld.com> wrote: > > Hi Stef, > > > > I think that is incorrect. Its easy to be certain... > > 1. Open Epicea > > 2. Save and continue > > 3. Open Epicea and observe there is no difference > > > > cheers -ben > > > > > > On 13 December 2017 at 17:59, Stephane Ducasse <stepharo.self(a)gmail.com> > > wrote: > >> > >> I think that epicea save point are the list elements on the left. > >> > >> > >> On Wed, Dec 13, 2017 at 9:05 AM, Norbert Hartl <norbert(a)hartl.name> > wrote: > >> > Same for me. I thought the last save point would be the last session > in > >> > the list but I donât think that is really true. So Iâm confused by > Epicea, > >> > too. > >> > > >> > Norbert > >> > > >> >> Am 13.12.2017 um 08:27 schrieb Ben Coman <btc(a)openinworld.com>: > >> >> > >> >> 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] I love the launcher!!!!

by Stephane Ducasse

:) For me it helps me controlling my mess euh natural entropy On Tue, Dec 12, 2017 at 8:13 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > 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. 13, 2017

[Pharo6][CI] test runs on submitted slices works again

by Marcus Denker

Hi, Pavel fixed the test runner (the monkey) for Pharo6. That means, back ports and fixes now can be checked as they used to: -> submit slice -> put issue on âfix review neededâ -> monkey will run all test For a while all these tests failed (due to issue 20788). We used a workaround (not run that test). Having the monkey-checker for Pharo6 again running is good as this simplifies very much backporting. Marcus

Dec. 13, 2017

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

by Stephane Ducasse

groupByRuns: looks good to me. On Tue, Dec 12, 2017 at 9:48 PM, Todd Blanchard <tblanchard(a)mac.com> wrote: > 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> 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. 13, 2017