- Pharo-users - lists.pharo.org

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