September 2018 - Pharo-users

Re: [Pharo-users] [ANN] Migrated Artefact to GitHub

by Norbert Hartl

> Am 28.09.2018 um 10:14 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: > > > >> On Fri, Sep 28, 2018 at 9:07 AM Torsten Bergmann <astares(a)gmx.de> wrote: >> Hi Guille, >> >> Yes, thanks. But it looks like the history is gone now - as you seem to load and then commited >> with Iceberg only. > > Yes, that's what I did. > >> >> By using Peters "STHub -> Git migration tool" the history of the changes is preserved and moved into >> the git history too. See https://github.com/peteruhnak/git-migration >> Would it be possible to use that? > > Yes, that could be used. The thing is that I'm not Artefact's maintainer, and I did not want to invest more than one hour on this. > But if someone wants to take the bull from the horns, that's ok ^^. > It is not that much work. Just copying the code under your username I consider rude. I spent a lot of time migrating repos to github of packages Iâm not the maintainer of. The git-migration of Peter is so easy to use there is no reason not to use. History is important Norbert > Guille

Sept. 28, 2018

Re: [Pharo-users] GTDocument how to

by Craig

Hi, I have found that moving the image and changes files onto a RAMdisk makes a huge difference to the install time of large packages. Give it a try. Craig -----Original Message----- From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Tim Mackinnon Sent: Friday, 28 September 2018 19:53 To: Any question about pharo is welcome Subject: Re: [Pharo-users] GTDocument how to When I installed GTDocumenter into a clean P61 image it took a really long time (like 20+ mins), so it may be something you have to wait out. It does beg the question why it takes so long? Actually all of our code loading is quite slow compared to other languages that load a lot more code. Not sure if if itâs ever been optimised ? Tim Sent from my iPhone > On 28 Sep 2018, at 05:58, Hilaire <hilaire(a)drgeo.eu> wrote: > >> Le 27/09/2018 Ã 16:52, Juraj Kubelka via Pharo-users a Ã©crit : >> >>> On Sep 27, 2018, at 10:41, Hilaire >>> <hilaire(a)drgeo.eu >>> <mailto:hilaire@drgeo.eu>> wrote: >>> >>> Thanks for the tips. Where should be key in this text? >> >> What do you mean? You can edit the text as you wish. > > Do not forget, what is obvious for one may not be for another. I could > write a book full of anecdotes with obvious features in DrGeo not so > obvious for a newbie. > > So you write this text in playground and inspect? > >> >> By evaluating and inspecting: >> >> -=-=-=- >> GtDocumenter editorForText: 'This is a Dr. Geo tutorial. Evaluate the >> following script: >> >> [[[ >> "A Dr. Geo script that returns DrGeo canvasâ >> ]]] >> >> Extensions are done using ==<gtView>== pragmas. >> ' >> -=-=-=- >> >> I have a text editor in an inspector where I can edit the Documenter >> content. >> >> >> Do you have the same? > > No, never saw that. I installed from: > Metacello new > baseline: 'GToolkit'; > repository: 'github://feenkcom/gtoolkit/src'; > load. > >> >>> >>> I went installing DrGeo along Documenter in P6.1, but it is stalled when >>> installing XML dependecies (a bit old, true). >>> >>> Conflict with XML? or Issue with DrGeo on P6.1, may be both. >> >> How can I install DrGeo? I do not see a Monticello script on the >> DrGeo.eu <http://DrGeo.eu> web page. > > I am afraid it is a bit tedious at first as it is not github based, but > Launchpad. > Read INSTALL file for full instruction: > https://bazaar.launchpad.net/~drgeo-developers/drgeo/trunk/view/head:/src/I… > >> >>> >>> This is so fragile. >> >> Keep in mind that GToolkit, including Documenter, is in alpha version. > > I did not have GToolkit in mind when I wrote fragile, more likely the > whole Smalltalk things. As I wrote in my previous email, my issue was > when installing DrGeo on a P6.1 image with GToolkit already installed. I > am not sure about why the process was hanging when installing XML's Dr. > Geo requirement. The image is then frozen > Ok may be I can't install DrGeo on P6.1, I still have error > (screenshot). In the other I failed to installing GToolkit on P7. > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > > <Capture du 2018-09-27 19-48-36.png>

Sept. 28, 2018

Re: [Pharo-users] GTDocument how to

by Tudor Girba

Hi, Please load the whole GT. Also, in the meantime we switched to Tonel which should speedup the loading time significantly. Cheers, Doru > On Sep 28, 2018, at 7:53 PM, Tim Mackinnon <tim(a)testit.works> wrote: > > When I installed GTDocumenter into a clean P61 image it took a really long time (like 20+ mins), so it may be something you have to wait out. > > It does beg the question why it takes so long? Actually all of our code loading is quite slow compared to other languages that load a lot more code. Not sure if if itâs ever been optimised ? > > Tim > > Sent from my iPhone > >> On 28 Sep 2018, at 05:58, Hilaire <hilaire(a)drgeo.eu> wrote: >> >>> Le 27/09/2018 Ã 16:52, Juraj Kubelka via Pharo-users a Ã©crit : >>> >>>> On Sep 27, 2018, at 10:41, Hilaire >>>> <hilaire(a)drgeo.eu >>>> <mailto:hilaire@drgeo.eu>> wrote: >>>> >>>> Thanks for the tips. Where should be key in this text? >>> >>> What do you mean? You can edit the text as you wish. >> >> Do not forget, what is obvious for one may not be for another. I could >> write a book full of anecdotes with obvious features in DrGeo not so >> obvious for a newbie. >> >> So you write this text in playground and inspect? >> >>> >>> By evaluating and inspecting: >>> >>> -=-=-=- >>> GtDocumenter editorForText: 'This is a Dr. Geo tutorial. Evaluate the >>> following script: >>> >>> [[[ >>> "A Dr. Geo script that returns DrGeo canvasâ >>> ]]] >>> >>> Extensions are done using ==<gtView>== pragmas. >>> ' >>> -=-=-=- >>> >>> I have a text editor in an inspector where I can edit the Documenter >>> content. >>> >>> >>> Do you have the same? >> >> No, never saw that. I installed from: >> Metacello new >> baseline: 'GToolkit'; >> repository: 'github://feenkcom/gtoolkit/src'; >> load. >> >>> >>>> >>>> I went installing DrGeo along Documenter in P6.1, but it is stalled when >>>> installing XML dependecies (a bit old, true). >>>> >>>> Conflict with XML? or Issue with DrGeo on P6.1, may be both. >>> >>> How can I install DrGeo? I do not see a Monticello script on the >>> DrGeo.eu <http://DrGeo.eu> web page. >> >> I am afraid it is a bit tedious at first as it is not github based, but >> Launchpad. >> Read INSTALL file for full instruction: >> https://bazaar.launchpad.net/~drgeo-developers/drgeo/trunk/view/head:/src/I… >> >>> >>>> >>>> This is so fragile. >>> >>> Keep in mind that GToolkit, including Documenter, is in alpha version. >> >> I did not have GToolkit in mind when I wrote fragile, more likely the >> whole Smalltalk things. As I wrote in my previous email, my issue was >> when installing DrGeo on a P6.1 image with GToolkit already installed. I >> am not sure about why the process was hanging when installing XML's Dr. >> Geo requirement. The image is then frozen >> Ok may be I can't install DrGeo on P6.1, I still have error >> (screenshot). In the other I failed to installing GToolkit on P7. >> >> Hilaire >> >> -- >> Dr. Geo >> http://drgeo.eu >> >> <Capture du 2018-09-27 19-48-36.png> > > -- www.feenk.com "Every thing should have the right to be different."

Sept. 28, 2018

Re: [Pharo-users] GTDocument how to

by Tim Mackinnon

When I installed GTDocumenter into a clean P61 image it took a really long time (like 20+ mins), so it may be something you have to wait out. It does beg the question why it takes so long? Actually all of our code loading is quite slow compared to other languages that load a lot more code. Not sure if if itâs ever been optimised ? Tim Sent from my iPhone > On 28 Sep 2018, at 05:58, Hilaire <hilaire(a)drgeo.eu> wrote: > >> Le 27/09/2018 Ã 16:52, Juraj Kubelka via Pharo-users a Ã©crit : >> >>> On Sep 27, 2018, at 10:41, Hilaire >>> <hilaire(a)drgeo.eu >>> <mailto:hilaire@drgeo.eu>> wrote: >>> >>> Thanks for the tips. Where should be key in this text? >> >> What do you mean? You can edit the text as you wish. > > Do not forget, what is obvious for one may not be for another. I could > write a book full of anecdotes with obvious features in DrGeo not so > obvious for a newbie. > > So you write this text in playground and inspect? > >> >> By evaluating and inspecting: >> >> -=-=-=- >> GtDocumenter editorForText: 'This is a Dr. Geo tutorial. Evaluate the >> following script: >> >> [[[ >> "A Dr. Geo script that returns DrGeo canvasâ >> ]]] >> >> Extensions are done using ==<gtView>== pragmas. >> ' >> -=-=-=- >> >> I have a text editor in an inspector where I can edit the Documenter >> content. >> >> >> Do you have the same? > > No, never saw that. I installed from: > Metacello new > baseline: 'GToolkit'; > repository: 'github://feenkcom/gtoolkit/src'; > load. > >> >>> >>> I went installing DrGeo along Documenter in P6.1, but it is stalled when >>> installing XML dependecies (a bit old, true). >>> >>> Conflict with XML? or Issue with DrGeo on P6.1, may be both. >> >> How can I install DrGeo? I do not see a Monticello script on the >> DrGeo.eu <http://DrGeo.eu> web page. > > I am afraid it is a bit tedious at first as it is not github based, but > Launchpad. > Read INSTALL file for full instruction: > https://bazaar.launchpad.net/~drgeo-developers/drgeo/trunk/view/head:/src/I… > >> >>> >>> This is so fragile. >> >> Keep in mind that GToolkit, including Documenter, is in alpha version. > > I did not have GToolkit in mind when I wrote fragile, more likely the > whole Smalltalk things. As I wrote in my previous email, my issue was > when installing DrGeo on a P6.1 image with GToolkit already installed. I > am not sure about why the process was hanging when installing XML's Dr. > Geo requirement. The image is then frozen > Ok may be I can't install DrGeo on P6.1, I still have error > (screenshot). In the other I failed to installing GToolkit on P7. > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > > <Capture du 2018-09-27 19-48-36.png>

Sept. 28, 2018

Re: [Pharo-users] [ANN] Migrated Artefact to GitHub

by Sean P. DeNigris

Guillermo Polito wrote > I did not want to invest more than one hour on this. The migration tool would have been much quicker than that ;-) ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Sept. 28, 2018

Re: [Pharo-users] [ANN] Migrated Artefact to GitHub

by Norbert Hartl

+1000 Please use the git-migration tool. Keeping the history is important. Takes only a couple of minutes to do > Am 28.09.2018 um 09:06 schrieb Torsten Bergmann <astares(a)gmx.de>: > > Hi Guille, > > Yes, thanks. But it looks like the history is gone now - as you seem to load and then commited > with Iceberg only. > > By using Peters "STHub -> Git migration tool" the history of the changes is preserved and moved into > the git history too. See https://github.com/peteruhnak/git-migration > > Would it be possible to use that? > > Thx > T. > > > Gesendet: Donnerstag, 27. September 2018 um 15:40 Uhr > Von: "Norbert Hartl" <norbert(a)hartl.name> > An: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> > Cc: "Discusses Development of Pharo" <pharo-dev(a)lists.pharo.org> > Betreff: Re: [Pharo-users] [ANN] Migrated Artefact to GitHub > > > Super! Thanks > > Norbert > Am 27.09.2018 um 11:26 schrieb Guillermo Polito <guillermopolito@gmail.com[mailto:guillermopolito@gmail.com]>: > > > Hi all, > > I've moved the Artefact library to GitHub (https://github.com/pharo-contributions/Artefact[https://github.com/pharo-co…) > > I've also made some changes to it in the way and made a 1.7.0 version with: > - support for Pharo7 streams > - a baseline > > So, people using Artifact, you can contribute through pull requests ^^, > 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 >

Sept. 28, 2018

Re: [Pharo-users] [ANN] Migrated Artefact to GitHub

by Guillermo Polito

On Fri, Sep 28, 2018 at 9:07 AM Torsten Bergmann <astares(a)gmx.de> wrote: > Hi Guille, > > Yes, thanks. But it looks like the history is gone now - as you seem to > load and then commited > with Iceberg only. > Yes, that's what I did. > > By using Peters "STHub -> Git migration tool" the history of the changes > is preserved and moved into > the git history too. See https://github.com/peteruhnak/git-migration Would it be possible to use that? > Yes, that could be used. The thing is that I'm not Artefact's maintainer, and I did not want to invest more than one hour on this. But if someone wants to take the bull from the horns, that's ok ^^. Guille

Sept. 28, 2018

Re: [Pharo-users] [ANN] Migrated Artefact to GitHub

by Torsten Bergmann

Hi Guille, Yes, thanks. But it looks like the history is gone now - asÂ you seem to load and then commited with Iceberg only.Â By using Peters "STHub -> Git migration tool" the history of the changes is preserved and moved into the git history too.Â See https://github.com/peteruhnak/git-migration Â Would it be possible to use that? Â Thx T.Â Â Gesendet:Â Donnerstag, 27. September 2018 um 15:40 Uhr Von:Â "Norbert Hartl" <norbert(a)hartl.name> An:Â "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> Cc:Â "Discusses Development of Pharo" <pharo-dev(a)lists.pharo.org> Betreff:Â Re: [Pharo-users] [ANN] Migrated Artefact to GitHub Â Super! Thanks Â Norbert Am 27.09.2018 um 11:26 schrieb Guillermo Polito <guillermopolito@gmail.com[mailto:guillermopolito@gmail.com]>: Â Hi all, Â I've moved the Artefact library to GitHub (https://github.com/pharo-contributions/Artefact[https://github.com/pharo-co…) Â I've also made some changes to it in the way and made a 1.7.0 version with: Â - support for Pharo7 streams Â - a baseline Â So, people using Artifact, you can contribute through pull requests ^^, 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

Sept. 28, 2018

Re: [Pharo-users] [Demo] Creating Bloc Widgets in Pharo

by Stephan Eggermont

Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > This is nice. Shows off some impressive capabilities. > > Not sure many people are capable of coming up this kind of code though ;-) I hope to provide enough examples that the patterns become visible Stephan

Sept. 27, 2018

Re: [Pharo-users] Pharo 7.0 code documentation

by Hilaire

Hi Dario You write comment per class, directly from the class browser. See Fraction class as an example. Or do need something else? Hilaire -- Dr. Geo http://drgeo.eu

Sept. 27, 2018

Re: [Pharo-users] GTDocument how to

by Hilaire

Le 27/09/2018 Ã 16:52, Juraj Kubelka via Pharo-users a Ã©critÂ : > >> On Sep 27, 2018, at 10:41, Hilaire >> <hilaire(a)drgeo.eu >> <mailto:hilaire@drgeo.eu>> wrote: >> >> Thanks for the tips. Where should be key in this text? > > What do you mean? You can edit the text as you wish. Do not forget, what is obvious for one may not be for another. I could write a book full of anecdotes with obvious features in DrGeo not so obvious for a newbie. So you write this text in playground and inspect? > > By evaluating and inspecting:Â > > -=-=-=- > GtDocumenter editorForText: 'This is a Dr. Geo tutorial. Evaluate the > following script: > > [[[ > "A Dr. Geo script that returns DrGeo canvasâÂ > ]]] > > Extensions are done using ==<gtView>== pragmas. > ' > -=-=-=- > > I have a text editor in an inspector where I can edit the Documenter > content.Â > > > Do you have the same? No, never saw that. I installed from: Metacello new Â Â baseline: 'GToolkit'; Â Â repository: 'github://feenkcom/gtoolkit/src'; Â Â load. > >> >> I went installing DrGeo along Documenter in P6.1, but it is stalled when >> installing XML dependecies (a bit old, true). >> >> Conflict with XML? or Issue with DrGeo on P6.1, may be both. > > How can I install DrGeo? I do not see a Monticello script on the > DrGeo.eu <http://DrGeo.eu> web page. I am afraid it is a bit tedious at first as it is not github based, but Launchpad. Read INSTALL file for full instruction: https://bazaar.launchpad.net/~drgeo-developers/drgeo/trunk/view/head:/src/I… > >> >> This is so fragile. > > Keep in mind that GToolkit, including Documenter, is in alpha version. I did not have GToolkit in mind when I wrote fragile, more likely the whole Smalltalk things. As I wrote in my previous email, my issue was when installing DrGeo on a P6.1 image with GToolkit already installed. I am not sure about why the process was hanging when installing XML's Dr. Geo requirement. The image is then frozen Â Ok may be I can't install DrGeo on P6.1, I still have error (screenshot). In the other I failed to installing GToolkit on P7. Hilaire -- Dr. Geo http://drgeo.eu

Sept. 27, 2018

Pharo 7.0 code documentation

by Trussardi Dario Romano

Ciao, I would be interested in understanding how I can document the code directly in pharo. Can someone give me some reference - link about it? Thank you, Dario

Sept. 27, 2018

Re: [Pharo-users] [Pharo-dev] [ANN] Migrated Artefact to GitHub

by Alistair Grant

Hi Guille, I wasn't aware this existed - thanks for letting us know! Cheers, Alistair On Thu, 27 Sep 2018 at 15:41, Norbert Hartl <norbert(a)hartl.name> wrote: > > Super! Thanks > > Norbert > > Am 27.09.2018 um 11:26 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: > > Hi all, > > I've moved the Artefact library to GitHub (https://github.com/pharo-contributions/Artefact) > > I've also made some changes to it in the way and made a 1.7.0 version with: > - support for Pharo7 streams > - a baseline > > So, people using Artifact, you can contribute through pull requests ^^, > 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

Sept. 27, 2018

Re: [Pharo-users] GTDocument how to

by Juraj Kubelka

> On Sep 27, 2018, at 10:41, Hilaire <hilaire(a)drgeo.eu> wrote: > > Thanks for the tips. Where should be key in this text? What do you mean? You can edit the text as you wish. By evaluating and inspecting: -=-=-=- GtDocumenter editorForText: 'This is a Dr. Geo tutorial. Evaluate the following script: [[[ "A Dr. Geo script that returns DrGeo canvasâ ]]] Extensions are done using ==<gtView>== pragmas. ' -=-=-=- I have a text editor in an inspector where I can edit the Documenter content. Do you have the same? > > I went installing DrGeo along Documenter in P6.1, but it is stalled when > installing XML dependecies (a bit old, true). > > Conflict with XML? or Issue with DrGeo on P6.1, may be both. How can I install DrGeo? I do not see a Monticello script on the DrGeo.eu web page. > > This is so fragile. Keep in mind that GToolkit, including Documenter, is in alpha version. Juraj > > Hilaire > > > Le 27/09/2018 Ã 14:51, Juraj Kubelka via Pharo-users a Ã©crit : >> As far as I understand your description, Documenter should fit. You can start by using: >> >> -=-=-=- >> GtDocumenter editorForText: 'This is a Dr. Geo tutorial. Evaluate the following script: >> >> [[[ >> "A Dr. Geo script that returns DrGeo canvas" >> ]]] >> >> Extensions are done using ==<gtView>== pragmas. >> â >> -=-=-=- >> >> Let me know how it works for you. > > -- > Dr. Geo > http://drgeo.eu > > >

Sept. 27, 2018

Re: [Pharo-users] GTDocument how to

by Hilaire

Thanks for the tips. Where should be key in this text? I went installing DrGeo along Documenter in P6.1, but it is stalled when installing XML dependecies (a bit old, true). Conflict with XML? or Issue with DrGeo on P6.1, may be both. This is so fragile. Hilaire Le 27/09/2018 Ã 14:51, Juraj Kubelka via Pharo-users a Ã©critÂ : > As far as I understand your description, Documenter should fit. You can start by using: > > -=-=-=- > GtDocumenter editorForText: 'This is a Dr. Geo tutorial. Evaluate the following script: > > [[[ > "A Dr. Geo script that returns DrGeo canvas" > ]]] > > Extensions are done using ==<gtView>== pragmas. > â > -=-=-=- > > Let me know how it works for you. -- Dr. Geo http://drgeo.eu

Sept. 27, 2018

Re: [Pharo-users] [ANN] Migrated Artefact to GitHub

by Norbert Hartl

Super! Thanks Norbert > Am 27.09.2018 um 11:26 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: > > Hi all, > > I've moved the Artefact library to GitHub (https://github.com/pharo-contributions/Artefact) > > I've also made some changes to it in the way and made a 1.7.0 version with: > - support for Pharo7 streams > - a baseline > > So, people using Artifact, you can contribute through pull requests ^^, > 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

Sept. 27, 2018

Re: [Pharo-users] GTDocument how to

by Juraj Kubelka

Hi Hilaire, As far as I understand your description, Documenter should fit. You can start by using: -=-=-=- GtDocumenter editorForText: 'This is a Dr. Geo tutorial. Evaluate the following script: [[[ "A Dr. Geo script that returns DrGeo canvas" ]]] Extensions are done using ==<gtView>== pragmas. â -=-=-=- Let me know how it works for you. Juraj > On Sep 26, 2018, at 14:10, Hilaire <hilaire(a)drgeo.eu> wrote: > > Hi, > > I would like a document where user types in normal text and plugs in > DrGeo view. The drgeo view will be dual. It will be alternatively the > output of a DrGeo script (drgeo canvas) or the DrGeo script itself (code). > > The view will be interactive. In drgeo canvas mode, user plays with the > geometric construction, when switched to code mode, the user edits the > DrGeo script and recompute the DrGeo canvas output. > > Is GTDocument appropriate to do this? If so, where to start? > > Thanks > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > > >

Sept. 27, 2018

Re: [Pharo-users] Pharo on macOS Mojave

by Sven Van Caekenberghe

Pharo 7 certainly works fine. > On 27 Sep 2018, at 12:06, Manuel Leuenberger <leuenberger(a)inf.unibe.ch> wrote: > > Hi, > > Did anybody already try Pharo 6.1 on macOS Mojave? Are there any issues that would suggest not to upgrade soon? > > Cheers, > Manuel > >

Sept. 27, 2018

Pharo on macOS Mojave

by Manuel Leuenberger

Hi, Did anybody already try Pharo 6.1 on macOS Mojave? Are there any issues that would suggest not to upgrade soon? Cheers, Manuel

Sept. 27, 2018

[ANN] Migrated Artefact to GitHub

by Guillermo Polito

Hi all, I've moved the Artefact library to GitHub ( https://github.com/pharo-contributions/Artefact) I've also made some changes to it in the way and made a 1.7.0 version with: - support for Pharo7 streams - a baseline So, people using Artifact, you can contribute through pull requests ^^, 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

Sept. 27, 2018

Gtoolkit and fast trees

by Arturo Zambrano

Hi, I would like to understand the differences between tree and fastTree. I've got different behavior between tree and fastTree, the second failing with a subscript out of bounds. It happens when I expand the root node and select one of the children. .... it seems that the rootNode cannot find the children... (see below a screenshot). What is more strange is that using the same dataset sometimes it works as expected and sometimes not... I could not reproduce it in a short script (yet). Any pointer is welcome Thanks. [image: image.png]

Sept. 26, 2018

Re: [Pharo-users] [Pharo-dev] [ANN] Success story Mobility Map

by Norbert Hartl

> Am 25.09.2018 um 17:44 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > > >> On 25 Sep 2018, at 14:39, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> >> >>> Am 25.09.2018 um 12:52 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >>> >>> Wow. Very nice, well done. >>> >>> Any chance on some more technical details, as in what 'connected by a message queue for the communication' exactly means ? How did you approach micro services exactly ? >>> >> Sure :) > > Thanks, this is very interesting ! > >> The installation spawns multiple physical machines. All the machines are joined to a docker swarm. The installation is reified as either task or service from the view on the docker swarm. Meaning you instantiate an arbitrary amount of services and docker swarm distributes them among the physical machines. Usually you donât take control which is running where but you can. At this point you have spread dozens of pharo images among multiple machines and each of them has an IP address. Furthermore in docker swarm you have a reification of a network meaning that every instance in a network can see all other instances on this network. Each service can be reached by its service name in that network. Docker swarm does all the iptables/firewall and DNS setup for you. > > Are you happy with docker swarm's availability/fail-over behaviour ? In other words: does it work when one image/instance goes bad, does it detect and restore the missing functionality ? > Yes, Iâm very satisified. Instances are automatically restarted if they crash. And not necessarily on the same machine exactly how I expect it. Docker has something called Healthcheck. You can have a command executed every 20 seconds. I hooked this to a curl command and to your SUnit Rest handler. The rest is writing unit tests for server health. If tests fail in sequence the instances are taken out of operation and are replaced with a new instance. The same is done for updating. Instances are started in a fashion that one instance of the new image is started, if it survives a couple of health checks it is taken operational and an old one is taken out. Then the next new is started... For simple software updates you have zero-downtime deployment. >> In order to have communication between those runtimes we use rabbitmq because you were so nice writing a driver for it ;) The rabbitmq does have a support for cluster setup, meaning each of the physical machines has a rabbitmq installation and they know each other. So it does not matter to which instance you send messages to and on which you register for receiving messages. So every pharo image connects to the service rabbitmq and opens a queue for interaction. > > Same question: does RabbitMQ's clustering work well under stress/problems ? Syncing all queues between all machines sounds quite heavy (I never tried it, but maybe it just works). I did not yet have time to real stress test the queue. And you are right copying between nodes might be a lot but still I have the feeling it is better to have then a single instance but no real reason. We also use huge payloads which might have to change if we encounter problems. > >> Each service like the car sharing opens a queue e.g. /queue/carSharing and listens on it. The broker images are stateful so they open queues like /queue/mobility-map-afdeg32 where afdeg32 is the container id of the instance (hostname in docker). In each request the queue name to reply is sent as a header. So we can make sure that the right image gets the message back. This way we can have sticky sessions keeping volatile data in memory for the lifecycle of a session. There is one worker image which opens a queue /queue/mobility-map where session independent requests can be processed. > > I think I understand ;-) > >> In order to ease development we are sharing code between the broker and the micro service. Each micro service has a -Common package where the classes are in that build the interface. The classes in here are a kind of data entity facades. They use NeoJSON to map to and from a stream. The class name is send with the message as a header so the remote side knows what to materialize. The handling is unified for the four cases >> >> - Request as inquiry to another micro service >> - Response returns values to a Request >> - Error is transferred like a Response but is then signalled on the receiving side >> - Notification connects the announcers on the broker and the micro service side. > > Yes, makes total sense. > >> Asynchronous calls we solved using Promises and Futures. Each async call to the Q becomes a promise (that blocks on #value) and is combined to a future value containing all promises with support to generate a delta of all resolved promises. This we need because you issue a search that takes longer and you want to display results as soon as they are resolved not after all haven been resolved. > > Which Promise/Future framework/library are you using in Pharo ? > We rolled our own. And I donât know about other frameworks. > You did not go for single threaded worker images ? For the micro services yes. They read from the queue one by one and process it. Here I scale out with multiple pharo instances. On the API image we have zinc for HTTP that is a multithreaded server and the clients are polling. Norbert > >> And a lot more. This is a coarse grained overview over the architecture. Iâm happy to answer further questions about this. >> >> Norbert >> >>>> On 25 Sep 2018, at 12:20, Norbert Hartl <norbert(a)hartl.name> wrote: >>>> >>>> As presented on ESUG here is the brief description of one of our current projects. >>>> >>>> Mobility Map >>>> ââââââ >>>> >>>> Mobility Map is a broker for mobility services. It offers multi-modal routing search enabling users to find the best travel options between locations. Travel options include car sharing, bikes, trains, busses etc. Rented cars can be offered for ride sharing on booking time letting other people find it to participate in the ride. Single travel options are combined in travel plans that can be booked and managed in a very easy way. >>>> >>>> For this project main requirements were scalability to serve a large user base and flexibility to add more additional providers to the broker. The application has been realized using web technologies for the frontend and pharo for the backend. Using a microservice architecture combined with a broker it is easy to extend the platform with additional brokers. Deployment is done using docker swarm for distributing dozens of pharo images among multiple server machines connected by a message queue for the communication. Pharo supported that scenario very well enabling us the meet the requirements with less effort. >>>> >>>> Pharo turned out to be a perfect fit to develop the application in a agile way. Small development cycles with continuous integration and continuous delivery enables fast turnarounds for the customers to validate progress. >>>> >>>> This is a screenshot of the search page for multi-modal results: >>>> >>>> >>>> <Screen Shot 2018-09-21 at 16.54.30.png> >>> >>> >> >> > >

Sept. 26, 2018

Re: [Pharo-users] Pharo launcher

by Trussardi Dario Romano

Ciao Christophe, > Hi Dario, > > The problem is probably fixed in the latest PharoLauncher version (1.4) available from http://pharo.org/download. Yes, i download the last Pharo launcher ( 1.4 ) and everything works, > If not, as specified in the dialog text, please run the given command from the command line to give us more information on what is the problem. > Thanks, Dario > Regards, > Christophe > >> Le 26 sept. 2018 Ã 12:05, Trussardi Dario Romano <dario.trussardi(a)tiscali.it> a Ã©crit : >> >> Ciao, >> >> on Ubuntu system with Pharo Launcher 1.3 >> >> after create a new Pharo 7.0-64 bit ( development version ) >> >> when i launch the images the system answer : >> >> Cannot determine image version: image version file not found! >> Try to run this command in a shell to get more information on the problem: >> cd "/opt/pharolauncher/pharo-vm/lib/pharo/5.0-201805090836" && export SQUEAK_PLUGINS="" && "/opt/pharolauncher/pharo-vm/lib/pharo/5.0-201805090836/pharo" --nodisplay "/home/party/Pharo/images/Pharo 7.0 - 64bit (180926)-01/Pharo 7.0 - 64bit (180926)-01.image" eval "(Smalltalk imagePath asFileReference parent) / 'pharo.version' writeStreamDo: [ :stream | |major minor| major := SystemVersion current major. minor := SystemVersion current minor. (major = 6 and: [ SystemVersion current highestUpdate >= 60509 ]) ifTrue: [ minor := 1 ]. stream << major asString; << minor asString ]"pha >> >> Thanks for considerations, >> >> Dario >> >> P.S. In the same environment one hold Pharo 7.0-64 bit ( development version ) image ran well with launch command >

Sept. 26, 2018

GTDocument how to

by Hilaire

Hi, I would like a document where user types in normal text and plugs in DrGeo view. The drgeo view will be dual. It will be alternatively the output of a DrGeo script (drgeo canvas) or the DrGeo script itself (code). The view will be interactive. In drgeo canvas mode, user plays with the geometric construction, when switched to code mode, the user edits the DrGeo script and recompute the DrGeo canvas output. Is GTDocument appropriate to do this? If so, where to start? Thanks Hilaire -- Dr. Geo http://drgeo.eu

Sept. 26, 2018

Re: [Pharo-users] Pharo launcher

by Christophe Demarey

Hi Dario, The problem is probably fixed in the latest PharoLauncher version (1.4) available from http://pharo.org/download. If not, as specified in the dialog text, please run the given command from the command line to give us more information on what is the problem. Regards, Christophe > Le 26 sept. 2018 Ã 12:05, Trussardi Dario Romano <dario.trussardi(a)tiscali.it> a Ã©crit : > > Ciao, > > on Ubuntu system with Pharo Launcher 1.3 > > after create a new Pharo 7.0-64 bit ( development version ) > > when i launch the images the system answer : > > Cannot determine image version: image version file not found! > Try to run this command in a shell to get more information on the problem: > cd "/opt/pharolauncher/pharo-vm/lib/pharo/5.0-201805090836" && export SQUEAK_PLUGINS="" && "/opt/pharolauncher/pharo-vm/lib/pharo/5.0-201805090836/pharo" --nodisplay "/home/party/Pharo/images/Pharo 7.0 - 64bit (180926)-01/Pharo 7.0 - 64bit (180926)-01.image" eval "(Smalltalk imagePath asFileReference parent) / 'pharo.version' writeStreamDo: [ :stream | |major minor| major := SystemVersion current major. minor := SystemVersion current minor. (major = 6 and: [ SystemVersion current highestUpdate >= 60509 ]) ifTrue: [ minor := 1 ]. stream << major asString; << minor asString ]"pha > > Thanks for considerations, > > Dario > > P.S. In the same environment one hold Pharo 7.0-64 bit ( development version ) image ran well with launch command

Sept. 26, 2018