- Pharo-users - lists.pharo.org

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

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

by Dale Henrichs

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

Re: [Pharo-users] The Ultimate Smalltalk Tutorial

by Dimitris Chloupis

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. 23, 2016

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

by phil＠highoctane.be

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> 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/ > lastSuccessfulBuild/artifact/book-result/SpecBooklet.pdf > > Individual chapters are also available: > https://ci.inria.fr/pharo-contribution/view/Books/job/BuildingUIWithSpec/ > lastSuccessfulBuild/artifact/book-result/ > > -- > Does this mail seem too brief? Sorry for that, I donât mean to be rude! > Please see 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 01:53, CodeDmitry <dimamakhnin(a)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-GUI-feature-in- > Pharo-tp4919772.html > > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > > > > > > >

Oct. 23, 2016

Re: [Pharo-users] The Ultimate Smalltalk Tutorial

by phil＠highoctane.be

BlueBook. Read the first half. http://stephane.ducasse.free.fr/FreeBooks/BlueBook/Bluebook.pdf HelloWorld: VTermOutputDriver stdout green: 'Hello World' If you are on OSX or Linux, will be shown on the console. Windows: writes the string in the stdout file in the image directory (silly Windows VM issue). In Pharo itself: Transcript open; << 'Hello World' HTH Phil On Sun, Oct 23, 2016 at 3:15 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-Ulti >> mate-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 Offray Vladimir Luna CÃ¡rdenas

Hi, On 23/10/16 04:07, Stephan Eggermont wrote: > On 23/10/16 06:53, CodeDmitry wrote: >> 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? > > This mostly just assembles and configures a number of existing parts. > Take a look at DockingBarMorph & friends. > > Stephan > > I'm using Stephan's suggested approach to bring a fixed easy to access place in the Pharo GUI for the stuff we commonly use on Grafoscopio: Cheers, Offray

Oct. 23, 2016

[ANN] Octopus: An easy way to generate HTML code using Pillar syntax

by Dimitris Chloupis

A new tool for those people who work with HTML and want to use pillar because its much easier but dont want to battle with mustache templates or want for fine grained control video https://www.youtube.com/watch?v=R0VAJgFQ0lg&feature=youtu.be repository with code and documentation https://github.com/kilon/Octopus

Oct. 23, 2016