December 2017 - Pharo-users

Re: [Pharo-users] Behold Pharo: The Modern Smalltalk

by Prof. Andrew P. Black

> On 9 Dec 2017, at 07:44 , Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > Making shortcuts in Pharo is no big deal, if 10% of people asking for Emacs or vim shortcuts bothered creating just 10 shortcuts each we would have by now at least 100 Emacs shortcuts in Pharo. When one say that needs something that He or she is not willing to do even 1% of its work, then he does not need it enough for others to bother. In September, I posted an Issue on pharo.fogbuz <https://pharo.fogbugz.com/f/cases/20466/Keyboard-Shortcuts>: making keyboard shortcuts for the Pharo Smalltalk editor is not easy, but should be. No one has responded to that issue saying that it really is easy, and explaining how to do it. So if you know, I invite you to work on this issue. tl;dr: I though that it was easy too, but after spending a couple of days trying to figure it out, gave up. If 10% of the energy expended in this thread had gone into fixing open issues, then Pharo would be getting better every day.

Dec. 9, 2017

[ann] gtmondrian

by Tudor Girba

Hi, We are happy to announce GT Mondrian, a graph visualization engine built on top of Bloc. It is similar to the original Mondrian and the Mondrian from Roassal, but it is different in that it is built directly out of Bloc elements. This is interesting because it allows us to combine typical widgets with visualizations. The other interesting thing about it is that it validates the design of Bloc: right now, the implementation has 509 lines of code (excluding graph-specific layouts). The goal is to make visualization a first class citizen and an integral part of the IDE. The key ingredient that made this happen is that Bloc can now treat graph layouts, such as tree or force based, behave under the same rules as typical widget layouts, such as grid or flow. The challenge comes from the fact that a graph layout depends on the notion of edges between elements, and we did not want to have elements know about edges in the core of Bloc. The solution was to split the typical edge implementation in graph visualization libraries into two distinct concepts: â¢ Line is an element that draws the connections. â¢ Edge defines constraints imposed by connections between elements. Thus, edges form constraints, and constraints are what layouts deal with. That is one reason why elements in bloc have the ability of defining layout-specific constraints. Using this, we can nicely define edges between elements as a plugin to Bloc, but still be able to connect arbitrary elements. What's more, it turns out that we need constraints for other layouts as well. For example, an element in a grid layout might specify the span. The API of GT Mondrian is similar to the one from Roassal, but there are a few differences as well. These are described in the Pillar documentation available in the GitHub repo. The best way to experience GT Mondrian and its documentation is to load the GToolkit as described here: https://github.com/feenkcom/gtoolkit If you download the GT code through Iceberg, the documentation can be experienced live by inspecting: './pharo-local/iceberg/feenkcom/gtoolkit-visualizer/doc/mondrian/index.pillar' asFileReference Cheers, The feenk team -- www.tudorgirba.com www.feenk.com "Quality cannot be an afterthought."

Dec. 9, 2017

Re: [Pharo-users] HTTP request question for an arango driver

by Stephane Ducasse

Super Yann! Keep pushing. Let us know. This is important to announce like that other people can join forces. On Fri, Dec 8, 2017 at 11:52 PM, Yann Lesage <yannlesag(a)gmail.com> wrote: > Le 08/12/2017 Ã 17:13, Norbert Hartl a Ã©crit : > >> Hi, >> >>> Am 08.12.2017 um 15:32 schrieb Yann Lesage <yannlesag(a)gmail.com>: >>> >>> Hello, >>> >>> >>> I write an driver for Arangodb . So like it's indicated in Arango >>> documentation, I use the HTTP API. The repo is >>> https://github.com/Valtena/Pharango >>> >> that is really wonderful. Iâm planning to do that for a long time but >> didnât find the time yet. Maybe I can find some time to help a little if you >> are interested. > > I have see that on the Pharo Discord. I don't had finish a first version, > write the road map and contributor.md, so it maybe a little early for that. > But I not against a code review in futur or another help. > >>> Now, the problem : Arango using Znclient make around 1 000 >>> requests/second. >>> >>> >>> And the question : Are there any recommended pratice to have the better >>> performance with ZNClient or a better way to perform lot of HTTP requests ? >>> >> I think the biggest benefit comes from caching the ZnClient. It is >> designed to be used like that. Next could be using keep-alive in order to >> reduce the number of connections to be made. Finalky I could imagine that >> pooling the most heavy objects in zinc can remove stress from the garbage >> collector. > > I am agree with this. I cache the ZnClient, without that, I don't have more > than 400 or 500 request/s. And the keep-alive is the default behavior in > Arango et ZnClient. > >> Norbert >>> >>> Thanks for your attention, >>> >>> Yann Lesage > > > Le 08/12/2017 Ã 22:14, Stephane Ducasse a Ã©crit : >> >> Yann >> I do not think that connecting a database via a HTTP client can be as >> fast as with a FFI or other means. >> This is mainly why database like Gemstone are superior for accessing a >> lot of data. >> Stef > > > I know that, but I would try to have the better performances. After, user > can group requests to limit the cost of http protocol. So, it's not a > fatality. I think try to use the arango shell in futur. In first, I will > finish the driver with HTTP client because is more easier to write it and > more flexible in using with distant server. > > Yann Lesage >

Dec. 9, 2017

Re: [Pharo-users] Behold Pharo: The Modern Smalltalk

by Dimitris Chloupis

Nope , nothing to do with Emacs GNU Smalltalk is Smalltalk without.... welll... Smalltalk Which is why almost none is using it. There is a project to use Pharo from inside Emacs called Shamoo. Frankly you will be sacrificing a lot of IDE goodies leaving Pharo. Neither Emacs or vim are proper IDEs , they are text editors pretending to be IDEs and failing miserably at it. On the other hand Pharo IS an IDE playing ball with big boys. Making shortcuts in Pharo is no big deal, if 10% of people asking for Emacs or vim shortcuts bothered creating just 10 shortcuts each we would have by now at least 100 Emacs shortcuts in Pharo. When one say that needs something that He or she is not willing to do even 1% of its work, then he does not need it enough for others to bother. Itâs the difference between hype and actual desire. On Fri, 8 Dec 2017 at 23:35, Kjell Godo <squeaklist(a)gmail.com> wrote: > isn't GNU Smalltalk a emacs Smalltalk? > maybe making a migration path from GNU to Pharo could be good? > > On Fri, Dec 8, 2017 at 1:33 PM, Kjell Godo <squeaklist(a)gmail.com> wrote: > >> if Pharo could have a emacs version or face or something >> that would advertise more functions that you can get >> from the Pharo version >> or maybe link the two versions Pharo and emacsVimPharo >> so there is like a migration path to Pharo >> or they could work together >> that could be lower the barrier to entry >> i saw emacs vim guy who could also hate to learning something new >> >> On Fri, Dec 8, 2017 at 1:08 PM, Stephane Ducasse <stepharo.self(a)gmail.com >> > wrote: >> >>> Hi Richard >>> >>> Thanks this is nice. I like Greeter :) >>> The suggestion of Ben are fun for the next one. >>> I will add a link to your article. >>> >>> Stef >>> >>> On Thu, Dec 7, 2017 at 11:35 PM, horrido <horrido.hobbies(a)gmail.com> >>> wrote: >>> > Done. Class #Hello is now #Greeter in package "HelloDemo". >>> > >>> > I presume we're good to go, then? >>> > >>> > >>> > >>> > Offray Vladimir Luna CÃ¡rdenas-2 wrote >>> >> May be the class name could be changed a little bit to allow more >>> >> flexibility using the Pharo Quick Start as a base. Something like >>> >> "Greeter" and "Greeter new say: 'Hello world!'" or "Greeter new sayIt" >>> >> could be implemented from there. Nice to see more and more >>> documentation >>> >> around Pharo, including this one. >>> >> >>> >> That being said, I have always felt that hello world is kind of a >>> >> strange introduction to programming: >>> >> >>> >> http://mutabit.com/offray/blog/en/entry/dumb-hello-world >>> >> >>> >> Cheers, >>> >> >>> >> Offray >>> >> >>> >> >>> >> On 07/12/17 15:31, horrido wrote: >>> >>> I've revised the draft slightly for the comments given here: >>> >>> https://medium.com/@richardeng/pharo-quick-start-5bab70944ce2 >>> >>> >>> >>> Yes, it's a definite improvement. Thanks. >>> >>> >>> >>> >>> >>> >>> >>> Richard Sargent wrote >>> >>>> Excellent work, Richard! >>> >>>> >>> >>>> May I offer the small criticism against using #initialize for the >>> method >>> >>>> name? I think a name like #sayIt (for example) and invocation like >>> >>>> "Hello >>> >>>> new sayIt" would make it explicit. >>> >>>> >>> >>>> This will be a great help for people who drop by out of curiosity. >>> >>>> >>> >>>> >>> >>>> On Thu, Dec 7, 2017 at 11:38 AM, horrido < >>> >>>> horrido.hobbies@ >>> >>>> > wrote: >>> >>>> >>> >>>>> I've completed the first draft of my Pharo Quick Start guide >>> >>>>> < >>> https://medium.com/@richardeng/pharo-quick-start-5bab70944ce2> >>> >>>>> . >>> >>>>> I >>> >>>>> decided >>> >>>>> to forge ahead anyway. >>> >>>>> >>> >>>>> Feedback welcome. >>> >>>>> >>> >>>>> Note that I chose wget instead of curl because many Linux distros >>> do >>> >>>>> not >>> >>>>> have curl installed. >>> >>>>> >>> >>>>> I've tested the guide for various Linux distros including Mint 18.3 >>> >>>>> (Ubuntu-based), Debian 9.2.1, Manjaro 17.0.6 (Arch-based), Solus >>> 3, and >>> >>>>> Fedora 27. So it should be good for all the popular distros (Top >>> 10). >>> >>>>> >>> >>>>> >>> >>>>> >>> >>>>> -- >>> >>>>> Sent from: >>> http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>> >>>>> >>> >>>>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>> >>> >>> >>> >>> > >>> > >>> > >>> > >>> > >>> > -- >>> > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>> > >>> >>> >> >

Dec. 9, 2017

Re: [Pharo-users] Behold Pharo: The Modern Smalltalk

by horrido

Pharo: The Next Ten Minutes <https://medium.com/@richardeng/pharo-the-next-ten-minutes-a17899dc9a58> . Feedback welcome. I will be leaving for vacation on Sunday for two weeks. Feedback should be given to me asap. Thanks. Stephane Ducasse-3 wrote > Hi Richard > > Thanks this is nice. I like Greeter :) > The suggestion of Ben are fun for the next one. > I will add a link to your article. > > Stef > > On Thu, Dec 7, 2017 at 11:35 PM, horrido < > horrido.hobbies@ > > wrote: >> Done. Class #Hello is now #Greeter in package "HelloDemo". >> >> I presume we're good to go, then? >> >> >> >> Offray Vladimir Luna CÃ¡rdenas-2 wrote >>> May be the class name could be changed a little bit to allow more >>> flexibility using the Pharo Quick Start as a base. Something like >>> "Greeter" and "Greeter new say: 'Hello world!'" or "Greeter new sayIt" >>> could be implemented from there. Nice to see more and more documentation >>> around Pharo, including this one. >>> >>> That being said, I have always felt that hello world is kind of a >>> strange introduction to programming: >>> >>> http://mutabit.com/offray/blog/en/entry/dumb-hello-world >>> >>> Cheers, >>> >>> Offray >>> >>> >>> On 07/12/17 15:31, horrido wrote: >>>> I've revised the draft slightly for the comments given here: >>>> https://medium.com/@richardeng/pharo-quick-start-5bab70944ce2 >>>> >>>> Yes, it's a definite improvement. Thanks. >>>> >>>> >>>> >>>> Richard Sargent wrote >>>>> Excellent work, Richard! >>>>> >>>>> May I offer the small criticism against using #initialize for the >>>>> method >>>>> name? I think a name like #sayIt (for example) and invocation like >>>>> "Hello >>>>> new sayIt" would make it explicit. >>>>> >>>>> This will be a great help for people who drop by out of curiosity. >>>>> >>>>> >>>>> On Thu, Dec 7, 2017 at 11:38 AM, horrido < >>>>> horrido.hobbies@ >>>>> > wrote: >>>>> >>>>>> I've completed the first draft of my Pharo Quick Start guide >>>>>> <https://medium.com/@richardeng/pharo-quick-start-5bab70944ce2> >>>>>> . >>>>>> I >>>>>> decided >>>>>> to forge ahead anyway. >>>>>> >>>>>> Feedback welcome. >>>>>> >>>>>> Note that I chose wget instead of curl because many Linux distros do >>>>>> not >>>>>> have curl installed. >>>>>> >>>>>> I've tested the guide for various Linux distros including Mint 18.3 >>>>>> (Ubuntu-based), Debian 9.2.1, Manjaro 17.0.6 (Arch-based), Solus 3, >>>>>> and >>>>>> Fedora 27. So it should be good for all the popular distros (Top 10). >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>>>>> >>>>>> >>>> >>>> >>>> >>>> >>>> -- >>>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>>> >>>> >> >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Dec. 9, 2017

Re: [Pharo-users] Behold Pharo: The Modern Smalltalk

by Ben Coman

We often get suggestions for such bindings. While in general it would be a great thing and I often promote lowering barriers of entry, I feel in this context "pure text mode" developers are more likely to find many other barriers with Pharo not fitting their familiar development paradigm. Such bindings are not the low hanging fruit for enticing developer to try Pharo and a better market is targeting those needing a better IDE. The more likely path to emacs/vim is pharo as a shell command which leaves a user's workflow around editing unchanged. cheers -ben On 9 December 2017 at 05:35, Kjell Godo <squeaklist(a)gmail.com> wrote: > isn't GNU Smalltalk a emacs Smalltalk? > maybe making a migration path from GNU to Pharo could be good? > > On Fri, Dec 8, 2017 at 1:33 PM, Kjell Godo <squeaklist(a)gmail.com> wrote: > >> if Pharo could have a emacs version or face or something >> that would advertise more functions that you can get >> from the Pharo version >> or maybe link the two versions Pharo and emacsVimPharo >> so there is like a migration path to Pharo >> or they could work together >> that could be lower the barrier to entry >> i saw emacs vim guy who could also hate to learning something new >> >> On Fri, Dec 8, 2017 at 1:08 PM, Stephane Ducasse <stepharo.self(a)gmail.com >> > wrote: >> >>> Hi Richard >>> >>> Thanks this is nice. I like Greeter :) >>> The suggestion of Ben are fun for the next one. >>> I will add a link to your article. >>> >>> Stef >>> >>> On Thu, Dec 7, 2017 at 11:35 PM, horrido <horrido.hobbies(a)gmail.com> >>> wrote: >>> > Done. Class #Hello is now #Greeter in package "HelloDemo". >>> > >>> > I presume we're good to go, then? >>> > >>> > >>> > >>> > Offray Vladimir Luna CÃ¡rdenas-2 wrote >>> >> May be the class name could be changed a little bit to allow more >>> >> flexibility using the Pharo Quick Start as a base. Something like >>> >> "Greeter" and "Greeter new say: 'Hello world!'" or "Greeter new sayIt" >>> >> could be implemented from there. Nice to see more and more >>> documentation >>> >> around Pharo, including this one. >>> >> >>> >> That being said, I have always felt that hello world is kind of a >>> >> strange introduction to programming: >>> >> >>> >> http://mutabit.com/offray/blog/en/entry/dumb-hello-world >>> >> >>> >> Cheers, >>> >> >>> >> Offray >>> >> >>> >> >>> >> On 07/12/17 15:31, horrido wrote: >>> >>> I've revised the draft slightly for the comments given here: >>> >>> https://medium.com/@richardeng/pharo-quick-start-5bab70944ce2 >>> >>> >>> >>> Yes, it's a definite improvement. Thanks. >>> >>> >>> >>> >>> >>> >>> >>> Richard Sargent wrote >>> >>>> Excellent work, Richard! >>> >>>> >>> >>>> May I offer the small criticism against using #initialize for the >>> method >>> >>>> name? I think a name like #sayIt (for example) and invocation like >>> >>>> "Hello >>> >>>> new sayIt" would make it explicit. >>> >>>> >>> >>>> This will be a great help for people who drop by out of curiosity. >>> >>>> >>> >>>> >>> >>>> On Thu, Dec 7, 2017 at 11:38 AM, horrido < >>> >>>> horrido.hobbies@ >>> >>>> > wrote: >>> >>>> >>> >>>>> I've completed the first draft of my Pharo Quick Start guide >>> >>>>> <https://medium.com/@richardeng/pharo-quick-start-5bab709 >>> 44ce2> >>> >>>>> . >>> >>>>> I >>> >>>>> decided >>> >>>>> to forge ahead anyway. >>> >>>>> >>> >>>>> Feedback welcome. >>> >>>>> >>> >>>>> Note that I chose wget instead of curl because many Linux distros >>> do >>> >>>>> not >>> >>>>> have curl installed. >>> >>>>> >>> >>>>> I've tested the guide for various Linux distros including Mint 18.3 >>> >>>>> (Ubuntu-based), Debian 9.2.1, Manjaro 17.0.6 (Arch-based), Solus >>> 3, and >>> >>>>> Fedora 27. So it should be good for all the popular distros (Top >>> 10). >>> >>>>> >>> >>>>> >>> >>>>> >>> >>>>> -- >>> >>>>> Sent from: http://forum.world.st/Pharo-Sm >>> alltalk-Users-f1310670.html >>> >>>>> >>> >>>>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>> >>> >>> >>> >>> > >>> > >>> > >>> > >>> > >>> > -- >>> > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>> > >>> >>> >> >

Dec. 9, 2017

Simplest 'REPL'

by cheshirecatalyst

I've recently picked up pharo, and am writing a small interpreter for a trivial language the details of which are unimportant. However I am looking for the simplest way to avoid having to use playground and Transcript to do something like | reader eval | reader := MyReader from: 'some stuff in my DSL'. eval := MyEvaluator from: reader. Transcript show: eval evaluate. I'm tired of having to change 'some stuff in my DSL' to a new expression and run it in playground. I don't really care which is easier, a Morphic with an input box at the bottom to put my expressions in with output up top, or a something like CommandShellTranscript (which i have looked at but is too complex for me to figure out how to get the desired result from). Basically I want to be able to use my DSL outside of playground, but still in image.

Dec. 8, 2017

Re: [Pharo-users] HTTP request question for an arango driver

by Yann Lesage

Le 08/12/2017 Ã 17:13, Norbert Hartl a Ã©critÂ : > Hi, > >> Am 08.12.2017 um 15:32 schrieb Yann Lesage <yannlesag(a)gmail.com>: >> >> Hello, >> >> >> I write an driver for Arangodb . So like it's indicated in Arango documentation, I use the HTTP API. The repo is https://github.com/Valtena/Pharango >> > that is really wonderful. Iâm planning to do that for a long time but didnât find the time yet. Maybe I can find some time to help a little if you are interested. I have see that on the Pharo Discord. I don't had finish a first version, write the road map and contributor.md, so it maybe a little early for that. But I not against a code review in futur or another help. >> Now, the problem : Arango using Znclient make around 1 000 requests/second. >> >> >> And the question : Are there any recommended pratice to have the better performance with ZNClient or a better way to perform lot of HTTP requests ? >> > I think the biggest benefit comes from caching the ZnClient. It is designed to be used like that. Next could be using keep-alive in order to reduce the number of connections to be made. Finalky I could imagine that pooling the most heavy objects in zinc can remove stress from the garbage collector. I am agree with this. I cache the ZnClient, without that, I don't have more than 400 or 500 request/s. And the keep-alive is the default behavior in Arango et ZnClient. > Norbert >> Thanks for your attention, >> >> Yann Lesage Le 08/12/2017 Ã 22:14, Stephane Ducasse a Ã©critÂ : > Yann > I do not think that connecting a database via a HTTP client can be as > fast as with a FFI or other means. > This is mainly why database like Gemstone are superior for accessing a > lot of data. > Stef I know that, but I would try to have the better performances. After, user can group requests to limit the cost of http protocol. So, it's not a fatality. I think try to use the arango shell in futur. In first, I will finish the driver with HTTP client because is more easier to write it and more flexible in using with distant server. Yann Lesage

Dec. 8, 2017

Re: [Pharo-users] Behold Pharo: The Modern Smalltalk

by Kjell Godo

isn't GNU Smalltalk a emacs Smalltalk? maybe making a migration path from GNU to Pharo could be good? On Fri, Dec 8, 2017 at 1:33 PM, Kjell Godo <squeaklist(a)gmail.com> wrote: > if Pharo could have a emacs version or face or something > that would advertise more functions that you can get > from the Pharo version > or maybe link the two versions Pharo and emacsVimPharo > so there is like a migration path to Pharo > or they could work together > that could be lower the barrier to entry > i saw emacs vim guy who could also hate to learning something new > > On Fri, Dec 8, 2017 at 1:08 PM, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > >> Hi Richard >> >> Thanks this is nice. I like Greeter :) >> The suggestion of Ben are fun for the next one. >> I will add a link to your article. >> >> Stef >> >> On Thu, Dec 7, 2017 at 11:35 PM, horrido <horrido.hobbies(a)gmail.com> >> wrote: >> > Done. Class #Hello is now #Greeter in package "HelloDemo". >> > >> > I presume we're good to go, then? >> > >> > >> > >> > Offray Vladimir Luna CÃ¡rdenas-2 wrote >> >> May be the class name could be changed a little bit to allow more >> >> flexibility using the Pharo Quick Start as a base. Something like >> >> "Greeter" and "Greeter new say: 'Hello world!'" or "Greeter new sayIt" >> >> could be implemented from there. Nice to see more and more >> documentation >> >> around Pharo, including this one. >> >> >> >> That being said, I have always felt that hello world is kind of a >> >> strange introduction to programming: >> >> >> >> http://mutabit.com/offray/blog/en/entry/dumb-hello-world >> >> >> >> Cheers, >> >> >> >> Offray >> >> >> >> >> >> On 07/12/17 15:31, horrido wrote: >> >>> I've revised the draft slightly for the comments given here: >> >>> https://medium.com/@richardeng/pharo-quick-start-5bab70944ce2 >> >>> >> >>> Yes, it's a definite improvement. Thanks. >> >>> >> >>> >> >>> >> >>> Richard Sargent wrote >> >>>> Excellent work, Richard! >> >>>> >> >>>> May I offer the small criticism against using #initialize for the >> method >> >>>> name? I think a name like #sayIt (for example) and invocation like >> >>>> "Hello >> >>>> new sayIt" would make it explicit. >> >>>> >> >>>> This will be a great help for people who drop by out of curiosity. >> >>>> >> >>>> >> >>>> On Thu, Dec 7, 2017 at 11:38 AM, horrido < >> >>>> horrido.hobbies@ >> >>>> > wrote: >> >>>> >> >>>>> I've completed the first draft of my Pharo Quick Start guide >> >>>>> <https://medium.com/@richardeng/pharo-quick-start-5bab709 >> 44ce2> >> >>>>> . >> >>>>> I >> >>>>> decided >> >>>>> to forge ahead anyway. >> >>>>> >> >>>>> Feedback welcome. >> >>>>> >> >>>>> Note that I chose wget instead of curl because many Linux distros do >> >>>>> not >> >>>>> have curl installed. >> >>>>> >> >>>>> I've tested the guide for various Linux distros including Mint 18.3 >> >>>>> (Ubuntu-based), Debian 9.2.1, Manjaro 17.0.6 (Arch-based), Solus 3, >> and >> >>>>> Fedora 27. So it should be good for all the popular distros (Top >> 10). >> >>>>> >> >>>>> >> >>>>> >> >>>>> -- >> >>>>> Sent from: http://forum.world.st/Pharo-Sm >> alltalk-Users-f1310670.html >> >>>>> >> >>>>> >> >>> >> >>> >> >>> >> >>> >> >>> -- >> >>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >>> >> >>> >> > >> > >> > >> > >> > >> > -- >> > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> > >> >> >

Dec. 8, 2017

Re: [Pharo-users] Behold Pharo: The Modern Smalltalk

by Kjell Godo

if Pharo could have a emacs version or face or something that would advertise more functions that you can get from the Pharo version or maybe link the two versions Pharo and emacsVimPharo so there is like a migration path to Pharo or they could work together that could be lower the barrier to entry i saw emacs vim guy who could also hate to learning something new On Fri, Dec 8, 2017 at 1:08 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi Richard > > Thanks this is nice. I like Greeter :) > The suggestion of Ben are fun for the next one. > I will add a link to your article. > > Stef > > On Thu, Dec 7, 2017 at 11:35 PM, horrido <horrido.hobbies(a)gmail.com> > wrote: > > Done. Class #Hello is now #Greeter in package "HelloDemo". > > > > I presume we're good to go, then? > > > > > > > > Offray Vladimir Luna CÃ¡rdenas-2 wrote > >> May be the class name could be changed a little bit to allow more > >> flexibility using the Pharo Quick Start as a base. Something like > >> "Greeter" and "Greeter new say: 'Hello world!'" or "Greeter new sayIt" > >> could be implemented from there. Nice to see more and more documentation > >> around Pharo, including this one. > >> > >> That being said, I have always felt that hello world is kind of a > >> strange introduction to programming: > >> > >> http://mutabit.com/offray/blog/en/entry/dumb-hello-world > >> > >> Cheers, > >> > >> Offray > >> > >> > >> On 07/12/17 15:31, horrido wrote: > >>> I've revised the draft slightly for the comments given here: > >>> https://medium.com/@richardeng/pharo-quick-start-5bab70944ce2 > >>> > >>> Yes, it's a definite improvement. Thanks. > >>> > >>> > >>> > >>> Richard Sargent wrote > >>>> Excellent work, Richard! > >>>> > >>>> May I offer the small criticism against using #initialize for the > method > >>>> name? I think a name like #sayIt (for example) and invocation like > >>>> "Hello > >>>> new sayIt" would make it explicit. > >>>> > >>>> This will be a great help for people who drop by out of curiosity. > >>>> > >>>> > >>>> On Thu, Dec 7, 2017 at 11:38 AM, horrido < > >>>> horrido.hobbies@ > >>>> > wrote: > >>>> > >>>>> I've completed the first draft of my Pharo Quick Start guide > >>>>> <https://medium.com/@richardeng/pharo-quick-start-5bab70944ce2&gt > ; > >>>>> . > >>>>> I > >>>>> decided > >>>>> to forge ahead anyway. > >>>>> > >>>>> Feedback welcome. > >>>>> > >>>>> Note that I chose wget instead of curl because many Linux distros do > >>>>> not > >>>>> have curl installed. > >>>>> > >>>>> I've tested the guide for various Linux distros including Mint 18.3 > >>>>> (Ubuntu-based), Debian 9.2.1, Manjaro 17.0.6 (Arch-based), Solus 3, > and > >>>>> Fedora 27. So it should be good for all the popular distros (Top 10). > >>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >>>>> > >>>>> > >>> > >>> > >>> > >>> > >>> -- > >>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >>> > >>> > > > > > > > > > > > > -- > > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > > > >

Dec. 8, 2017