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

Re: [Pharo-dev] [ANN] Scale

by stepharo

Guille I could not really understand the three points below. I have some questions: - "Scale introduces a new command line handler to manage scripts. " do you mean a separate way of managing command lines? - "syntax sugar to script" which one? the #! ... "Scale requires TaskIt and OSSubprocess to provide easy-to-use interaction with the system. Should all this be part of Pharo" - to me this is ok to get it separated but I believe that we should really think about that because to me Pharo should support exactly such kind of programs. Also if TaskIt enhance for real the concurrency model then why not using to support better Pharo? Stef Le 24/10/16 Ã 11:09, Guillermo Polito a Ã©crit : > Hi all, > > and thanks Santi for rescuing Scale from the Limbo :). > > I saw already some discussions pointing to this thread indirectly. I > want to answer some philosophical aspects, just to remove some burden > from Santi who is the real one that should take credit for pushing > this to the light ^^. > > 1) Why scale and not "pharo scripting". I saw an email from Norbert > about this. > > Well, I remember we discussed this with Santi a couple of years ago > about this, when we started and brainstormed about it, but I am not > able to remember the exact details right now. But, I can still think > about some arguments in favor of the current decision (which we may > not keep in the future, hey :)) > > - First, Pharo is different from ruby and python in terms of > deployment. In ruby and python, you have the main libraries that are > shared and your application is deployed locally as files. We can think > that the script becomes the application. In Pharo, to write an > application we need to interact and change with the environment. Thus > we cannot share it. You can think about scale as a read-only pharo > environment deployed in your machine for scripting purposes. > - Second, Scale is Pharo, but not only. Scale introduces a new command > line handler to manage scripts. Scale introduces an interpreter that > is the one that is in charge of executing the code, provide special > bindings and syntax sugar to scripts (see e.g. the 'system' instance > in scripts). Scale requires TaskIt and OSSubprocess to provide > easy-to-use interaction with the system. Should all this be part of > Pharo? Well I do not know but I prefer to keep it as a separate > entity. Maybe we can call it a separate distribution, installation or > whatever. > > - Third, if it is a matter of naming (which I think it is), something > that comes out of the second point is that > > #! /usr/bin/local/scale => #! /usr/bin/local/pharo scale > > or better => #! /usr/bin/env pharo scale ? > > 2) We would appreciate if feedback is not lost in the mailing list but > is converted in issues instead: > > https://github.com/guillep/Scale/issues > > Fell free to contribute, provide feedback or even check the code, it > is really a simple and short project. > It was nice that Santi implemented scale installation in scale :) > > Cheers, > Guille > > On Sun, Oct 23, 2016 at 11:04 PM, phil(a)highoctane.be > <mailto:phil@highoctane.be> <phil(a)highoctane.be > <mailto:phil@highoctane.be>> wrote: > > Ok thanks, that will do for me. > > Phil > > On Sun, Oct 23, 2016 at 10:11 PM, Santiago Bragagnolo > <santiagobragagnolo(a)gmail.com > <mailto:santiagobragagnolo@gmail.com>> wrote: > > Thanks Phil! That's not easy to do now, Is mean to be a > feature for the next version. > > By the moment you have to add the variable to SCScriptRunner > and initialize the value maybe in initialize. > > This SCScriptRunner is the context of execution of the script. > > > > On Sun, 23 Oct 2016 at 21:48 phil(a)highoctane.be > <mailto:phil@highoctane.be> <phil(a)highoctane.be > <mailto:phil@highoctane.be>> wrote: > > Ah, this is just *beautiful* > > Thank you thank you thank you for making this available. > > Question: How is one creating a new scripting object and > making it available? (like system etc). > > Phil > > > > > > On Sun, Oct 23, 2016 at 8:34 PM, Santiago Bragagnolo > <santiagobragagnolo(a)gmail.com > <mailto:santiagobragagnolo@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 > <https://github.com/guillep/Scale> > Oneliner to install: (note it needs sudo) > > wget -O-https://raw.githubusercontent.com/guillep/Scale/master/setupScale.sh > <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 > <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 > <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. 24, 2016

Re: [Pharo-dev] [REMEMBER] TechTalk tomorrow 16UTC

by Dale Henrichs

No problem ... it was early in the morning for me and I wasn't thinking that clearly ... as if I do think clearly later in the day:) Dale On 10/24/2016 08:02 AM, Esteban Lorenzano wrote: > oops, yesâ¦ tuesday 25/10â¦ sorry for the mess :) > >> On 24 Oct 2016, at 16:35, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: >> >> Hmmm... since Esteban sent the email at 1 am my time and this _is_ tomorrow for me ... but perhaps Esteban means Tuesday? since I think this is still _today_ in Europe? >> >> Dale >> >> >> On 10/24/16 7:31 AM, Dale Henrichs wrote: >>> Since time is short (for me) and I still have to get out ouf bed, shower eat and maybe get into the office before the meeting ... could someone drop me an email with the details I need to find and install (?) discord and find the techtalk ... I'll be out of pocket for about an hour getting ready --- as this is short notice (for me) --- >>> >>> Thanks, >>> >>> Dale >>> >>> On 10/24/16 12:58 AM, Esteban Lorenzano wrote: >>>> Hello fellow pharoers, >>>> >>>> The time has come (1 month passes so fast!). And tomorrow we will be handling another TechTalk. >>>> This time we propose to talk about the new Bootstrap process. >>>> >>>> For this, Iâd ask Guille, Pavel and/or Christophe to be present. They are the ones actually working on it, so weâll all learn from what they have to say :) >>>> >>>> Meeting will be handled with discord, as last time. >>>> >>>> And as always, this will also be a place to ask anything about pharo development (statuses, proposals, etc., etc., etc.) >>>> >>>> See you tomorrow ! >>>> >>>> Esteban >> >

Oct. 24, 2016

Re: [Pharo-dev] MetaLink to conditionally skip a method execution based on an arg

by test

Hi, i would be also interested in answer to this interesting MetaLink-question. werner p.s. Yuriy, i guess this could also be done with ghost On 10/23/2016 09:21 AM, Yuriy Tymchuk wrote: > Iâve also described the question with examples on SO: > https://stackoverflow.com/questions/40200546/conditionally-skip-a-method-wi… > >> On 22 Oct 2016, at 23:13, Yuriy Tymchuk <yuriy.tymchuk(a)me.com >> <mailto:yuriy.tymchuk@me.com>> wrote: >> >> Hi. >> >> Imagine I have method /a:/ and I want to skip the execution (return >> self or nil or whatever) when /a:/ is evaluated with parameter 0. I >> have tried to add a meta link which will run instead of the method >> with a condition, but the condition did not workâ¦ I have tried to >> implement the metallic method to do nothing if the arg is 0 otherwise >> to perform the method, but I end up with an infinite loopâ¦ >> >> Did anybody do something like that already? Any suggestions? >> >> Uko >

Oct. 24, 2016

Re: [Pharo-dev] Spur VM Bug for Chinese Characters?

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote > I decided to... simplify implementation Thanks for following up! ----- Cheers, Sean -- View this message in context: http://forum.world.st/Spur-VM-Bug-for-Chinese-Characters-tp4918883p4919990.… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 24, 2016

Re: [Pharo-dev] [REMEMBER] TechTalk tomorrow 16UTC

by phil＠highoctane.be

https://discord.gg/EBDhD On Mon, Oct 24, 2016 at 4:44 PM, Blondeau Vincent < vincent.blondeau(a)worldline.com> wrote: > I think that his tomorrow is Tuesday, because he sent the email Monday > (CEST). > But, I will be interested by a link to find the TechTalk on discord too. > > Thanks > > Vincent > > > -----Message d'origine----- > > De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de > > Dale Henrichs > > EnvoyÃ© : lundi 24 octobre 2016 16:35 > > Ã : pharo-dev(a)lists.pharo.org > > Objet : Re: [Pharo-dev] [REMEMBER] TechTalk tomorrow 16UTC > > > > Hmmm... since Esteban sent the email at 1 am my time and this _is_ > > tomorrow for me ... but perhaps Esteban means Tuesday? since I think > this is > > still _today_ in Europe? > > > > Dale > > > > > > On 10/24/16 7:31 AM, Dale Henrichs wrote: > > > Since time is short (for me) and I still have to get out ouf bed, > > > shower eat and maybe get into the office before the meeting ... could > > > someone drop me an email with the details I need to find and install > > > (?) discord and find the techtalk ... I'll be out of pocket for about > > > an hour getting ready --- as this is short notice (for me) --- > > > > > > Thanks, > > > > > > Dale > > > > > > On 10/24/16 12:58 AM, Esteban Lorenzano wrote: > > >> Hello fellow pharoers, > > >> > > >> The time has come (1 month passes so fast!). And tomorrow we will be > > >> handling another TechTalk. > > >> This time we propose to talk about the new Bootstrap process. > > >> > > >> For this, Iâd ask Guille, Pavel and/or Christophe to be present. They > > >> are the ones actually working on it, so weâll all learn from what > > >> they have to say :) > > >> > > >> Meeting will be handled with discord, as last time. > > >> > > >> And as always, this will also be a place to ask anything about pharo > > >> development (statuses, proposals, etc., etc., etc.) > > >> > > >> See you tomorrow ! > > >> > > >> Esteban > > > > > > > > !!!********************************************************* > **************************** > "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage > exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret > professionnel. Si vous recevez ce message par erreur, merci d'en avertir > immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne > pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra > Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs > efforts soient faits pour maintenir cette transmission exempte de tout > virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa > responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un > virus transmis. > > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive this > e-mail in error, please notify the sender immediately and destroy it. As > its integrity cannot be secured on the Internet, the Worldline liability > cannot be triggered for the message content. Although the sender endeavours > to maintain a computer virus-free network, the sender does not warrant that > this transmission is virus-free and will not be liable for any damages > resulting from any virus transmitted.!!!" >

Oct. 24, 2016

Re: [Pharo-dev] [REMEMBER] TechTalk tomorrow 16UTC

by Esteban Lorenzano

oops, yesâ¦ tuesday 25/10â¦ sorry for the mess :) > On 24 Oct 2016, at 16:35, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: > > Hmmm... since Esteban sent the email at 1 am my time and this _is_ tomorrow for me ... but perhaps Esteban means Tuesday? since I think this is still _today_ in Europe? > > Dale > > > On 10/24/16 7:31 AM, Dale Henrichs wrote: >> Since time is short (for me) and I still have to get out ouf bed, shower eat and maybe get into the office before the meeting ... could someone drop me an email with the details I need to find and install (?) discord and find the techtalk ... I'll be out of pocket for about an hour getting ready --- as this is short notice (for me) --- >> >> Thanks, >> >> Dale >> >> On 10/24/16 12:58 AM, Esteban Lorenzano wrote: >>> Hello fellow pharoers, >>> >>> The time has come (1 month passes so fast!). And tomorrow we will be handling another TechTalk. >>> This time we propose to talk about the new Bootstrap process. >>> >>> For this, Iâd ask Guille, Pavel and/or Christophe to be present. They are the ones actually working on it, so weâll all learn from what they have to say :) >>> >>> Meeting will be handled with discord, as last time. >>> >>> And as always, this will also be a place to ask anything about pharo development (statuses, proposals, etc., etc., etc.) >>> >>> See you tomorrow ! >>> >>> Esteban >> > >

Oct. 24, 2016

Re: [Pharo-dev] [REMEMBER] TechTalk tomorrow 16UTC

by Marcus Denker

> On 24 Oct 2016, at 16:35, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: > > Hmmm... since Esteban sent the email at 1 am my time and this _is_ tomorrow for me ... but perhaps Esteban means Tuesday? since I think this is still _today_ in Europe? Indeed! It is tuesday. Which reminds me of this nice quote: "Don't worry about the world coming to an end today. It is already tomorrow in Australia." â Charles M. Schulz

Oct. 24, 2016

Re: [Pharo-dev] [REMEMBER] TechTalk tomorrow 16UTC

by Denis Kudriashov

Yes 2016-10-24 16:35 GMT+02:00 Dale Henrichs <dale.henrichs(a)gemtalksystems.com>: > Hmmm... since Esteban sent the email at 1 am my time and this _is_ > tomorrow for me ... but perhaps Esteban means Tuesday? since I think this > is still _today_ in Europe? > > Dale > > > > On 10/24/16 7:31 AM, Dale Henrichs wrote: > >> Since time is short (for me) and I still have to get out ouf bed, shower >> eat and maybe get into the office before the meeting ... could someone drop >> me an email with the details I need to find and install (?) discord and >> find the techtalk ... I'll be out of pocket for about an hour getting ready >> --- as this is short notice (for me) --- >> >> Thanks, >> >> Dale >> >> On 10/24/16 12:58 AM, Esteban Lorenzano wrote: >> >>> Hello fellow pharoers, >>> >>> The time has come (1 month passes so fast!). And tomorrow we will be >>> handling another TechTalk. >>> This time we propose to talk about the new Bootstrap process. >>> >>> For this, Iâd ask Guille, Pavel and/or Christophe to be present. They >>> are the ones actually working on it, so weâll all learn from what they have >>> to say :) >>> >>> Meeting will be handled with discord, as last time. >>> >>> And as always, this will also be a place to ask anything about pharo >>> development (statuses, proposals, etc., etc., etc.) >>> >>> See you tomorrow ! >>> >>> Esteban >>> >> >> > >

Oct. 24, 2016

Re: [Pharo-dev] [REMEMBER] TechTalk tomorrow 16UTC

by Blondeau Vincent

I think that his tomorrow is Tuesday, because he sent the email Monday (CEST). But, I will be interested by a link to find the TechTalk on discord too. Thanks Vincent > -----Message d'origine----- > De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de > Dale Henrichs > EnvoyÃ© : lundi 24 octobre 2016 16:35 > Ã : pharo-dev(a)lists.pharo.org > Objet : Re: [Pharo-dev] [REMEMBER] TechTalk tomorrow 16UTC > > Hmmm... since Esteban sent the email at 1 am my time and this _is_ > tomorrow for me ... but perhaps Esteban means Tuesday? since I think this is > still _today_ in Europe? > > Dale > > > On 10/24/16 7:31 AM, Dale Henrichs wrote: > > Since time is short (for me) and I still have to get out ouf bed, > > shower eat and maybe get into the office before the meeting ... could > > someone drop me an email with the details I need to find and install > > (?) discord and find the techtalk ... I'll be out of pocket for about > > an hour getting ready --- as this is short notice (for me) --- > > > > Thanks, > > > > Dale > > > > On 10/24/16 12:58 AM, Esteban Lorenzano wrote: > >> Hello fellow pharoers, > >> > >> The time has come (1 month passes so fast!). And tomorrow we will be > >> handling another TechTalk. > >> This time we propose to talk about the new Bootstrap process. > >> > >> For this, Iâd ask Guille, Pavel and/or Christophe to be present. They > >> are the ones actually working on it, so weâll all learn from what > >> they have to say :) > >> > >> Meeting will be handled with discord, as last time. > >> > >> And as always, this will also be a place to ask anything about pharo > >> development (statuses, proposals, etc., etc., etc.) > >> > >> See you tomorrow ! > >> > >> Esteban > > > !!!************************************************************************************* "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

Oct. 24, 2016

Re: [Pharo-dev] [ANN] Scale

by Denis Kudriashov

2016-10-24 16:27 GMT+02:00 Santiago Bragagnolo <santiagobragagnolo(a)gmail.com >: > (system home / #pharo) ensureCreateDirectory. > pharo5 := system loadPharo: 50 into: system home / #pharo. > pharo5WithScale := system loadBaseline: 'Scale' from: 'github://path' > into: pharo5. > Maybe we should add #execute: into SCImageBundle? With this we could simply write: pharo5 := system loadPharo: 50 into: system home / #pharo. pharo5 execute: myCodeString And maybe for convenience we could ask #asImageBundle on passed arguments of system #execute: methods? system execute: myCodeString into: 'myPharo' asFileReference

Oct. 24, 2016