September 2018 - Pharo-users

Re: [Pharo-users] GTDocument how to

by Juraj Kubelka

Hi Hilaire, You can create extension similar to one you have here: DrGeoCanvas>>#gtInspectorCanvasIn: DrGeoCanvas>>#gtCanvasIn: aView <gtView> ^ self view ifNil: [ aView empty ] ifNotNil: [ :aMorph | aMorph gtMorphFor: aView ] Then you can obtain Documenter views like this: Juraj > On Sep 30, 2018, at 06:07, Hilaire <hilaire(a)drgeo.eu> wrote: > > For DSL geometric sketch, I use the DrGeoCanvas class. When instantiated > with the #minimal message, it holds a view with only the sketch and no > widget. Therefore It is an interactive geometric sketch in a Morph, it > can be obtained with the #view message. > > Inspected methods with the <gtView> pragma indicate a BLelement is > expected as a view. > > Therefore, how can I embed DrGeoCanvas interactive moprh in Documenter? > > For example, how to deal with an example as bellow? > > | canvas | > > canvas := DrGeoCanvas minimal. > > canvas line: 0@0 to: 5@5. > > minimal view "get the view if necessary" > > Hilaire > > > Le 29/09/2018 Ã 15:49, Juraj Kubelka via Pharo-users a Ã©crit : >> >> 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. >> >>> > > -- > Dr. Geo > http://drgeo.eu > > >

Sept. 30, 2018

Quora: If you could create your own programming language, what would some of the features be?

by Richard Kenneth Eng

Here's the answer I wrote: http://qr.ae/TUGKcH It would be just like Smalltalk <https://www.quora.com/Which-programming-language-is-very-interesting-but-pe…> but with optional static typing. Separate namespaces, too. It would have built-in support for multi-core concurrency. I would call it *Maxwell* (after James Clerk Maxwell). Since Smalltalk already has lambdas, Maxwell could do functional programming, too. Since Smalltalk is fully reflective, Maxwell could do metaprogramming, too, just like Lisp. Since Smalltalk has built-in support for *live coding*, Maxwell could also eliminate the traditional edit-compile-test-debug cycle that hampers most developers. *Productivity could easily double!* Maxwell would also have the option to compile to native code, C, Java, and JavaScript, so it can: 1. execute very quickly on bare metal 2. interoperate with C 3. utilize the JVM ecosystem 4. run in the web browser Maxwell would retain Smalltalkâs simplicity (for the most part) making it great for educational purposes. Finally, Maxwell would be a tightly controlled standard, thereby avoiding fragmentation. *There can be only one Maxwell.* And I would be the BDFL.

Sept. 30, 2018

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

by Pierce Ng

On Wed, Sep 26, 2018 at 07:49:10PM +0200, Norbert Hartl wrote: >>> And a lot more. This is a coarse grained overview over the >>> architecture. Iâm happy to answer further questions about this. >>> [very nice writeup] Hi Norbert, Very nice write-up, thanks. What persistence mechanism are you using - Gemstone/S, Glorp, Voyage, ...? Pierce

Sept. 30, 2018

Re: [Pharo-users] Pharo on macOS Mojave

by Esteban Lorenzano

Yes, so far no problem. But they are deprecating 32bit (they will not be read next version) so I advice using P7 and the 64bit VM. Esteban > On 29 Sep 2018, at 19:35, brackendev <bracken.spencer(a)gmail.com> wrote: > > 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. 30, 2018

Re: [Pharo-users] GTDocument how to

by Hilaire

For DSL geometric sketch, I use the DrGeoCanvas class. When instantiated with the #minimal message, it holds a view with only the sketch and no widget. Therefore It is an interactive geometric sketch in a Morph, it can be obtained with the #view message. Inspected methods with the <gtView> pragma indicate a BLelement is expected as a view. Therefore, how can I embed DrGeoCanvas interactive moprh in Documenter? For example, how to deal with an example as bellow? | canvas | canvas := DrGeoCanvas minimal. canvas line: 0@0 to: 5@5. minimal view "get the view if necessary" Hilaire Le 29/09/2018 Ã 15:49, Juraj Kubelka via Pharo-users a Ã©critÂ : > > 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. > >> -- Dr. Geo http://drgeo.eu

Sept. 30, 2018

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

by Norbert Hartl

I think I need to apologize. I did not see how my mail could be read. I would never accuse you of taking ownership of something you did not do. Because I know you wouldnât do something like that. It just makes me wonder that you donât know me good enough to know that I would not accuse you of that. I was referring to the removal of prior contributions. Anyway the way I wrote it was unfortunate and my apologies again. I donât need to write much more because I can subscribe myself to everything Peter said. We should not asking for contributions if we donât treat them as something valuable. Of course nobody has time to do stuff. But in this case we have a tool that costs only a couple of minutes and saves a lot stuff of value. So I didnât mean you have to do it but someone. And I just wanted to be to consider using the git migration tool in th future. There was no need to kill your repo because the history can be added and your changes can be rebased on that. That is what git gives us. And finally Iâm asking everone to take care. I need to take care more about what I write. But people that get easily offended should see that is the other part of the problem. Norbert > Am 29.09.2018 um 01:13 schrieb Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com>: > >> 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. 30, 2018

Re: [Pharo-users] GTDocument how to

by Juraj Kubelka

Ok. As far as I know, Iceberg does not update local repositories in this use case. Which is fine for developers, less convenient for users. Juraj -- Juraj Kubelka El 29-09-2018, a la(s) 16:42, Hilaire <hilaire(a)drgeo.eu> escribiÃ³: > Likely. As GIT is integrated to Pharo, when installing the package I was > expecting the local repo to be synchronized from remote master. I will > delete local repos and try it again, it will take time. > > Hilaire > > >> Le 29/09/2018 Ã 20:43, Juraj Kubelka via Pharo-users a Ã©crit : >> I do not know how it is possible, but your header mentions Pharo 6.1, but according to the UI you have Pharo 7. And the missing class is part of Pharo 6 only and is not required in Pharo 7. >> >> One reason might be that you keep locally old (2 months) GToolkit code. Can you check this? > > -- > Dr. Geo > http://drgeo.eu > > >

Sept. 29, 2018

Re: [Pharo-users] GTDocument how to

by Hilaire

Likely. As GIT is integrated to Pharo, when installing the package I was expecting the local repo to be synchronized from remote master. I will delete local repos and try it again, it will take time. Hilaire Le 29/09/2018 Ã 20:43, Juraj Kubelka via Pharo-users a Ã©critÂ : > I do not know how it is possible, but your header mentions Pharo 6.1, but according to the UI you have Pharo 7. And the missing class is part of Pharo 6 only and is not required in Pharo 7. > > One reason might be that you keep locally old (2 months) GToolkit code. Can you check this? -- Dr. Geo http://drgeo.eu

Sept. 29, 2018

Re: [Pharo-users] GTDocument how to

by Juraj Kubelka

To be more concrete: you might have locally an old Bloc repository. Juraj -- Juraj Kubelka El 29-09-2018, a la(s) 15:43, Juraj Kubelka via Pharo-users <pharo-users(a)lists.pharo.org> escribiÃ³: > <mime-attachment>

Sept. 29, 2018

Re: [Pharo-users] GTDocument how to

by Juraj Kubelka

I do not know how it is possible, but your header mentions Pharo 6.1, but according to the UI you have Pharo 7. And the missing class is part of Pharo 6 only and is not required in Pharo 7. One reason might be that you keep locally old (2 months) GToolkit code. Can you check this? Juraj -- Juraj Kubelka El 29-09-2018, a la(s) 14:37, Hilaire <hilaire(a)drgeo.eu> escribiÃ³: > 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 > > <Capture du 2018-09-29 19-34-16.png>

Sept. 29, 2018

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

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