September 2018 - Pharo-users

Re: [Pharo-users] GTDocument how to

by Hilaire

Indeed new VM passed that error. I have another issue related to unmetÂ dependencies. See screenshot. Not sure it belongs to GToolkit or P7. Hilaire Le 29/09/2018 Ã 19:16, Alistair Grant a Ã©critÂ : > This looks like you have an old VM. If you get the current stable VM > it should be fine. > > The current Pharo 6 & 7 VMs are both dated 28 June 2018. -- Dr. Geo http://drgeo.eu

Sept. 29, 2018

Re: [Pharo-users] Pharo on macOS Mojave

by brackendev

Pharo 6.1 works fine on Mojave for me. Manuel Leuenberger 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 -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Sept. 29, 2018

Re: [Pharo-users] GTDocument how to

by Alistair Grant

Hi Hilaire, This looks like you have an old VM. If you get the current stable VM it should be fine. The current Pharo 6 & 7 VMs are both dated 28 June 2018. Cheers, Alistair On Sat, 29 Sep 2018 at 19:11, Hilaire <hilaire(a)drgeo.eu> wrote: > > Nice! > > I got issue when installing GToolkit on P7. May be the VM is not up to > the task (I took the one shipped with P6.1) but there are error message > with stdio... See screenshot. > > Will try with a newer VM. > > Hilaire > > > Le 29/09/2018 Ã 17:12, Juraj Kubelka via Pharo-users a Ã©crit : > > I was able to install both, DrGeo and GToolkit in Pharo 7.0 image: > > -- > Dr. Geo > http://drgeo.eu >

Sept. 29, 2018

Re: [Pharo-users] GTDocument how to

by Hilaire

Nice! I got issue when installing GToolkit on P7. May be the VM is not up to the task (I took the one shipped with P6.1) but there are error message with stdio... See screenshot. Will try with a newer VM. Hilaire Le 29/09/2018 Ã 17:12, Juraj Kubelka via Pharo-users a Ã©critÂ : > I was able to install both, DrGeo and GToolkit in Pharo 7.0 image: -- Dr. Geo http://drgeo.eu

Sept. 29, 2018

Image does not start anymore

by Bernhard Pieber

Hi, I have a Pharo 7 image which I normally start from Pharo Launcher on Windows. I think I saved it without problems. However, suddenly it stopped opening. As it contains data and some unsaved code I would hate to loose, I'd appreciate any help on how to debug a situation like this. I attached the debug log. Cheers, Bernhard

Sept. 29, 2018

Re: [Pharo-users] GTDocument how to

by Juraj Kubelka

Hi Hilaire, I was able to install both, DrGeo and GToolkit in Pharo 7.0 image: It takes time, but it is possible :-) I hope it helps. Juraj > On Sep 29, 2018, at 10:49, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > > Hi Hilaire, > >> On Sep 27, 2018, at 14:58, Hilaire <hilaire(a)drgeo.eu <mailto:hilaire@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> >>>> <mailto:hilaire@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. > > Definitely. You question is valid. I was not sure how to help. > >> >> So you write this text in playground and inspect? > > Well, there are basically two ways to start using Documenter. In both cases it happens in the GT Inspector. > > First, you can inspect a class and write a Documenter document as a class comment (Comment inspector tab). > Second, you can create a a-file.pillar local file and inspect it (âa-file.pillarâ asFileReference). > > Let me know if it helps. > >> >>> >>> 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 <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/> <http://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… <https://bazaar.launchpad.net/~drgeo-developers/drgeo/trunk/view/head:/src/I…> > > I have checked GToolkit dependencies and there is no XML project involved: > > <Screen Shot 2018-09-29 at 10.43.15.png> > > >> >>> >>>> >>>> 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. > > > We updated GToolkit this week to work in Pharo 7. At least you should be able to load it and open Documenter (or GToolkit tour from World menu). Can you give a try? > > Juraj > > >> >> Hilaire >> >> -- >> Dr. Geo >> http://drgeo.eu <http://drgeo.eu/> >> >> <Capture du 2018-09-27 19-48-36.png>

Sept. 29, 2018

Re: [Pharo-users] Iceberg - better control of project name?

by Ben Coman

Having also worked with the Exercism-Pharo project I've had the same thoughts. Its a bit like from the command line specifying which directory is created. git clone <repository> [<directory>] cheers -ben On Sat, 29 Sep 2018 at 12:34, Tim Mackinnon <tim(a)testit.works> wrote: > Hi - Iâve just noticed a small issue with the latest iceberg - or at least > its confusing. The Exercism project - is in a repo specified by them - its > exercism/pharo.git > > And when I check it out using the latest iceberg using the GitHub option - > I specify an Owner of âexercismâ and a project name âpharoâ to get it to > properly check out. However in the iceberg window this then appears as a > project called âpharoâ which is very misleading when there is the master > âPharoâ project for all of pharo. (See photo) > > There doesnât seem to be a way to override the display of this name to > make it âexercism/pharoâ - and Iâm wondering if Iceberg should handle this > a bit better - either by showing {owner}/{project} or letting you give a > better name in the definition to override what is shown? > > Tim > >

Sept. 29, 2018

Re: [Pharo-users] GTDocument how to

by Juraj Kubelka

Hi Hilaire, > On Sep 27, 2018, at 14: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. Definitely. You question is valid. I was not sure how to help. > > So you write this text in playground and inspect? Well, there are basically two ways to start using Documenter. In both cases it happens in the GT Inspector. First, you can inspect a class and write a Documenter document as a class comment (Comment inspector tab). Second, you can create a a-file.pillar local file and inspect it (âa-file.pillarâ asFileReference). Let me know if it helps. > >> >> 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… <https://bazaar.launchpad.net/~drgeo-developers/drgeo/trunk/view/head:/src/I…> I have checked GToolkit dependencies and there is no XML project involved: > >> >>> >>> 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. We updated GToolkit this week to work in Pharo 7. At least you should be able to load it and open Documenter (or GToolkit tour from World menu). Can you give a try? Juraj > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > > <Capture du 2018-09-27 19-48-36.png>

Sept. 29, 2018

Re: [Pharo-users] Pharo 7.0 code documentation

by Juraj Kubelka

Hi Dario, If you want to have an experience doing live documentation, you can start with GToolkit Documenter: https://github.com/feenkcom/gtoolkit It is an alpha version. I will be happy to help you and to know about your experience. Juraj -- Juraj Kubelka El 27-09-2018, a la(s) 14:01, Trussardi Dario Romano <dario.trussardi(a)tiscali.it> escribiÃ³: > 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. 29, 2018

Iceberg - better control of project name?

by Tim Mackinnon

Hi - Iâve just noticed a small issue with the latest iceberg - or at least its confusing. The Exercism project - is in a repo specified by them - its exercism/pharo.git And when I check it out using the latest iceberg using the GitHub option - I specify an Owner of âexercismâ and a project name âpharoâ to get it to properly check out. However in the iceberg window this then appears as a project called âpharoâ which is very misleading when there is the master âPharoâ project for all of pharo. (See photo) There doesnât seem to be a way to override the display of this name to make it âexercism/pharoâ - and Iâm wondering if Iceberg should handle this a bit better - either by showing {owner}/{project} or letting you give a better name in the definition to override what is shown? Tim

Sept. 29, 2018