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

[Pharo 7.0-dev] Build #233: 20597 Rename-old-Compiler-encoder-to-LegacyEncoders

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

There is a new Pharo build available! The status of the build #233 was: SUCCESS. The Pull Request #403 was integrated: "20597 Rename-old-Compiler-encoder-to-LegacyEncoders" Pull request url: https://github.com/pharo-project/pharo/pull/403 Issue Url: https://pharo.fogbugz.com/f/cases/20597 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 27, 2017

[ANN] Iceberg 0.6.2 backported to Pharo 6.1

by Esteban Lorenzano

Hi, I backported lastest Iceberg version to Pharo 6.1 to allow people to benefit for latest changes. This version has an important amount of tweak and fixes, but most important is the inclusion of tonel file format (this is default for Pharo 7.0, optional for Pharo 6.1) and introduces a file-per-class format. The advantages of this format has everything to do with the speed of access (is easier to reconstruct a package like) and the space on disk (methods are usually small but minimum space in disk is usually 4k so we waste a lot of space). Is also a better format for SSD disks. To backport Iceberg 0.6.2 I also needed to backport latest version of Metacello, so Pharo 6.1 and Pharo7+ users now also have the latest version of it available :) cheers! Esteban

Oct. 27, 2017

[Pharo 7.0-dev] Build #232: SUCCESS

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

There is a new Pharo build available! The status of the build #232 was: SUCCESS. Could not extract further issue information from commit message: OK more baselineOf Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 27, 2017

[Pharo 7.0-dev] Build #231: [Bug]: Fix Issue 16136 - DateModel: Handle nil Sanely

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

There is a new Pharo build available! The status of the build #231 was: SUCCESS. The Pull Request #394 was integrated: "[Bug]: Fix Issue 16136 - DateModel: Handle nil Sanely" Pull request url: https://github.com/pharo-project/pharo/pull/394 Issue Url: https://pharo.fogbugz.com/f/cases/16136 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 27, 2017

Re: [Pharo-dev] Github API on github

by Esteban Lorenzano

> On 27 Oct 2017, at 08:55, Norbert Hartl <norbert(a)hartl.name> wrote: > > > >> Am 26.10.2017 um 15:54 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: >> >> >> >>> On 26 Oct 2017, at 15:51, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>> Now the interesting question.... >>> >>> *drumroll* >>> >>> Will iceberg use this library??? >> >> what Guille did is an extract of Iceberg github api which at the time was a reinterpretation of Torstenâs api. >> I guess is possible, but my original intention was to keep it smallâ¦ so it depends :) >> > From time to time we should try to make our software modular. Doesnât that mean guille should provide a minimal package you can integrate in iceberg? right now it is modular and small :) to use the extracted api, it just needs to stay like that :P Esteban > > Norbert >> Esteban >> >>> >>> Norbert >>> >>>> Am 26.10.2017 um 15:06 schrieb Tudor Girba <tudor(a)tudorgirba.com>: >>>> >>>> Even more awesomeness :). Thanks for doing this! >>>> >>>> Doru >>>> >>>> >>>>> On Oct 26, 2017, at 2:02 PM, Torsten Bergmann <astares(a)gmx.de> wrote: >>>>> >>>>> I already contacted Guille in a private message on this one. >>>>> >>>>> Because now we have three (sorted in order of appearance): >>>>> >>>>> 1. https://balletie.github.io/GitHub/ (from Balletie, very complete) >>>>> 2. https://github.com/astares/GitHub-API (a wrapper I wrote to play with the API) >>>>> 3. https://github.com/guillep/github-api (Guille) >>>>> >>>>> If time permits we should consolidate this into a single one (maybe on https://github.com/pharo-vcs/github-api) >>>>> >>>>> Guille will contact Balletie as a next step. >>>>> >>>>> Thanks >>>>> T. >>>>> >>>>> >>>>>> Gesendet: Donnerstag, 26. Oktober 2017 um 13:32 Uhr >>>>>> Von: "Tudor Girba" <tudor(a)tudorgirba.com> >>>>>> An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >>>>>> Betreff: Re: [Pharo-dev] Github API on github >>>>>> >>>>>> Awesome. >>>>>> >>>>>> Doru >>>>>> >>>>>> >>>>>>> On Oct 20, 2017, at 10:07 AM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >>>>>>> >>>>>>> Hi guys, >>>>>>> >>>>>>> I extracted and extended some of the github API from iceberg, so it can be used as a standalone project. Maybe this is useful for somebody. >>>>>>> >>>>>>> https://github.com/guillep/github-api >>>>>>> >>>>>>> It should be easy to extend and add new functionalities, so don't hesitate if you need some missing request :) >>>>>>> >>>>>>> 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 >>>>>>> >>>>>>> Web: http://guillep.github.io >>>>>>> Phone: +33 06 52 70 66 13 >>>>>> >>>>>> -- >>>>>> www.tudorgirba.com >>>>>> www.feenk.com >>>>>> >>>>>> âThe smaller and more pervasive the hardware becomes, the more physical the software gets." >>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> -- >>>> www.tudorgirba.com >>>> www.feenk.com >>>> >>>> "Presenting is storytelling." >>> >

Oct. 27, 2017

Re: [Pharo-dev] Github API on github

by Esteban Lorenzano

> On 27 Oct 2017, at 04:55, Ben Coman <btc(a)openinworld.com> wrote: > > > > On Thu, Oct 26, 2017 at 9:51 PM, Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>> wrote: > Now the interesting question.... > > *drumroll* > > Will iceberg use this library??? > > Norbert > > What risk would this have to Iceberg losing is generality to other git/non-git repos? right now github api is used just for plugins (and they activate just in case of github repos) so I think that wouldnât be a problem. Esteban > > cheers -ben > > > > > Am 26.10.2017 um 15:06 schrieb Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>>: > > > > Even more awesomeness :). Thanks for doing this! > > > > Doru > > > > > >> On Oct 26, 2017, at 2:02 PM, Torsten Bergmann <astares(a)gmx.de <mailto:astares@gmx.de>> wrote: > >> > >> I already contacted Guille in a private message on this one. > >> > >> Because now we have three (sorted in order of appearance): > >> > >> 1. https://balletie.github.io/GitHub/ <https://balletie.github.io/GitHub/> (from Balletie, very complete) > >> 2. https://github.com/astares/GitHub-API <https://github.com/astares/GitHub-API> (a wrapper I wrote to play with the API) > >> 3. https://github.com/guillep/github-api <https://github.com/guillep/github-api> (Guille) > >> > >> If time permits we should consolidate this into a single one (maybe on https://github.com/pharo-vcs/github-api <https://github.com/pharo-vcs/github-api>). > >> > >> Guille will contact Balletie as a next step. > >> > >> Thanks > >> T. > >> > >> > >>> Gesendet: Donnerstag, 26. Oktober 2017 um 13:32 Uhr > >>> Von: "Tudor Girba" <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> > >>> An: "Pharo Development List" <pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org>> > >>> Betreff: Re: [Pharo-dev] Github API on github > >>> > >>> Awesome. > >>> > >>> Doru > >>> > >>> > >>>> On Oct 20, 2017, at 10:07 AM, Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>> wrote: > >>>> > >>>> Hi guys, > >>>> > >>>> I extracted and extended some of the github API from iceberg, so it can be used as a standalone project. Maybe this is useful for somebody. > >>>> > >>>> https://github.com/guillep/github-api <https://github.com/guillep/github-api> > >>>> > >>>> It should be easy to extend and add new functionalities, so don't hesitate if you need some missing request :) > >>>> > >>>> 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 <tel:%2B33%2006%2052%2070%2066%2013> > >>> > >>> -- > >>> www.tudorgirba.com <http://www.tudorgirba.com/> > >>> www.feenk.com <http://www.feenk.com/> > >>> > >>> âThe smaller and more pervasive the hardware becomes, the more physical the software gets." > >>> > >>> > >>> > >> > > > > -- > > www.tudorgirba.com <http://www.tudorgirba.com/> > > www.feenk.com <http://www.feenk.com/> > > > > "Presenting is storytelling." > >

Oct. 27, 2017

Re: [Pharo-dev] Github API on github

by Norbert Hartl

> Am 26.10.2017 um 15:54 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > > >> On 26 Oct 2017, at 15:51, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> Now the interesting question.... >> >> *drumroll* >> >> Will iceberg use this library??? > > what Guille did is an extract of Iceberg github api which at the time was a reinterpretation of Torstenâs api. > I guess is possible, but my original intention was to keep it smallâ¦ so it depends :) > >From time to time we should try to make our software modular. Doesnât that mean guille should provide a minimal package you can integrate in iceberg? Norbert > Esteban > >> >> Norbert >> >>> Am 26.10.2017 um 15:06 schrieb Tudor Girba <tudor(a)tudorgirba.com>: >>> >>> Even more awesomeness :). Thanks for doing this! >>> >>> Doru >>> >>> >>>> On Oct 26, 2017, at 2:02 PM, Torsten Bergmann <astares(a)gmx.de> wrote: >>>> >>>> I already contacted Guille in a private message on this one. >>>> >>>> Because now we have three (sorted in order of appearance): >>>> >>>> 1. https://balletie.github.io/GitHub/ (from Balletie, very complete) >>>> 2. https://github.com/astares/GitHub-API (a wrapper I wrote to play with the API) >>>> 3. https://github.com/guillep/github-api (Guille) >>>> >>>> If time permits we should consolidate this into a single one (maybe on https://github.com/pharo-vcs/github-api) >>>> >>>> Guille will contact Balletie as a next step. >>>> >>>> Thanks >>>> T. >>>> >>>> >>>>> Gesendet: Donnerstag, 26. Oktober 2017 um 13:32 Uhr >>>>> Von: "Tudor Girba" <tudor(a)tudorgirba.com> >>>>> An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >>>>> Betreff: Re: [Pharo-dev] Github API on github >>>>> >>>>> Awesome. >>>>> >>>>> Doru >>>>> >>>>> >>>>>> On Oct 20, 2017, at 10:07 AM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >>>>>> >>>>>> Hi guys, >>>>>> >>>>>> I extracted and extended some of the github API from iceberg, so it can be used as a standalone project. Maybe this is useful for somebody. >>>>>> >>>>>> https://github.com/guillep/github-api >>>>>> >>>>>> It should be easy to extend and add new functionalities, so don't hesitate if you need some missing request :) >>>>>> >>>>>> 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 >>>>>> >>>>>> Web: http://guillep.github.io >>>>>> Phone: +33 06 52 70 66 13 >>>>> >>>>> -- >>>>> www.tudorgirba.com >>>>> www.feenk.com >>>>> >>>>> âThe smaller and more pervasive the hardware becomes, the more physical the software gets." >>>>> >>>>> >>>>> >>>> >>> >>> -- >>> www.tudorgirba.com >>> www.feenk.com >>> >>> "Presenting is storytelling." >>

Oct. 27, 2017

Re: [Pharo-dev] , for vector creation

by Tudor Girba

Indeed, we have BlInsets that are used for either padding or margin. Doru > On Oct 26, 2017, at 11:43 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Doru > > I was thinking that you would also have BlMargin because Margin is a > nice concept. > When I introduced it with Igor it simplified a lot of code in expand, > shrink and other operations. > > Stef > > On Thu, Oct 26, 2017 at 11:39 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> Hi, >> >> To make the conversation more interesting, in Bloc we also have BlPoint with subclasses for 2D, 3D and 4D. The reason for this is that we model explicitly the intention of usage even if they share the instance variable names. We did not use Point because we needed 3D and 4D as well and Point has too many meanings that are conflated into one. >> >> This pattern was used everywhere we could. For example, we have BlBounds instead of Rectangle (actually, this is also because of performance reasons of working directly with 4 numbers rather than 2 points). >> >> Of course, these come with an apparent extra maintenance cost. So, if we see a possibility of unifying we should definitely take it, and this is where external reviewers can help to point out possibilities. We should just not unify just for the sake of it. >> >> Cheers, >> Doru >> >>> On Oct 26, 2017, at 10:57 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>> Hi, >>> >>>> On Oct 26, 2017, at 10:36 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >>>> >>>> 2017-10-26 10:20 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: >>>> Hi, >>>>> On Oct 26, 2017, at 10:10 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >>>>> >>>>> Another question. >>>>> >>>>> Will not these vectors deprecate Point in future ? Imaging that we will completely move to Bloc. >>>> >>>> No. Point is a perfectly reasonable data structure to describe a position. A Vector is something else and has other contracts. The coincidence is that they share the same variables, but they have different API. For example, a vector has #length. A point does not. >>>> >>>> Now Point implements most vector operations. The #length is defined as radius by #r message. I imaging that with new vector you will reimplement many of Point methods. Also I doubt that Point plays any role in system which is different than math vector. >>> >>> I think that over time we have accumulated all sorts of other usages for Point. For example, Rectangle uses origin and corner as a position not as vectors. >>> >>> Doru >>> >>>> >>>>> And what about Rectangle? (Bloc implements own BlRectangle). >>>> >>>> These two do not have the same semantics. BlRectangle is a BlGeometry and is used for defining a path within an element. BlRectangle is polymorphic with other paths such as BlEllipse or BlPolygon. Rectangle is a generic data structure that can be used for other purposes. >>>> >>>> We should definitely try to find commonalities and opportunities for unification. However, we should not confuse state with types which are defined by the purpose they are used for (and associated behavior). >>>> >>>> Doru >>>> >>>> >>>> >>>>> 2017-10-26 9:26 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: >>>>> #(1 3 4 5 7 -2) asVector >>>>> >>>>> Meh. >>>>> Ugly. >>>>> >>>>> { 1. 3. 4. a. b } asVector >>>>> >>>>> is the natural consequence. >>>>> >>>>> v := (1,3,4,5,7,-2) asVector >>>>> >>>>> keeps the parens. But why do I need to do that? >>>>> >>>>> Autoformatting messing with my parentheses is just a mistake. >>>>> I put them in, leave them where they are, 'kay? I do not need an editor that rewrites what I tell it. AST power or not. >>>>> >>>>> And frankly, I like the "Feenk way of doing things" most of the time, so I am willing to go that route. >>>>> >>>>> Phil >>>>> >>>>> >>>>> >>>>> On Thu, Oct 26, 2017 at 8:52 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>>>>> >>>>>> Automatic formatting will turn it into >>>>>> >>>>>> vector := 1,3,4,5,7,-2. >>>>>> >>>>>> Which is not as nice. >>>>>> >>>>>> And even though it looks ok for literal numbers (#(1 3 4 5 7 -2) asVector would work too), this starts to look quite generic: >>>>>> >>>>>> vector := width, height, depth. >>>>>> >>>>>> >>>>>> Question: why not extend @ notation? >>>>>> >>>>>> x @ y @ z? >>>>>> >>>>>> Peter >>>>>> >>>>>> >>>>>> >>>>>> On Thu, Oct 26, 2017 at 8:22 AM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: >>>>>>> >>>>>>> I also like the , message for those vectors and the concatenation of dimensions makes sense. >>>>>>> >>>>>>> vector := (1,3,4,5,7,-2). >>>>>>> >>>>>>> looks how it should be. >>>>>>> >>>>>>> Readable, easy to translate vector stuff from reference text. >>>>>>> >>>>>>> Phil >>>>>>> >>>>>>> >>>>>>> On Thu, Oct 26, 2017 at 7:00 AM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Am 25.10.2017 10:50 PM schrieb "Torsten Bergmann" <astares(a)gmx.de>: >>>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> there might be reasons for an own 2D vector class (instead of using Point). >>>>>>>> But still I dislike the reimplementation of "," because for me so far it >>>>>>>> has the meaning of "concatenating things". >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Like concatenating coordinates :-) >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Here you redefine it to create vector instances and it works only up to three >>>>>>>> so far. Right? >>>>>>>> >>>>>>>> I understand that this gives some similarities with the math notation (1,2) >>>>>>>> but I personally would prefer to use: >>>>>>>> >>>>>>>> 1@2 asVector >>>>>>>> >>>>>>>> or Vector2D x: 1 y: 2 >>>>>>>> >>>>>>>> Thx >>>>>>>> T. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> Gesendet: Mittwoch, 25. Oktober 2017 um 20:06 Uhr >>>>>>>>> Von: "Tudor Girba" <tudor(a)tudorgirba.com> >>>>>>>>> An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >>>>>>>>> Betreff: [Pharo-dev] , for vector creation >>>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> As mentioned in the separate thread, we played with introducing the extension: >>>>>>>>> >>>>>>>>> , aNumber >>>>>>>>> ^ BlVector2D x: self y: aNumber >>>>>>>>> >>>>>>>>> This means that (10,20) will return a 2D vector. >>>>>>>>> >>>>>>>>> We also have (10,20,30) which returns a 3D vector. >>>>>>>>> >>>>>>>>> , is used for different meanings already in the image beside the collection concatenation. For example, in FileReference is adds a file extension. And Exceptions create a collection. In other packages, PetitParser uses it as a sequence operator. >>>>>>>>> >>>>>>>>> Please voice your concerns. >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> Doru >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> www.tudorgirba.com >>>>>>>>> www.feenk.com >>>>>>>>> >>>>>>>>> "Every thing should have the right to be different." >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>>> -- >>>> www.tudorgirba.com >>>> www.feenk.com >>>> >>>> "When people care, great things can happen." >>>> >>>> >>>> >>>> >>>> >>>> >>> >>> -- >>> www.tudorgirba.com >>> www.feenk.com >>> >>> "If you interrupt the barber while he is cutting your hair, >>> you will end up with a messy haircut." >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "We are all great at making mistakes." >> >> >> >> >> >> >> >> >> > -- www.tudorgirba.com www.feenk.com "If you can't say why something is relevant, it probably isn't."

Oct. 27, 2017

Re: [Pharo-dev] curious

by Ben Coman

Ahh... it was a brain freeze. The [meta] tab shows the methods of the selected instance, but my "key" is not an instance of PackageCheck, it the PackageCheck Class, so the class-side methods are shown. cheers -ben On Fri, Oct 27, 2017 at 1:30 PM, Ben Coman <btc(a)openinworld.com> wrote: > I wasn't what to title this post. > Please just take a moment to inspect... > > Object subclasses > collect: [:class| class -> class methods size] > thenSelect: [:map| > (map value between: 1 and: 5) and: > (map key printString first = $P) ]. > > Then choose (a random example)... > "PackageChecker->1" item > "key" variable > [Meta] tab > "PackageCheck class" item > > and I'd expect a single method shown, rather than the zero I see. > Actually I'd expect the choice in that last step > to be "PackageCheck" rather than "PackageCheck class" > > Now continue with, browse "PackageCheck class" > then switch to instance side, and there I see the single class I expected > earlier. > > So is there something wrong there, or am I having a brain freeze? > > cheers -ben >

Oct. 27, 2017

curious

by Ben Coman

I wasn't what to title this post. Please just take a moment to inspect... Object subclasses collect: [:class| class -> class methods size] thenSelect: [:map| (map value between: 1 and: 5) and: (map key printString first = $P) ]. Then choose (a random example)... "PackageChecker->1" item "key" variable [Meta] tab "PackageCheck class" item and I'd expect a single method shown, rather than the zero I see. Actually I'd expect the choice in that last step to be "PackageCheck" rather than "PackageCheck class" Now continue with, browse "PackageCheck class" then switch to instance side, and there I see the single class I expected earlier. So is there something wrong there, or am I having a brain freeze? cheers -ben

Oct. 27, 2017