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