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

[Pharo 7.0-dev] Build #289: 20676 Categorize uncategorized methods in classes starting with K
by ci-pharo-ci-jenkins2＠inria.fr Nov. 13, 2017

Nov. 13, 2017

There is a new Pharo build available! The status of the build #289 was: SUCCESS. The Pull Request #470 was integrated: "20676 Categorize uncategorized methods in classes starting with K" Pull request url: https://github.com/pharo-project/pharo/pull/470 Issue Url: https://pharo.fogbugz.com/f/cases/20676 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #288: 20674 Categorize uncategorized methods in classes starting with J
by ci-pharo-ci-jenkins2＠inria.fr Nov. 13, 2017

Nov. 13, 2017

There is a new Pharo build available! The status of the build #288 was: SUCCESS. The Pull Request #468 was integrated: "20674 Categorize uncategorized methods in classes starting with J" Pull request url: https://github.com/pharo-project/pharo/pull/468 Issue Url: https://pharo.fogbugz.com/f/cases/20674 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #287: 20677-Improve-system-dependencies-tests
by ci-pharo-ci-jenkins2＠inria.fr Nov. 13, 2017

Nov. 13, 2017

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

1 0

Iceberg pull request tool is broken
by Stephane Ducasse Nov. 13, 2017

Nov. 13, 2017

https://github.com/pharo-vcs/iceberg/issues/515

1 0

Esteban's ChangeLog week of 6 November 2017
by estebanlm＠gmail.com Nov. 13, 2017

Nov. 13, 2017

Hello! This is my weekly ChangeLog, from 6 November 2017 to 12 November 2017. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=6/11/2017&to=12/11/2017 ChangeLog ========= 5 November 2017: ---------------- * I spent the full week working on the conversion to tonel, which is not working. So I can say "mission accomplished" ;) Please notice that for properly use Pharo7.0a with tonel you should: * update/sync your clone and fork * download a new Pharo7.0a image Next week I'm on holidays and on Smalltalks conf so you will not hear much, but right after I will work on simplify the contribution process (make it more coherent at least) and improvements to speed up Iceberg a bit more. cheers! Esteban

1 0

feenk log
by Tudor Girba Nov. 12, 2017

Nov. 12, 2017

Hi, Over the past couple of weeks Alex worked on stabilizing a first beta01 version for Pharo 6.1: https://twitter.com/feenkcom/status/929031849879461889 This is available as a beta01 tag in the pharo61 branch here: https://github.com/pharo-graphics/Bloc/tree/beta01 The main readme was updated with instructions and links: https://github.com/pharo-graphics/Bloc An overview of the improvements: - improved animations support that also works for scaling https://twitter.com/feenkcom/status/927617393194610693 - improved debugging support for transformations https://twitter.com/feenkcom/status/926040946130612224 - support for programatic testing of bloc mouse events: https://twitter.com/feenkcom/status/925672206763511808 - updated MemoryGame tutorial: http://files.pharo.org/books-pdfs/booklet-Bloc/2017-11-09-memorygame.pdf https://github.com/pharo-graphics/Tutorials - extended examples that offer a 52% coverage - new Bloc world menu for easily accessing Bloc examples and reseting the Universe Cheers, The feenk team -- www.tudorgirba.com www.feenk.com "The coherence of a trip is given by the clearness of the goal."

8 14

Moving back and forth from 64 to 32 bit images - possible?
by Todd Blanchard Nov. 12, 2017

Nov. 12, 2017

What is the story on moving back and forth on 32 and 64 bit images? I'd like to develop apps for my Raspberry Pi on my Mac - both will use native libraries but the Mac is full of 64 bit system libraries and the Pi is full of 32 bit libraries and I don't want to have to run around building 32 bit copies of the libraries I already have on my Mac. Is this possible to achieve?

1 0

Tonel and class definition changes
by Denis Kudriashov Nov. 12, 2017

Nov. 12, 2017

Hi. I extracted my question from previous thread about encoding issue in Tonel. 2017-11-10 18:08 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > On 10 Nov 2017, at 13:05, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > 2017-11-10 16:30 GMT+01:00 Martin McClure <martin(a)hand2mouse.com>: >>> >>> Tonel is intended to be, I believe: >>> * For Smalltalk primarily (although there are other languages) >>> * Be for any Smalltalk dialect (although the first implementation is for >>> Pharo, it is being ported to GemStone, and we intend to port it to VW and >>> VA) >>> >> >> Interesting how it will be handled when Pharo will use slots abstraction >> exclusively. And more simple, when there will be only package and tags >> instead of class categories. >> > > To be more clear. Imaging that instead of #instanceVariables field Pharo > will use #slots. And instead of #category it will be #package and #tags > > > what does it has to do with this thread? > My question was related to the sentence that Tonel is intended to be for any Smalltalk dialect. If Pharo will use #slots, #package and #tags names in class definition format it will be not compatible to other smalltalks. > handling that is trivial: once we actually have slots (bah, we have them, > but once we *use* them) and once we move to package+tags, we just adapt the > descriptions. Thatâs the advantage of using STON to keep them. > And what will happen then? We will again regenerate all sources/history? When we will switch to new names every class will be modified in following commit.

3 4

Is fileout on the change sorter working in Pharo 70?
by Stephane Ducasse Nov. 12, 2017

Nov. 12, 2017

Hi I'm trying to rescue some of my work (that I cannot save in MC nor in Iceberg because the system does not see it - super funny). I can browse the change using the changesorter when I do fileout the system tells me that the file it saved but I cannot find it on my disc. Apparently none of the fileout is working in the changesorter. :( Stef

7 15

Convention for "reset" methods
by Cyril Ferlicot Nov. 12, 2017

Nov. 12, 2017

Hi, Torsten is doing a really cool job by cleaning the protocols of Pharo. Smalltalk has a lot of conventions and if we want the users to apply them we need to have a clean Pharo. On that subject I was wonderingâ¦ Do we have a real convention for "reset" methods? With this script: ((RPackageOrganizer default packages flatCollect: #methods) select: [ :each | each selector = #reset ]) collect: #protocol as: Bag We can see that there is different way to do. 25 in accessing 11 in initialization 10 in positioning 10 in instance creation And some others less popular choices. So my question is, should we have a conventional protocol for reset methods? For now, most of them are in "accessing", but it cause a violation of the RBUnaryAccessingMethodWithoutReturnRule. Personally I think that "initialization" protocol make the more sens. If the community agree on it we could - Recategorize - Make sure the automatic categorizer follow the convention - Add a rule/test to check that Waiting for your thoughts :) -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

3 2