October 2016 - Pharo-users - lists.pharo.org

Re: Pharo 5 accented chars bug/regression

by Milan Vavra

Here's what you can do to be able to type c with caron in Pharo 3.0, 4.0, 5.0 on Windows: You perform a little bit of brain surgery on the event handling. *** Warning! This could void your warranty! *** If you do this wrong, your image might stop responding to keystrokes or mouse or just freeze altogether. Save any important data you may have in the image before you proceed. You modify HandMorph>>#generateKeyboardEvent: as follows. After a line that goes charCode := evtBuf sixth. you put another one that looks like this: charCode > 255 ifTrue: [ keyValue := 0 ]. Save. Done. If you did it right, you can now type c with caron and friends. Specifically c with caron, e with caron, uppercase E with caron. And some uppercase cyrilic characters. What this does is that it trusts that the value in charCode is more reliable than that in keyValue. The national characters with Unicode code points of over 255 get passed in to the image from the vm with bogus value of keyValue so if we see a Unicode character with a code point of over 255 we zero the bogus value so it can do no harm. Best Regards, Milan Vavra -- View this message in context: http://forum.world.st/Pharo-5-accented-chars-bug-regression-tp4898863p49199… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Oct. 24, 2016

Re: [Pharo-users] The Ultimate Smalltalk Tutorial

by Nicolai Hess

Am 23.10.2016 3:16 nachm. schrieb "Vitor Medina Cruz" <vitormcruz(a)gmail.com >: > > I think the MOOC is too much for a tutorial. What I miss today is a good written (no videos! Please!) tutorial that teaches just a little of the language and give a few guidelines on how to do simple stuff with the environment, such as a "Hello World!", creating a class, tests and run stuff. I thought "pharo by example" provides exactly that. What is missing here, from your perspective? I learned a lot from it and it helped me to get started to learn smalltalk, not only the syntax, but also, doing something the smalltalk way. > > On Sat, Oct 15, 2016 at 12:15 PM, horrido <horrido.hobbies(a)gmail.com> wrote: >> >> Excellent suggestion! I shall look into it. Thanks. >> >> >> >> >> -- >> View this message in context: http://forum.world.st/The-Ultimate-Smalltalk-Tutorial-tp4918859p4918930.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >

Oct. 24, 2016

Re: [Pharo-users] The Ultimate Smalltalk Tutorial

by Ben Coman

On Mon, Oct 24, 2016 at 8:11 AM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > I was looking my entire life for something like Pharo , almost 30 years. > When I found it took me another 5 to realize this is it and I had many close > calls to abandoning it. But in the end I realized with its weakness and > frustrated moments I love Pharo. > > To tell you truth even if I was to give up Pharo, today, it would not matter > much. Mainly because I can take the Pharo ideology to any other programming > language even the most ugly ones like Java, C++ and JavaScript. I don't remember who said it, but I like the quote... "The only languages worth learning are those that change the way you think about programming" > On Mon, 24 Oct 2016 at 01:52, Vitor Medina Cruz <vitormcruz(a)gmail.com> > wrote: >> I think what is missing is something before all that, something that spark >> the "I am interested in Pharo", the STEP 0. What does that today? I think a >> simple tutorial that catch the attention of people would do that. Right now >> I think it is too hard for someone to get interested in Smalltalk in >> general, and Pharo in particular, because something like that is missing, >> and one must really understand and see the value of Smalltalk to persist and >> keep going and learning, like happened to me. Perhaps something like these? * https://medium.com/concerning-pharo/reddit-st-in-10-cool-pharo-classes-1b53… * https://medium.com/concerning-pharo/rediscovering-the-ux-of-the-legendary-h… * https://medium.com/concerning-pharo/elegant-pharo-code-bb590f0856d0 If you do notice somewhere a suitable step 0, please let us know. For those of us using Pharo a while, our perspective changes so maybe we can't see what might hook newcomers. The things we see as important might be a paradigm step too far for newcomers. Although those who teach Pharo classes would have a better idea of a newcomer perspective, may that is still different from someone voluntarily choosing Pharo without a supportive environment like a university course. cheers -ben

Oct. 24, 2016

Re: [Pharo-users] The Ultimate Smalltalk Tutorial

by Dimitris Chloupis

It's hard because very few people are curious by nature. It's people that love to get out of their comfort zone. You cannot instill that to people , you either have it or you don't. So the truth is , there is no step 0. Let's be sincere here Smalltalk is by far the most anti mainstream language. Plenty of people pass through these forums , all of the are curious and interested , very few stick around. Took me two years to be convinced to take Pharo seriously another two to let it replace Python. The reply I wrote was a joke. I would never recommend Pharo over Python or Ruby or even JavaScript. The Pharo path is a path of suffering and pain. Sure it's fun but it ain't easy. I was looking my entire life for something like Pharo , almost 30 years. When I found it took me another 5 to realize this is it and I had many close calls to abandoning it. But in the end I realized with its weakness and frustrated moments I love Pharo. To tell you truth even if I was to give up Pharo, today, it would not matter much. Mainly because I can take the Pharo ideology to any other programming language even the most ugly ones like Java, C++ and JavaScript. I recently discovered how to turn C++ into a full live coding language with almost zero compile times. Where there is a will there is a way. In the end it does not matter how you code but why you code. The why is deeply embedded in Smalltalk. On Mon, 24 Oct 2016 at 01:52, Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: > *stepharo:* > > I am not saying it for me, but to get other people into the Smalltalk > community. My interest in Smalltalk spark the first time I read the Design > Principles Behind Smalltalk, since then I: > > 1- Read the BlueBook (yes) before I know of Pharo; > 2- Read "I Can Read C++ and Java But I Canât Read Smalltalk"; > 3- Read a number of Smalltalk resources, tutorials, blogs etc; > 4- Did Profstef; > 5- Learn a little of Redline Smalltalk; > 6- Tried Squeek, didn't like; > 7- Find Pharo, like it more than Squeek; > 8- Read Pharo By Example almost entirely, the first example didn't work > (at least at the time) because some dependencies were missing, then I > search into the internet, found what was missing and keep going; > 9- Did the MOOC ENTIRELY, and I saw all the videos, yes! > > So, is there any other thing you think I *maybe* haven't done, despite > the fact that you don't know me much? > > As for someone who did the MOOC, I don't think it's a good tutorial in the > lines I understand Richard described in the start of this thread: for > newcomers. Don't get me wrong, it's a very good course if you would like to > get more deep into Pharo and OO, but I understand the intention of Richard > was other. So, except from Porfstef, I think none of those resources is a > good start point for newcomers, because none of them were good for me nor > the people I tried to introduce Pharo. I just keep going because I was > already VERY interested in Smalltalk, if not for that I would have > also given up. > > My opinion is only that, an opinion, you can take it or not, it was not > meant to be personal or whatever, but if you wanna take it as so there > isn't much I can do. > > *Phil:* > > Thanks for your suggestions, but I was just telling Richard that I think > the MOOC was too much for a tutorial, that I think other format and > something simpler would be better for newcomers. > > *Dimitri:* > > I am already on STEP 4 ;) > > I think what is missing is something before all that, something that spark > the "I am interested in Pharo", the STEP 0. What does that today? I think > a simple tutorial that catch the attention of people would do that. Right > now I think it is too hard for someone to get interested in Smalltalk in > general, and Pharo in particular, because something like that is missing, > and one must really understand and see the value of Smalltalk to persist > and keep going and learning, like happened to me. > > Regards, > Vitor > > On Sun, Oct 23, 2016 at 2:26 PM, Dimitris Chloupis <kilon.alios(a)gmail.com> > wrote: > > The four stages of Pharo addiction > > STEP1 > "I am interested in Pharo , any quick tutorial to get me started ?" > > If you want a quick dive to Pharo for experienced coders there is this > > > https://ci.inria.fr/pharo-contribution/job/UpdatedPharoByExample/lastSucces… > > STEP2 > "Ah I really like Pharo maybe more info about the language and a practical > example to give it a go myself ?" > > for a bit more dive into the Smalltalk language there is this > > > https://ci.inria.fr/pharo-contribution/job/UpdatedPharoByExample/lastSucces… > > STEP3 > "Damn this is really cool , where I can find more info I really like to > give this a deeper look!" > > and of course the rest of the book for those that cant get enough of Pharo > > https://github.com/SquareBracketAssociates/UpdatedPharoByExample > > > STEP4 > "I hate you so much !!! I cant sleep, cant eat, no friends, ex > girlfriend.... AHHH CANNNOT STOP !!!! TOO MUCH FUN!!!" > > > On Sun, Oct 23, 2016 at 4:16 PM Vitor Medina Cruz <vitormcruz(a)gmail.com> > wrote: > > I think the MOOC is too much for a tutorial. What I miss today is a good > written (no videos! Please!) tutorial that teaches just a little of the > language and give a few guidelines on how to do simple stuff with the > environment, such as a "Hello World!", creating a class, tests and run > stuff. > > On Sat, Oct 15, 2016 at 12:15 PM, horrido <horrido.hobbies(a)gmail.com> > wrote: > > Excellent suggestion! I shall look into it. Thanks. > > > > > -- > View this message in context: > http://forum.world.st/The-Ultimate-Smalltalk-Tutorial-tp4918859p4918930.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > > >

Oct. 24, 2016

Re: [Pharo-users] The Ultimate Smalltalk Tutorial

by Vitor Medina Cruz

*stepharo:* I am not saying it for me, but to get other people into the Smalltalk community. My interest in Smalltalk spark the first time I read the Design Principles Behind Smalltalk, since then I: 1- Read the BlueBook (yes) before I know of Pharo; 2- Read "I Can Read C++ and Java But I Canât Read Smalltalk"; 3- Read a number of Smalltalk resources, tutorials, blogs etc; 4- Did Profstef; 5- Learn a little of Redline Smalltalk; 6- Tried Squeek, didn't like; 7- Find Pharo, like it more than Squeek; 8- Read Pharo By Example almost entirely, the first example didn't work (at least at the time) because some dependencies were missing, then I search into the internet, found what was missing and keep going; 9- Did the MOOC ENTIRELY, and I saw all the videos, yes! So, is there any other thing you think I *maybe* haven't done, despite the fact that you don't know me much? As for someone who did the MOOC, I don't think it's a good tutorial in the lines I understand Richard described in the start of this thread: for newcomers. Don't get me wrong, it's a very good course if you would like to get more deep into Pharo and OO, but I understand the intention of Richard was other. So, except from Porfstef, I think none of those resources is a good start point for newcomers, because none of them were good for me nor the people I tried to introduce Pharo. I just keep going because I was already VERY interested in Smalltalk, if not for that I would have also given up. My opinion is only that, an opinion, you can take it or not, it was not meant to be personal or whatever, but if you wanna take it as so there isn't much I can do. *Phil:* Thanks for your suggestions, but I was just telling Richard that I think the MOOC was too much for a tutorial, that I think other format and something simpler would be better for newcomers. *Dimitri:* I am already on STEP 4 ;) I think what is missing is something before all that, something that spark the "I am interested in Pharo", the STEP 0. What does that today? I think a simple tutorial that catch the attention of people would do that. Right now I think it is too hard for someone to get interested in Smalltalk in general, and Pharo in particular, because something like that is missing, and one must really understand and see the value of Smalltalk to persist and keep going and learning, like happened to me. Regards, Vitor On Sun, Oct 23, 2016 at 2:26 PM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > The four stages of Pharo addiction > > STEP1 > "I am interested in Pharo , any quick tutorial to get me started ?" > > If you want a quick dive to Pharo for experienced coders there is this > > https://ci.inria.fr/pharo-contribution/job/UpdatedPharoByExample/ > lastSuccessfulBuild/artifact/book-result/PharoTour/PharoTour.html > > STEP2 > "Ah I really like Pharo maybe more info about the language and a practical > example to give it a go myself ?" > > for a bit more dive into the Smalltalk language there is this > > https://ci.inria.fr/pharo-contribution/job/UpdatedPharoByExample/ > lastSuccessfulBuild/artifact/book-result/FirstApplication/ > FirstApplication.html > > STEP3 > "Damn this is really cool , where I can find more info I really like to > give this a deeper look!" > > and of course the rest of the book for those that cant get enough of Pharo > > https://github.com/SquareBracketAssociates/UpdatedPharoByExample > > > STEP4 > "I hate you so much !!! I cant sleep, cant eat, no friends, ex > girlfriend.... AHHH CANNNOT STOP !!!! TOO MUCH FUN!!!" > > > On Sun, Oct 23, 2016 at 4:16 PM Vitor Medina Cruz <vitormcruz(a)gmail.com> > wrote: > >> I think the MOOC is too much for a tutorial. What I miss today is a good >> written (no videos! Please!) tutorial that teaches just a little of the >> language and give a few guidelines on how to do simple stuff with the >> environment, such as a "Hello World!", creating a class, tests and run >> stuff. >> >> On Sat, Oct 15, 2016 at 12:15 PM, horrido <horrido.hobbies(a)gmail.com> >> wrote: >> >> Excellent suggestion! I shall look into it. Thanks. >> >> >> >> >> -- >> View this message in context: http://forum.world.st/The- >> Ultimate-Smalltalk-Tutorial-tp4918859p4918930.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> >>

Oct. 23, 2016

Re: [Pharo-users] What is the correct way to go around implementing a GUI feature in Pharo?

by Johan Fabry

We are still working on this, so all your corrections, thoughts, comments are welcome! -- Does this mail seem too brief? Sorry for that, I donât mean to be rude! Please see http://emailcharter.org <http://emailcharter.org/> . Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile > On 23 Oct 2016, at 13:12, phil(a)highoctane.be wrote: > > Oooh, didn't knew about this one. Great, I was just in need of a couple more Spec clues. > > Phil > > On Sun, Oct 23, 2016 at 4:29 PM, Johan Fabry <jfabry(a)dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>> wrote: > > Building a small window with these menus and/or buttons is straightforward in Spec. Have a look at the Spec GUI documentation book (a work in progress): > https://ci.inria.fr/pharo-contribution/view/Books/job/BuildingUIWithSpec/la… <https://ci.inria.fr/pharo-contribution/view/Books/job/BuildingUIWithSpec/la…> > > Individual chapters are also available: > https://ci.inria.fr/pharo-contribution/view/Books/job/BuildingUIWithSpec/la… <https://ci.inria.fr/pharo-contribution/view/Books/job/BuildingUIWithSpec/la…> > > -- > Does this mail seem too brief? Sorry for that, I donât mean to be rude! Please see http://emailcharter.org <http://emailcharter.org/> . > > Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/~jfabry> > PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile > > > On 23 Oct 2016, at 01:53, CodeDmitry <dimamakhnin(a)gmail.com <mailto:dimamakhnin@gmail.com>> wrote: > > > > I want to have a bootstrap-like navbar at the top of my pharo GUI to store > > commonly accessed features/custom hierarchies of menus. > > > > My first thought is that I should spend a bunch of time playing with Morphs > > and invent my own MVC(models being the state managed by the menu, views > > being the controls(morphs), and controllers being asynchronous blocks of > > code that are invoked when events occur). > > > > Are there any good resources that teach how to go around doing stuff like > > this, or do I have to reinvent it myself by researching how Pharo GUI works > > internally, and figure out how to do this by successful incremental > > experiments? > > > > > > > > > > > > -- > > View this message in context: http://forum.world.st/What-is-the-correct-way-to-go-around-implementing-a-G… <http://forum.world.st/What-is-the-correct-way-to-go-around-implementing-a-G…> > > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > > > > > > >

Oct. 23, 2016

Re: [Pharo-users] [Pharo-dev][ANN] Scale

by Tudor Girba

Nice work! Doru > On Oct 23, 2016, at 8:36 PM, Santiago Bragagnolo <santiagobragagnolo(a)gmail.com> wrote: > > > Hi everybody. > > We are officially releasing a first version of scale. > > Scale is a command line handler that is there for making easier the life of the people that uses scripting in linux. As such, we only tested it so far in linux. It will be for sure easy to adapt it to mac because its a *nix, but not for windoze. > > IMPORTANT REMARK: scale is not meant to develop applications, it is meant to develop scripts in Pharo, to be launched from the command line. This means that scale does not provide a top level syntax to declare classes or methods: people should do that as any normal Pharo application. Scale should be used to invoke such applications. > > When would you use scale? > - For example, to replace some bash scripts used for common boring tasks (and you are using python or ruby there :P) > - Another example, would be when you want to replace bash scripts that chain things like: > ./pharo eval --save "something" > ./pharo eval --save "other something" > ... > > Github: https://github.com/guillep/Scale > Oneliner to install: (note it needs sudo) > wget -O- https://raw.githubusercontent.com/guillep/Scale/master/setupScale.sh | sudo bash > > In the repository there is some user level documentation based on examples and a list of available methods on the magical variable system. There are many examples as well on the repository. > > Last but not least, I'm using this project in others two projects, where it proof it self quite powerful what keeps me on maintaining Scale. > > These projects are: > > Pharo Android VM building https://github.com/sbragagnolo/pharo-vm > > Here I use it for automating the creation of a > * new building image, > * the creation of new resource image (for deploying on the android apk), > * linking the android sources into the building directory > * generating the code from the console > > MakrosTool https://github.com/sbragagnolo/MakrosTool > > MakrosTool is an extension of scale that adds a second magical variable for building up component reification in a ROS based environment. > > > Santiago & Guille > > > > > -- www.tudorgirba.com www.feenk.com âThe smaller and more pervasive the hardware becomes, the more physical the software gets."

Oct. 23, 2016

Re: [Pharo-users] [Pharo-dev][ANN] Scale

by Dimitris Chloupis

Great work, I did discover your project by accident with searching around Github, a good reason to have pharo projects on Github. One thing I would like and I know this is easier said than done, is the ability to directly mix bash script with scale script on the same file. Of course I see that you have already included many bash commands and have the ability to execute a string as bash. Definitely will give it a try, thank you :) On Sun, Oct 23, 2016 at 9:37 PM Santiago Bragagnolo < santiagobragagnolo(a)gmail.com> wrote: > > Hi everybody. > > We are officially releasing a first version of scale. > > Scale is a command line handler that is there for making easier the life > of the people that uses scripting in linux. As such, we only tested it so > far in linux. It will be for sure easy to adapt it to mac because its a > *nix, but not for windoze. > > *IMPORTANT REMARK*: scale is not meant to develop applications, it is > meant to develop scripts in Pharo, to be launched from the command line. > This means that scale does not provide a top level syntax to declare > classes or methods: people should do that as any normal Pharo application. > Scale should be used to invoke such applications. > > When would you use scale? > - For example, to replace some bash scripts used for common boring tasks > (and you are using python or ruby there :P) > - Another example, would be when you want to replace bash scripts that > chain things like: > ./pharo eval --save "something" > ./pharo eval --save "other something" > ... > > Github: https://github.com/guillep/Scale > Oneliner to install: (note it needs sudo) > > wget -O- https://raw.githubusercontent.com/guillep/Scale/master/setupScale.sh | sudo bash > > > In the repository there is some user level documentation based on examples > and a list of available methods on the magical variable system. There are > many examples as well on the repository. > > Last but not least, I'm using this project in others two projects, where > it proof it self quite powerful what keeps me on maintaining Scale. > > These projects are: > > *Pharo Android VM building *https://github.com/sbragagnolo/pharo-vm > > Here I use it for automating the creation of a > * new building image, > * the creation of new resource image (for deploying on the android > apk), > * linking the android sources into the building directory > * generating the code from the console > > *MakrosTool* https://github.com/sbragagnolo/MakrosTool > > MakrosTool is an extension of scale that adds a second magical variable > for building up component reification in a ROS based environment. > > > Santiago & Guille > > > > > >

Oct. 23, 2016

[Pharo-dev][ANN] Scale

by Santiago Bragagnolo

Hi everybody. We are officially releasing a first version of scale. Scale is a command line handler that is there for making easier the life of the people that uses scripting in linux. As such, we only tested it so far in linux. It will be for sure easy to adapt it to mac because its a *nix, but not for windoze. *IMPORTANT REMARK*: scale is not meant to develop applications, it is meant to develop scripts in Pharo, to be launched from the command line. This means that scale does not provide a top level syntax to declare classes or methods: people should do that as any normal Pharo application. Scale should be used to invoke such applications. When would you use scale? - For example, to replace some bash scripts used for common boring tasks (and you are using python or ruby there :P) - Another example, would be when you want to replace bash scripts that chain things like: ./pharo eval --save "something" ./pharo eval --save "other something" ... Github: https://github.com/guillep/Scale Oneliner to install: (note it needs sudo) wget -O- https://raw.githubusercontent.com/guillep/Scale/master/setupScale.sh | sudo bash In the repository there is some user level documentation based on examples and a list of available methods on the magical variable system. There are many examples as well on the repository. Last but not least, I'm using this project in others two projects, where it proof it self quite powerful what keeps me on maintaining Scale. These projects are: *Pharo Android VM building *https://github.com/sbragagnolo/pharo-vm Here I use it for automating the creation of a * new building image, * the creation of new resource image (for deploying on the android apk), * linking the android sources into the building directory * generating the code from the console *MakrosTool* https://github.com/sbragagnolo/MakrosTool MakrosTool is an extension of scale that adds a second magical variable for building up component reification in a ROS based environment. Santiago & Guille

Oct. 23, 2016

Re: [Pharo-users] How to add a dependency in a baseline

by Dimitris Chloupis

Well I started by using Gofer instead of spec configuration for Pillar. That is what I regarded an ugly hack but with some googling I found a solution via spec configuration and was not sure if it was a good solution hence why asked. The intention is indeed to load Pillar development, mainly because I wanted to take advantage of the Pillar Editor but if it proves too unstable I can always revert back to stable. Thanks indeed the first code fragment is what I wanted to make sure it works well. Will keep lock in mind for the future. Thanks again. Curious question: let say that the spec configuration in first code fragment fails to load for various reason, is there a way for metacello to detect the fail and add something to the baseline , let say the stable version of pillar, so if it sees that the development version of pillar fails to load it falls back to loading the stable version instead ? Essentially I am asking here about metacello exceptions. On Sun, Oct 23, 2016 at 8:26 PM Dale Henrichs < dale.henrichs(a)gemtalksystems.com> wrote: > Dimitris, > > This is your baseline method and I'm not sure what you consider "an ugly > hack": > > baseline: spec > <baseline> > spec for: #'pharo' do: [ > spec > package: 'Octopus' with: [ spec requires: #('Pillar') ]; > configuration: 'Pillar' with: [ > spec > repository: 'http://smalltalkhub.com/mc/Pier/Pillar/main > '; > version: #'development' ] ] > > Is it the fact that you have to include #development instead of #stable > in your baseline? If so , you can make a pre-load decision to use the > development version of Pillar by using a Metacello lock: > > Metacello new > configuration: 'Pillar' > version: #development; > repository: 'http://smalltalkhub.com/mc/Pier/Pillar/main'; > lock. > > Then you can change your baseline back to using #stable or whatever and > when you load the Octopus project, using 'Metacello new', the > #development version should be used ... > > Or is there something else that you consider "an ugly hack"? > > Dale > > On 10/23/16 6:46 AM, Dimitris Chloupis wrote: > > I have a baseline in my github repo for a tool I am making and I have > > included the pillar development dependency via an ugly hack , whats it > > the proper way of doing this ? > > > > > https://github.com/kilon/Octopus/blob/master/BaselineOfOctopus.package/Base… > > > > > > >

Oct. 23, 2016