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

Re: [Pharo-dev] , for vector creation

by Hilaire

A clear separation between Point and Vector makes perfectly sense. Ideally, Point should be deprecated then. Otherwise it is a complexity growth. Hilaire Le 26/10/2017 Ã 11:39, Tudor Girba a Ã©critÂ : > 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. -- Dr. Geo http://drgeo.eu

Oct. 26, 2017

Re: [Pharo-dev] , for vector creation

by Tudor Girba

Hi, > On Oct 26, 2017, at 4:09 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Peter UhnÃ¡k wrote >> But in both cases #, is sent to FileReference/Petit parser instance, so it >> is contained. >> You would use it on a (generic) Number and tie it to specific Bloc >> meaning. > > Yes, this is exactly the problem. It is a reintroduction of a message like > #name, which plagued us for so long. We appropriate the meaning of `aNumber, > â¦` for the whole world. Now, if in MyCoolProject I want to implement > aNumber>>#, I will break the system. Maybe we can follow the FS/PP pattern > and scope the message to only-vector-like-things via an initial message, so > just like `$f asParser, â¦`, have `1 {vector-appropriate-message}, â¦`? You mean like sending @ to a number, right? :) Doru > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > -- www.tudorgirba.com www.feenk.com "Reasonable is what we are accustomed with."

Oct. 26, 2017

Re: [Pharo-dev] , for vector creation

by Sean P. DeNigris

Peter UhnÃ¡k wrote > But in both cases #, is sent to FileReference/Petit parser instance, so it > is contained. > You would use it on a (generic) Number and tie it to specific Bloc > meaning. Yes, this is exactly the problem. It is a reintroduction of a message like #name, which plagued us for so long. We appropriate the meaning of `aNumber, â¦` for the whole world. Now, if in MyCoolProject I want to implement aNumber>>#, I will break the system. Maybe we can follow the FS/PP pattern and scope the message to only-vector-like-things via an initial message, so just like `$f asParser, â¦`, have `1 {vector-appropriate-message}, â¦`? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Oct. 26, 2017

Re: [Pharo-dev] Github API on github

by Esteban Lorenzano

> 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 :) 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. 26, 2017

Re: [Pharo-dev] Github API on github

by Norbert Hartl

Now the interesting question.... *drumroll* Will iceberg use this library??? 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. 26, 2017

Re: [Pharo-dev] Github API on github

by Tudor Girba

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. 26, 2017

Re: [Pharo-dev] Github API on github

by Torsten Bergmann

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." > > >

Oct. 26, 2017

Re: [Pharo-dev] OSWindow in Pharo 6.1 stable

by Tudor Girba

Thanks Ronie. Please keep us posted with the progress. Cheers, Doru > On Oct 19, 2017, at 7:48 PM, Ronie Salgado <roniesalg(a)gmail.com> wrote: > > Hi ClÃ©ment, > > Last night I was checking again the VM. If I remove the hack in the ioProcessEvents, I can receive the events with SDL2, but as soon as I type on the main Pharo window I get a crash in an objective-c message send by SDL2. I still need to debug SDL2 itself with debugging symbols. > > I am not sure whether I will be able to fix the problem without modifying SDL2. In the worst case escenario, we will have to move to the minheadless vm. > > Best regards, > Ronie > > 2017-10-18 4:49 GMT-03:00 ClÃ©ment Bera <bera.clement(a)gmail.com>: > Hi again, > > I made many more attempts since those mails: I wrote this page showing how to deploy my game in native app at 50fps on Linux, Mac and Windows. > > Currently I deploy with: > Ubuntu 64 bits: Pharo61-64 (Pharo61-32 also works with the right lib installed) > Mac OS X 64 bits: Pharo5Alpha-32 (On Pharo61 the keyboard events do not work correctly) > Windows 64 bits: Pharo61-32 (There are bugs with the SDL2 window, the top bar is not displayed, but the game work. Reportedly it would work better with Pharo61-64 but the default Pharo64 VM on Windows still does not feature the JIT, once the default VM does, I will update). > > My goal is to deploy on all platforms with Pharo61-64 (and later Pharo7-64). > > I wrote this mail since maybe you are interested in knowing that with Pharo5Alpha-32 and the set-up described on the page of my game the keyboard events work fine on Mac, so it may be possible to write a fix for Pharo61/Pharo7 based on that. > > Best, > > > > > On Fri, Sep 29, 2017 at 8:56 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Tx ronie! > > > On Fri, Sep 29, 2017 at 1:42 PM, Ronie Salgado <roniesalg(a)gmail.com> wrote: > > Hi ClÃ©ment, > > > > I just checked on my machine and it is also not working. It seems to be a VM > > bug. It will take me some time to debug it. I have some suspicious on > > ioProcessEvents . > > > > Best regards, > > Ronie > > > > 2017-09-29 10:39 GMT+02:00 ClÃ©ment Bera <bera.clement(a)gmail.com>: > >> > >> > >> > >> On Fri, Sep 29, 2017 at 10:29 AM, Hilaire <hilaire(a)drgeo.eu> wrote: > >>> > >>> Hi, > >>> > >>> IMHO, it will make Pharo much more robust if core libraries as sdl, > >>> cairo, etc will be shipped with each plateform dependent virtual machine and > >>> the image modified accordingly to use these core libraries. > >> > >> > >> That's how it is now but some of it is not working (Here SDL events and > >> there are 2 SDL2 libs by default). > >> > >> I think we should still have a minimal image starting with a minimal UI > >> without using FFI/SDL/Cairo or whatever lib. Else when we start on a > >> platform where one of this thing is not properly supported yet (See the > >> problem on the raspberry pie with some Pharo alpha version) it is too hard > >> to understand what is going on. > >> > >>> > >>> > >>> The delivery of Pharo application to end users is an issue because of > >>> these recuring problem. > >> > >> > >> Honestly I was trying to write a doc on how to deploy Pharo client app > >> with SDL2 and Cairo but I have only a version working in Pharo 4 on Mac and > >> Linux, while in theory I could have it working in Windows/Mac/Linux in the > >> latest Pharo. > >> > >>> > >>> Hilaire > >>> > >>> > >>> > >>> Le 28/09/2017 Ã 15:02, ClÃ©ment Bera a Ã©crit : > >>>> > >>>> Btw for some reason in the one-click version of Pharo 32 bits on Mac > >>>> there is 2 SDL plugins (libSDL2-2.0.0 and libSDL2), which leads to conflicts > >>>> (the VM use randomly one lib or the other). I randomly chose one that I use > >>>> and deleted the other one, do you have advises on which one I should prefer > >>>> ? Maybe the events are working only with the other one ? > >>>> > >>> > >>> -- > >>> Dr. Geo > >>> http://drgeo.eu > >>> > >>> > >>> > >> > > > > > > > -- > ClÃ©ment BÃ©ra > Pharo consortium engineer > https://clementbera.wordpress.com/ > BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq > -- www.tudorgirba.com www.feenk.com "We can create beautiful models in a vacuum. But, to get them effective we have to deal with the inconvenience of reality."

Oct. 26, 2017

Re: [Pharo-dev] Github API on github

by Tudor Girba

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."

Oct. 26, 2017

Re: [Pharo-dev] feenk log

by werner kassens

Hi Doru, you say BLVector is implemented as having instance vars x,y instead of using an Array (like polymath), i guess perhaps because of speed considerations? but i wonder why you then dont use FloatArrays for vectors, their precision, although generally bad, is sufficient for graphics and they are faster for vector operations? werner

Oct. 26, 2017