- Pharo-users - lists.pharo.org

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

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

by Cyril Ferlicot D.

Le 29/09/2018 Ã 01:05, Guillermo Polito a Ã©critÂ : > I'm sorry if I offended somebody. I've deleted the repository (it was > under pharo-repository, not under my name). With it the changes I made > to make it work on Pharo7. > > I understand that Peter's tool is easy, i've used it before. > But I have my constraints, as others has theirs. > Just note that lot of people complained but nobody took the work to > migrate it with Peter's tool. > Why? If that's so easy :) > > So I decided I was going to spend only ~1hour. It wasÂ > Â - Find the right code on sthub (Rmod repository or another one?) > Â - loading the code + doing a commit (couple of minutes) > Â - adapting the code for pharo 7 > Â - writing a baseline and testing it worked (in a new image, loading > dependencies) > Â - writing a readme, putting a link to the website > > All of them are little tasks of a couple of minutes. Count interruptions > in the middle. > And now I'm sending this email out of frustration. > Hi Guille, If I can be added to pharo-contribution team I can do the migration with history in the next days (weeks max). And thank you for all the work you are doing on a lot of projects! > > -- > > Â Â Â > > > > 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 > -- Cyril Ferlicot https://ferlicot.fr

Sept. 28, 2018

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

by Guillermo Polito

On Sat, Sep 29, 2018 at 1:05 AM Guillermo Polito <guillermopolito(a)gmail.com> wrote: > I'm sorry if I offended somebody. I've deleted the repository (it was > under pharo-repository, not under my name). With it the changes I made to > make it work on Pharo7. > > I understand that Peter's tool is easy, i've used it before. > But I have my constraints, as others has theirs. > Just note that lot of people complained but nobody took the work to > migrate it with Peter's tool. > Why? If that's so easy :) > > So I decided I was going to spend only ~1hour. It was > - Find the right code on sthub (Rmod repository or another one?) > - loading the code + doing a commit (couple of minutes) > - adapting the code for pharo 7 > - writing a baseline and testing it worked (in a new image, loading > dependencies) > - writing a readme, putting a link to the website > Also take into account that while tests run green on Pharo7, Milton's example was not working. And that I had to test manually. So count into my "hour" also: - loading Milton's code - (realize that I have to manually !!!!) load Roassal (otherwise his code does not load) - And test his code Of course I'm not paid for this, I did it for Milton, because apparently nobody was taking "ONE HOUR" to answer his email. And also there are a couple of Artefact examples (Jpeg related) that do not work since years and they add a bit of noise while you test because you don't know if there are more things broken or not. > > All of them are little tasks of a couple of minutes. Count interruptions > in the middle. > And now I'm sending this email out of frustration. > > On Fri, Sep 28, 2018 at 9:19 PM Norbert Hartl <norbert(a)hartl.name> wrote: > >> >> >> 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 >> >> > > -- > > > > 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 > -- 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

I'm sorry if I offended somebody. I've deleted the repository (it was under pharo-repository, not under my name). With it the changes I made to make it work on Pharo7. I understand that Peter's tool is easy, i've used it before. But I have my constraints, as others has theirs. Just note that lot of people complained but nobody took the work to migrate it with Peter's tool. Why? If that's so easy :) So I decided I was going to spend only ~1hour. It was - Find the right code on sthub (Rmod repository or another one?) - loading the code + doing a commit (couple of minutes) - adapting the code for pharo 7 - writing a baseline and testing it worked (in a new image, loading dependencies) - writing a readme, putting a link to the website All of them are little tasks of a couple of minutes. Count interruptions in the middle. And now I'm sending this email out of frustration. On Fri, Sep 28, 2018 at 9:19 PM Norbert Hartl <norbert(a)hartl.name> wrote: > > > 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 > > -- 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] GTDocument how to

by Tim Mackinnon

Ah yes - the newer Tonel format should help - I havenât consciously noticed when having slow loading if all of the dependencies were Tonel2. I still wonder if we may have a code loading perf issue overall - not sure if itâs ever been measured (might be a great summer project for someone). Hopefully a move to Tonel and git might give opportunities to optimise it. Certainly when I look at the quantity of JavaScript that gets pulled in - we seem quite slow. Tim Sent from my iPhone > On 29 Sep 2018, at 06:51, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > 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 Hilaire

Hi, I don't remember to be annoyed by the loading time of GToolkit. Regarding DrGeo it is installed from Tonel file format repository (which is local too), and it is usually very fast. Oh! But P6.1 may not be up to the task with Tonel? I don't remember clearly all the reason why I skipped P6 (the canvas bug but may be something else) Hilaire Le 28/09/2018 Ã 19:53, Tim Mackinnon a Ã©critÂ : > 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 -- Dr. Geo http://drgeo.eu

Sept. 28, 2018

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