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

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

by ClÃ©ment Bera

Hi again, I made many more attempts since those mails: I wrote this page <https://github.com/clementbera/wizard-battle-arena> 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

Oct. 18, 2017

Re: [Pharo-dev] Writeup: how to contribute to Pharo

by Esteban Lorenzano

hi, > On 18 Oct 2017, at 08:39, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Esteban it would be good to make the remote handling more robust because many people face > this problem. if people enter a wrong url, we can't do anything. now, the RSD is another problem, not related with this one. Esteban > > On Tue, Oct 17, 2017 at 11:53 AM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > no is ok. > with the pharo version I know the iceberg version :) > > anyway your problem is that the remote for pharo is bad. > > you added git(a)github.com <mailto:git@github.com>:pharo/pharo.git and I do not think that exists. > Correct one is: > > git(a)github.com <mailto:git@github.com>:pharo-project/pharo.git > > Esteban > > >> On 17 Oct 2017, at 11:51, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com <mailto:hernan.morales@gmail.com>> wrote: >> >> I don't see any easy way to find the Iceberg version. >> >> Should I update Iceberg using this script also in Pharo 7? >> >> "Restore defaults" >> Iceberg enableMetacelloIntegration: false. >> MetacelloPharo30Platform select. >> >> "Update metacello" >> Metacello new >> baseline: 'Metacello'; >> repository: 'github://metacello/metacello:Pharo6.1/repository <>'; >> onConflict: [:e | e useIncoming ]; >> get; >> load. >> >> "Update iceberg" >> #( >> 'Iceberg-UI' >> 'Iceberg-Plugin-GitHub' >> 'Iceberg-Plugin' >> 'Iceberg-Metacello-Integration' >> 'Iceberg-Libgit-Tonel' >> 'Iceberg-Libgit-Filetree' >> 'Iceberg-Libgit' >> 'Iceberg' >> 'LibGit-Core') >> do: [ :each | (each asPackageIfAbsent: [ nil ]) ifNotNil: #removeFromSystem ]. >> Metacello new >> baseline: 'Iceberg'; >> repository: 'github://pharo-vcs/iceberg:v0.6 <>'; >> load. >> >> 2017-10-17 6:46 GMT-03:00 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com <mailto:hernan.morales@gmail.com>>: >> Hi Esteban, >> >> This one: >> >> wget -O- get.pharo.org/70+vm <http://get.pharo.org/70+vm> | bash - >> >> 2017-10-17 3:36 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: >> which Pharo version (and Iceberg version) do you have? >> >> Esteban >> >>> On 17 Oct 2017, at 04:36, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com <mailto:hernan.morales@gmail.com>> wrote: >>> >>> Hi Guille, >>> >>> In https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to… <https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to…> >>> >>> This part is not working for me: "Go back to iceberg, right click on the pharo repository and go to the Pharo entry. You'll see the option Create new branch from Fogbugz issue." >>> >>> Because there is no such "Pharo" option in the menu. See the attached screenshot. >>> >>> Did I miss something? >>> Any suggestion? >>> >>> >>> 2017-08-10 12:17 GMT-03:00 Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>>: >>> Hi, >>> >>> I've made some write up for the pharo part (not metacello or external projects) >>> >>> https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to… <https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to…> >>> >>> Of course, expect bugs on it :) Not everything is smooth. If you have comments, they are welcome. >>> >>> Guille >>> >>> -- >>> >>> Guille Polito >>> >>> Research Engineer >>> 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:+33%206%2052%2070%2066%2013> >>> <Clipboard01.png> >> >> >> > >

Oct. 18, 2017

Re: [Pharo-dev] Writeup: how to contribute to Pharo

by Guillermo Polito

On Tue, Oct 17, 2017 at 12:42 PM, HernÃ¡n Morales Durand < hernan.morales(a)gmail.com> wrote: > Thank you Esteban, that was the problem! :) > > Maybe guille wants to clarify the correct remote repository in the page: > https://github.com/guillep/PharoIntegrationProcess/wiki/ > Contribute-a-fix-to-Pharo after "You can click on the *Add remote* option > and configure a remote with a name and repository url." > Done that. Can you check if that's ok? > > Another thing. I created a PR with a fix for this bug : > https://pharo.fogbugz.com/f/cases/17754/CheckBoxModel- > RadioButtonModel-ignore-disable following the guide to the Step 3. > However I couldn't view any PR in my Github page (see attach). > > Do I miss something? > > > 2017-10-17 6:53 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> no is ok. >> with the pharo version I know the iceberg version :) >> >> anyway your problem is that the remote for pharo is bad. >> >> you added git@github.com:pharo/pharo.git and I do not think that exists. >> Correct one is: >> >> git@github.com:pharo-project/pharo.git >> >> Esteban >> >> >> On 17 Oct 2017, at 11:51, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> >> wrote: >> >> I don't see any easy way to find the Iceberg version. >> >> Should I update Iceberg using this script also in Pharo 7? >> >> "Restore defaults" >> Iceberg enableMetacelloIntegration: false. >> MetacelloPharo30Platform select. >> >> "Update metacello" >> Metacello new >> baseline: 'Metacello'; >> repository: 'github://metacello/metacello:Pharo6.1/repository'; >> onConflict: [:e | e useIncoming ]; >> get; >> load. >> >> "Update iceberg" >> #( >> 'Iceberg-UI' >> 'Iceberg-Plugin-GitHub' >> 'Iceberg-Plugin' >> 'Iceberg-Metacello-Integration' >> 'Iceberg-Libgit-Tonel' >> 'Iceberg-Libgit-Filetree' >> 'Iceberg-Libgit' >> 'Iceberg' >> 'LibGit-Core') >> do: [ :each | (each asPackageIfAbsent: [ nil ]) ifNotNil: >> #removeFromSystem ]. >> Metacello new >> baseline: 'Iceberg'; >> repository: 'github://pharo-vcs/iceberg:v0.6'; >> load. >> >> 2017-10-17 6:46 GMT-03:00 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com >> >: >> >>> Hi Esteban, >>> >>> This one: >>> >>> wget -O- get.pharo.org/70+vm | bash - >>> >>> 2017-10-17 3:36 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >>> >>>> which Pharo version (and Iceberg version) do you have? >>>> >>>> Esteban >>>> >>>> On 17 Oct 2017, at 04:36, HernÃ¡n Morales Durand < >>>> hernan.morales(a)gmail.com> wrote: >>>> >>>> Hi Guille, >>>> >>>> In https://github.com/guillep/PharoIntegrationProcess/wiki/Cont >>>> ribute-a-fix-to-Pharo >>>> >>>> This part is not working for me: "Go back to iceberg, right click on >>>> the pharo repository and go to the *Pharo* entry. You'll see the >>>> option *Create new branch from Fogbugz issue*." >>>> >>>> Because there is no such "Pharo" option in the menu. See the attached >>>> screenshot. >>>> >>>> Did I miss something? >>>> Any suggestion? >>>> >>>> >>>> 2017-08-10 12:17 GMT-03:00 Guillermo Polito <guillermopolito(a)gmail.com> >>>> : >>>> >>>>> Hi, >>>>> >>>>> I've made some write up for the pharo part (not metacello or external >>>>> projects) >>>>> >>>>> https://github.com/guillep/PharoIntegrationProcess/wiki/Cont >>>>> ribute-a-fix-to-Pharo >>>>> >>>>> Of course, expect bugs on it :) Not everything is smooth. If you have >>>>> comments, they are welcome. >>>>> >>>>> Guille >>>>> >>>>> -- >>>>> >>>>> Guille Polito >>>>> >>>>> Research Engineer >>>>> 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> >>>>> >>>> >>>> <Clipboard01.png> >>>> >>>> >>>> >>> >> >> > -- 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

Oct. 18, 2017

Re: [Pharo-dev] Writeup: how to contribute to Pharo

by Stephane Ducasse

Esteban it would be good to make the remote handling more robust because many people face this problem. On Tue, Oct 17, 2017 at 11:53 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > no is ok. > with the pharo version I know the iceberg version :) > > anyway your problem is that the remote for pharo is bad. > > you added git@github.com:pharo/pharo.git and I do not think that exists. > Correct one is: > > git@github.com:pharo-project/pharo.git > > Esteban > > > On 17 Oct 2017, at 11:51, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> > wrote: > > I don't see any easy way to find the Iceberg version. > > Should I update Iceberg using this script also in Pharo 7? > > "Restore defaults" > Iceberg enableMetacelloIntegration: false. > MetacelloPharo30Platform select. > > "Update metacello" > Metacello new > baseline: 'Metacello'; > repository: 'github://metacello/metacello:Pharo6.1/repository'; > onConflict: [:e | e useIncoming ]; > get; > load. > > "Update iceberg" > #( > 'Iceberg-UI' > 'Iceberg-Plugin-GitHub' > 'Iceberg-Plugin' > 'Iceberg-Metacello-Integration' > 'Iceberg-Libgit-Tonel' > 'Iceberg-Libgit-Filetree' > 'Iceberg-Libgit' > 'Iceberg' > 'LibGit-Core') > do: [ :each | (each asPackageIfAbsent: [ nil ]) ifNotNil: > #removeFromSystem ]. > Metacello new > baseline: 'Iceberg'; > repository: 'github://pharo-vcs/iceberg:v0.6'; > load. > > 2017-10-17 6:46 GMT-03:00 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> > : > >> Hi Esteban, >> >> This one: >> >> wget -O- get.pharo.org/70+vm | bash - >> >> 2017-10-17 3:36 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> >>> which Pharo version (and Iceberg version) do you have? >>> >>> Esteban >>> >>> On 17 Oct 2017, at 04:36, HernÃ¡n Morales Durand < >>> hernan.morales(a)gmail.com> wrote: >>> >>> Hi Guille, >>> >>> In https://github.com/guillep/PharoIntegrationProcess/wiki/Cont >>> ribute-a-fix-to-Pharo >>> >>> This part is not working for me: "Go back to iceberg, right click on the >>> pharo repository and go to the *Pharo* entry. You'll see the option *Create >>> new branch from Fogbugz issue*." >>> >>> Because there is no such "Pharo" option in the menu. See the attached >>> screenshot. >>> >>> Did I miss something? >>> Any suggestion? >>> >>> >>> 2017-08-10 12:17 GMT-03:00 Guillermo Polito <guillermopolito(a)gmail.com>: >>> >>>> Hi, >>>> >>>> I've made some write up for the pharo part (not metacello or external >>>> projects) >>>> >>>> https://github.com/guillep/PharoIntegrationProcess/wiki/Cont >>>> ribute-a-fix-to-Pharo >>>> >>>> Of course, expect bugs on it :) Not everything is smooth. If you have >>>> comments, they are welcome. >>>> >>>> Guille >>>> >>>> -- >>>> >>>> Guille Polito >>>> >>>> Research Engineer >>>> 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> >>>> >>> >>> <Clipboard01.png> >>> >>> >>> >> > >

Oct. 18, 2017

Re: [Pharo-dev] Compiler Explorer (for the Compiler guys) #offtopic

by Tudor Girba

Hi, This is already available since some time in the GTInspector. You can just inspect a compiled method. You will get both the bytecode and the AST (with source tracking, too). In fact, this was one of the original reasons why GTInspector exists: I wanted to figure out how the AST is structured so that I can write queries against it :). Cheers, Doru > On Oct 17, 2017, at 10:03 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > > I'm sure we could do this with ease, because we already can see the bytecodes. > > https://godbolt.org/ > > Regards! > > Esteban A. Maringolo > -- www.tudorgirba.com www.feenk.com "The coherence of a trip is given by the clearness of the goal."

Oct. 18, 2017

Re: [Pharo-dev] Help for the mooc

by Stephane Ducasse

Tx! I should fix it but probably the videos are still using the old one. On Tue, Oct 17, 2017 at 10:36 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > >> On 17 Oct 2017, at 22:29, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> >> Hi >> >> students have a problem with the following in Pharo 50 (we could not upgrade) >> >> (ZnEasy getPng: 'http://pharo.org/web/files/pharo.png') asMorph openInWindow >> >> >> ConnectionClosed : connection closed while waiting for data >> >> And well this is super annoying. >> >> Stef > > This is fixed in later versions. You can try the following: > > (ZnEasy getPng: 'http://pharo.org/files/pharo.png') asMorph openInWindow. > > The reason that last one works is that http://pharo.org/files/pharo.png is an http url that resolves directly, while http://pharo.org/web/files/pharo.png redirects to an https equivalent which can only be read with #serverName support. For this, you need not only a more recent version of Zinc, but also a newer VM with a more recent SSL plugin. > > Sven

Oct. 18, 2017

Re: [Pharo-dev] UnifiedFFI Docs

by Stephane Ducasse

Please do not hesitate to do Pull Requests. Luc told me that he wants to do a pass on it and Esteban promises that to me but he is super busy. Stef On Wed, Oct 18, 2017 at 5:54 AM, Todd Blanchard <tblanchard(a)mac.com> wrote: > Wonderful! Thanks. > >> On Oct 17, 2017, at 3:45 PM, stephan <stephan(a)stack.nl> wrote: >> >> On 17-10-17 23:06, Todd Blanchard wrote: >>> Anyone know what happened to this? >>> https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre… >> >> https://github.com/SquareBracketAssociates/Booklet-uFFI >> >> has a link to a bintray pdf download >> >> Stephan >> >> >> > >

Oct. 18, 2017

Re: [Pharo-dev] UnifiedFFI Docs

by Todd Blanchard

Wonderful! Thanks. > On Oct 17, 2017, at 3:45 PM, stephan <stephan(a)stack.nl> wrote: > > On 17-10-17 23:06, Todd Blanchard wrote: >> Anyone know what happened to this? >> https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre… > > https://github.com/SquareBracketAssociates/Booklet-uFFI > > has a link to a bintray pdf download > > Stephan > > >

Oct. 18, 2017

Re: [Pharo-dev] UnifiedFFI Docs

by stephan

On 17-10-17 23:06, Todd Blanchard wrote: > Anyone know what happened to this? > > https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre… > https://github.com/SquareBracketAssociates/Booklet-uFFI has a link to a bintray pdf download Stephan

Oct. 17, 2017

Re: [Pharo-dev] Compiler Explorer (for the Compiler guys) #offtopic

by Mariano Martinez Peck

heheheheh I had a similar idea years ago [1]. It looks like I start implementing it [2], but I cannot find if I finished it or not LOL. [1] http://forum.world.st/Re-The-idea-of-VM-Learning-Toolkit-td3461173.html [2] https://www.list.inf.unibe.ch/pipermail/moose-dev/2011-April/007655.html On Tue, Oct 17, 2017 at 6:52 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > You can do that with the VMMaker package loaded. There is not all the UI, > but you can print the assembly code in the Transcript. > > On Tue, Oct 17, 2017 at 10:03 PM, Esteban A. Maringolo < > emaringolo(a)gmail.com> wrote: > >> I'm sure we could do this with ease, because we already can see the >> bytecodes. >> >> https://godbolt.org/ >> >> Regards! >> >> Esteban A. Maringolo >> >> > > > -- > ClÃ©ment BÃ©ra > Pharo consortium engineer > https://clementbera.wordpress.com/ > BÃ¢timent B 40, avenue Halley 59650 > <https://maps.google.com/?q=40,+avenue+Halley+59650%C2%A0Villeneuve+d'Ascq&entry=gmail&source=g>Villeneuve > d > <https://maps.google.com/?q=40,+avenue+Halley+59650%C2%A0Villeneuve+d'Ascq&entry=gmail&source=g> > 'Ascq > <https://maps.google.com/?q=40,+avenue+Halley+59650%C2%A0Villeneuve+d'Ascq&entry=gmail&source=g> > -- Mariano http://marianopeck.wordpress.com

Oct. 17, 2017