- Pharo-dev - lists.pharo.org

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

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

by Dale Henrichs

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 Dale Henrichs

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] [ANN] Scale

by Santiago Bragagnolo

Hi Denis! Thanks. There is an class called SCImageBundle. It represents the folder where you downloaded a pharo+vm. So you can instantiate it by hand SCImageBundle new directory: 'path' asFileReference. in any case, this is also the return of the following messages of the system object: #loadPharo: aVersion into: aFileReference #loadBaseline: aPackageName from: aRepository into: anImageBundle andSaveItAt: aDirectory #loadBaselineUI: aPackageName from: aRepository into: anImageBundle andSaveItAt: aDirectory So you can do something like (system home / #pharo) ensureCreateDirectory. pharo5 := system loadPharo: 50 into: system home / #pharo. pharo5WithScale := system loadBaseline: 'Scale' from: 'github://path' into: pharo5. Save after run just sets a flag. If to the end of the execution is on, it saves the image before shutting it down. If the script you are running is supposed to update the same image that is running you have to use this method (and run as sudo) On Mon, 24 Oct 2016 at 11:49 Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Really nice project, Santiago. > > I have few questions: > > - what "system saveAfterRun" actually do? > > As I understand it saves image when script completes. Imaging during > script I loaded Seaside. Does this command makes Seaside accessible from > any scale scripts? > > - system execute: aString into: anImageBundle > > What is anImageBundle here? > > - What you think to make scripts working as workspace? All undeclared > variables will be added to environment automatically. And in case of > saveAfterRun they will became accessible from any scale scripts. > > > 2016-10-23 20:34 GMT+02:00 Santiago Bragagnolo < > santiagobragagnolo(a)gmail.com>: > > 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. 24, 2016

Re: [Pharo-dev] Fwd: Call for design for a literal programming doc similar to PythonDocTest

by phil＠highoctane.be

Nice, seems to work. Now, I tried to click on a package tag and add a comment at that level. For sure it erased the previous one. We may not allow people to edit package level comment when on a package tag. Also manifest >>description is like description ^ 'some desc' Would be nicer like description ^ 'some desc' Just sayin' b/c this is what the formatter does when asked. Phil Phil On Mon, Oct 24, 2016 at 9:35 AM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > 2016-10-10 21:29 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: > >> Whatever would be better than what we have now. >> I like what you propose, makes sense and doesn't loads the UI with more >> stuff. >> >> I am willing to test your implementation for sure. >> > > > it is in now (Pharo 60267). If anything is missing, not working or > whatever, please report back. > (Packages without package manifest class show just nothing, but you can > add a new package comment (package manifest class will be created). > If a package manifest class exists, but without a #description you text > appears in the comment pane ("No package comment in this manifest .... > please add a comment"). > > >> >> Phil >> >> On Mon, Oct 10, 2016 at 6:56 PM, Nicolai Hess <nicolaihess(a)gmail.com> >> wrote: >> >>> >>> ---------- Forwarded message ---------- >>> From: Nicolai Hess <nicolaihess(a)gmail.com> >>> Date: 2016-09-16 17:01 GMT+02:00 >>> Subject: Re: [Pharo-dev] Call for design for a literal programming doc >>> similar to PythonDocTest >>> To: Pharo Development List <pharo-dev(a)lists.pharo.org> >>> >>> >>> >>> >>> 2016-09-16 0:19 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: >>> >>>> I'd be more interested with a package level doc than a class doc or >>>> test. >>>> >>>> Package level doc is quite useful to outline how some things are >>>> working together, something which is quite hard to figure out except by >>>> reading external doc or inferring things by walking through the code or a >>>> running test. >>>> >>> >>> >>> Why don't we have yet package comments ? >>> I see there is some support for it in PackageManifest, I remember there >>> was some work (people working) on support for Nautilus, no? >>> >>> maybe something like this, (see attached file) >>> Nautilus comment pane >>> on class selection -> show class comment >>> no class selection -> show package comment (class side #description of >>> package manifest of this package) >>> you can even add or change the (package) comment, it will compile a >>> proper #description method on the manifest class) >>> >>> >>> Anyone looked at this ? >>> Is this what we can use for supporting and editing package comments? I >>> am not sure if the >>> use of package manifests is how we wanted to implement package comments. >>> Any other ideas? >>> >>> I can open a fogbugzs issue and refine this implementation a little bit. >>> >>> >>> >>>> Having the ability to read about a package would be very useful. >>>> Basically, this is what Java provides. >>>> >>>> http://docs.oracle.com/javase/7/docs/technotes/tools/solaris >>>> /javadoc.html#packagecomment >>>> >>>> Phil >>>> >>>> >>>> On Thu, Sep 15, 2016 at 8:45 PM, stepharo <stepharo(a)free.fr> wrote: >>>> >>>>> Hi all >>>>> >>>>> I want something similar in the spirit to PythonDocTest >>>>> https://docs.python.org/2/library/doctest.html >>>>> >>>>> I'm talking about >>>>> >>>>> basename >>>>> "Returns the base of the basename, >>>>> i.e. >>>>> /foo/gloops.taz basename is 'gloops.taz' >>>>> / basename is '/'" >>>>> >>>>> Pragmas do not work well i.e., >>>>> basename >>>>> "Returns the base of the basename" >>>>> <expr: '''/foo/gloops.taz'' asFileReference basename' result: >>>>> 'gloops.taz'> >>>>> >>>>> >>>>> We should invent a syntax to be put inside comments and that we can >>>>> easily parse because we need to improve >>>>> the use and discovery of the library. >>>>> >>>>> I was thinking about >>>>> >>>>> basename >>>>> "Returns the base of the basename" >>>>> " >>>>> '/foo/gloops.taz' asFileReference basename >>>>> >>> 'gloops.taz' >>>>> " >>>>> >>>>> Do you have any idea? >>>>> >>>>> I cannot not do anything and just complain that our methods are not >>>>> that well documented. >>>>> We as a community should take this and build an super cool system. >>>>> >>>>> I tried and defined >>> on Object to see if it works! >>>>> >>>>> Object >>> aResultingObject >>>>> "If the method comment contains >>> then it is a pharo >>>>> documentated test. We can check that it is true." >>>>> >>>>> " >>>>> '/foo/gloops.taz' asFileReference basename >>>>> >>> 'gloops.taz' >>>>> " >>>>> >>>>> ^ self = aResultingObject >>>>> >>>>> >>>>> Stef >>>>> >>>>> >>>>> >>>> >>> >>> >> >

Oct. 24, 2016

Re: [Pharo-dev] [ANN] Scale

by Denis Kudriashov

2016-10-24 11:48 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > What you think to make scripts working as workspace? All undeclared > variables will be added to environment automatically. And in case of > saveAfterRun they will became accessible from any scale scripts. > It makes me feel that it could allow things which are impossible with ruby, python or whatever.

Oct. 24, 2016