August 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] (no subject)

by Guillermo Polito

On Sun, Aug 13, 2017 at 10:31 AM, Vityou . <zlee314(a)gmail.com> wrote: > I recently discovered the pharo launcher. However, it only gives me > options to use outdated images, and I'm not sure about the vm. Is there > any way to change this? > Usually it will download the right vm for your image so you don't have to care. -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Aug. 13, 2017

Re: [Pharo-users] including Pillar in Pharo image by default

by Norbert Hartl

Hi, > Am 11.08.2017 um 21:10 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > hi, > >> On 11 Aug 2017, at 18:57, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com <mailto:cyril.ferlicot@gmail.com>> wrote: >> >> Another step would be to get a minimal parser not relying on >> PetitParser. > > Letâs think differently: why not to include a tiny PetitParser? > Then we can think on: > > - pillar sintax (better than just a restricted version) > - simplify other âsmall parsersâ that are already on the image. > - we provide a tool to o cool stuff (instead relying as always in regexp, etc.) > +1 I like that. I always feel bad if I use regex in pharo because I think I can do better. But then installing petit parser just to do some parsing sounds heavy weight. And parsing is such central functionality that it would be good to have a small parser near the core. For pillar I would like to see that class comments are a layer on top of the image core. It is metadata that can be optional and pillar could be a dependency to that layer. This would make it possible to strip out on deployment, too. Because I don't need class comments on my server :) Norbert

Aug. 13, 2017

(no subject)

by Vityou .

I recently discovered the pharo launcher. However, it only gives me options to use outdated images, and I'm not sure about the vm. Is there any way to change this?

Aug. 13, 2017

[ann] moldable editor - syntax highlighting ... with a twist

by Tudor Girba

Hi, After another intense week, we are happy to announce that the Brick editor now supports some advanced syntax highlighting. To put it in perspective, let us take a look at one screenshot showing an inspector presentation containing a Brick editor opened on a Pillar file that includes some text, a code snippet and a reference to a picture: This shows both that we style the text based on the Pillar grammar, but also that we can style Smalltalk code (in fact, we have two nested stylers here). But, the more interesting thing is that below the picture reference, we get to see the actual picture (which happens to be another inspector screenshot). In fact, this picture is actually just another text attribute (we call it an adornment) that can be dynamically added to any text elements. This opens up a whole lot of expression power and it is all easily compose-able. This is another reason why we say that this editor is moldable and you should expect new applications making use of this moldability and combining it with the liveliness of Pharo. The latest Brick code is loadable through: Metacello new baseline: 'Brick'; repository: 'github://pharo-graphics/Brick/src'; load: #development. If you want to play with Pillar, load the following extra code and just inspect a Pillar file: Metacello new smalltalkhubUser: 'Pier' project: 'Pillar'; configuration: 'Pillar'; version: #development; load. ((IceRepository registry detect: [ :each | each name = 'Brick' ]) packageNamed: 'Brick-Editor-Pillar') loadLatest. One other thing to mention is performance. What Alex (Syrel) managed to do is quite remarkable. To see the impact in practice, try editing the largest method in Pharo (UnicodeDefinitions class >> #data) in both the built-in editor and in the Brick editor by inspecting: BrTextEditor onMethod: UnicodeDefinitions class >> #data There are still issues left to deal with and we will focus on them in the following weeks. But, we can safely say that the most important challenges are now behind us and that the design of the editor code is stable and robust. Please do let us know what you think. Cheers, The feenk team -- www.tudorgirba.com www.feenk.com "If you interrupt the barber while he is cutting your hair, you will end up with a messy haircut."

Aug. 12, 2017

Re: [Pharo-users] including Pillar in Pharo image by default

by Esteban Lorenzano

> On 12 Aug 2017, at 18:22, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Esteban, I think that when Stef says "a mini version of pillar" he does not mean a mini version of the parser or the AST, but a version that does not have the exporting to html/latex/â¦ I know that. But Cyril talked about âgetting a parser without PPâ. That's where my comment belongs :) Esteban > > On Sat, Aug 12, 2017 at 4:37 PM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > and btw, this kind of threads belongs to pharo-dev, not to pharo-users :) > > Esteban > > > On 12 Aug 2017, at 16:35, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > > > > > >> On 12 Aug 2017, at 12:46, Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: > >> > >> Hi, > >> > >> I would very much like this path. What would constitute tiny? > > > > no idea, we need to think on it :) > > but I see no point in create a new (even small) parser/scanner each time we need one. At the end you have several small parsers that repeat always same process when PetitParser is good for most of our problems (and if you need to improve it. you can always load PP compiler, etc.). > > > > Esteban > > > >> > >> Cheers, > >> Doru > >> > >> > >>> On Aug 11, 2017, at 9:10 PM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > >>> > >>> hi, > >>> > >>>> On 11 Aug 2017, at 18:57, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com <mailto:cyril.ferlicot@gmail.com>> wrote: > >>>> > >>>> Another step would be to get a minimal parser not relying on > >>>> PetitParser. > >>> > >>> Letâs think differently: why not to include a tiny PetitParser? > >>> Then we can think on: > >>> > >>> - pillar sintax (better than just a restricted version) > >>> - simplify other âsmall parsersâ that are already on the image. > >>> - we provide a tool to o cool stuff (instead relying as always in regexp, etc.) > >>> > >>> cheers, > >>> Esteban > >> > >> -- > >> www.tudorgirba.com <http://www.tudorgirba.com/> > >> www.feenk.com <http://www.feenk.com/> > >> > >> "Beauty is where we see it." > >> > >> > >> > >> > >> > > > > > > > > -- > > Guille Polito > > Research Engineer > French National Center for Scientific Research - http://www.cnrs.fr <http://www.cnrs.fr/> > > > Web: http://guillep.github.io <http://guillep.github.io/> > Phone: +33 06 52 70 66 13

Aug. 12, 2017

Re: [Pharo-users] including Pillar in Pharo image by default

by Guillermo Polito

Esteban, I think that when Stef says "a mini version of pillar" he does not mean a mini version of the parser or the AST, but a version that does not have the exporting to html/latex/... On Sat, Aug 12, 2017 at 4:37 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > and btw, this kind of threads belongs to pharo-dev, not to pharo-users :) > > Esteban > > > On 12 Aug 2017, at 16:35, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > > > >> On 12 Aug 2017, at 12:46, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> > >> Hi, > >> > >> I would very much like this path. What would constitute tiny? > > > > no idea, we need to think on it :) > > but I see no point in create a new (even small) parser/scanner each time > we need one. At the end you have several small parsers that repeat always > same process when PetitParser is good for most of our problems (and if you > need to improve it. you can always load PP compiler, etc.). > > > > Esteban > > > >> > >> Cheers, > >> Doru > >> > >> > >>> On Aug 11, 2017, at 9:10 PM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >>> > >>> hi, > >>> > >>>> On 11 Aug 2017, at 18:57, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> > wrote: > >>>> > >>>> Another step would be to get a minimal parser not relying on > >>>> PetitParser. > >>> > >>> Letâs think differently: why not to include a tiny PetitParser? > >>> Then we can think on: > >>> > >>> - pillar sintax (better than just a restricted version) > >>> - simplify other âsmall parsersâ that are already on the image. > >>> - we provide a tool to o cool stuff (instead relying as always in > regexp, etc.) > >>> > >>> cheers, > >>> Esteban > >> > >> -- > >> www.tudorgirba.com > >> www.feenk.com > >> > >> "Beauty is where we see it." > >> > >> > >> > >> > >> > > > > > -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Aug. 12, 2017

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

by Ben Coman

Thanks Esteban. @everyone, please vote & share. cheers -ben On Sat, Aug 12, 2017 at 11:35 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > done: > > https://www.reddit.com/r/programming/comments/6t9242/debugging_lambdas_by_ > rematerializing_saved/ > https://news.ycombinator.com/item?id=14998234 > > Esteban > > On 12 Aug 2017, at 17:26, Ben Coman <btc(a)openinworld.com> wrote: > > hi Tim, > > That is..... AWESOME! > > Very nice delivery - it flowed well with great narration. > > I loved @2:17 "this is the interesting piece, because PharoLambda has > serialized the execution context of its application and saved it into [my > S3 bucket] ... [then on the local machine] rematerializes a debugger [on > that context]." > > There is a clarity in your video presentation that really may intrigue > outsiders. As a community we should push this on the usual hacker forums - > ycombinator could be a good starting point (but I'm locked out of my > account there). > An enticing title could be... > "Debugging Lambdas by re-materializing saved execution contexts on your > local machine." > > cheers -ben > > On Fri, Aug 11, 2017 at 3:37 PM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > >> This is cool Tim. >> >> So what image size you deployed at the end? >> >> 2017-08-10 15:47 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: >> >>> I just wanted to thank everyone for their help in getting my pet project >>> further along, so that now I can announce that PharoLambda is now working >>> with the V7 minimal image and also supports post mortem debugging by saving >>> a zipped fuel context onto S3. >>> >>> This latter item is particularly satisfying as at a recent serverless >>> conference (JeffConf) there was a panel where poor development tools on >>> serverless platforms was highlighted as a real problem. >>> >>> In our community weâve had these kinds of tools at our fingertips for >>> ages - but I donât think the wider development community has really >>> noticed. Debugging something short lived like a Lambda execution is quite >>> startling, as the current answer is âadd more loggingâ, and we all know >>> that sucks. To this end, Iâve created a little screencast showing this in >>> action - and it was pretty cool because it was a real example I encountered >>> when I got everything working and was trying my test application out. >>> >>> Iâve also put a bit of work into tuning the excellent GitLab CI tools, >>> so that I can cache many of the artefacts used between different build runs >>> (this might also be of interest to others using CI systems). >>> >>> The Gitlab project is on: https://gitlab.com/macta/PharoLambda >>> And the screencast: https://www.youtube.com/watch?v=bNNCT1hLA3E >>> >>> Tim >>> >>> >>> On 15 Jul 2017, at 00:39, Tim Mackinnon <tim(a)testit.works> wrote: >>> >>> Hi - Iâve been playing around with getting Pharo to run well on AWS >>> Lambda. Itâs early days, but I though it might be interesting to share what >>> Iâve learned so far. >>> >>> Usage examples and code at https://gitlab.com/macta/PharoLambda >>> >>> With help from many of the folks here, Iâve been able to get a simple >>> example to run in 500ms-1200ms with a minimal Pharo 6 image. You can easily >>> try it out yourself. This seems slightly better than what the GoLang folks >>> have been able to do. >>> >>> Tim >>> >>> >>> >> > >

Aug. 12, 2017

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

by Esteban Lorenzano

done: https://www.reddit.com/r/programming/comments/6t9242/debugging_lambdas_by_r… <https://www.reddit.com/r/programming/comments/6t9242/debugging_lambdas_by_r…> https://news.ycombinator.com/item?id=14998234 <https://news.ycombinator.com/item?id=14998234> Esteban > On 12 Aug 2017, at 17:26, Ben Coman <btc(a)openinworld.com> wrote: > > hi Tim, > > That is..... AWESOME! > > Very nice delivery - it flowed well with great narration. > > I loved @2:17 "this is the interesting piece, because PharoLambda has serialized the execution context of its application and saved it into [my S3 bucket] ... [then on the local machine] rematerializes a debugger [on that context]." > > There is a clarity in your video presentation that really may intrigue outsiders. As a community we should push this on the usual hacker forums - ycombinator could be a good starting point (but I'm locked out of my account there). > An enticing title could be... > "Debugging Lambdas by re-materializing saved execution contexts on your local machine." > > cheers -ben > > On Fri, Aug 11, 2017 at 3:37 PM, Denis Kudriashov <dionisiydk(a)gmail.com <mailto:dionisiydk@gmail.com>> wrote: > This is cool Tim. > > So what image size you deployed at the end? > > 2017-08-10 15:47 GMT+02:00 Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>>: > I just wanted to thank everyone for their help in getting my pet project further along, so that now I can announce that PharoLambda is now working with the V7 minimal image and also supports post mortem debugging by saving a zipped fuel context onto S3. > > This latter item is particularly satisfying as at a recent serverless conference (JeffConf) there was a panel where poor development tools on serverless platforms was highlighted as a real problem. > > In our community weâve had these kinds of tools at our fingertips for ages - but I donât think the wider development community has really noticed. Debugging something short lived like a Lambda execution is quite startling, as the current answer is âadd more loggingâ, and we all know that sucks. To this end, Iâve created a little screencast showing this in action - and it was pretty cool because it was a real example I encountered when I got everything working and was trying my test application out. > > Iâve also put a bit of work into tuning the excellent GitLab CI tools, so that I can cache many of the artefacts used between different build runs (this might also be of interest to others using CI systems). > > The Gitlab project is on: https://gitlab.com/macta/PharoLambda <https://gitlab.com/macta/PharoLambda> > And the screencast: https://www.youtube.com/watch?v=bNNCT1hLA3E <https://www.youtube.com/watch?v=bNNCT1hLA3E> > > Tim > > >> On 15 Jul 2017, at 00:39, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >> >> Hi - Iâve been playing around with getting Pharo to run well on AWS Lambda. Itâs early days, but I though it might be interesting to share what Iâve learned so far. >> >> Usage examples and code at https://gitlab.com/macta/PharoLambda <https://gitlab.com/macta/PharoLambda> >> >> With help from many of the folks here, Iâve been able to get a simple example to run in 500ms-1200ms with a minimal Pharo 6 image. You can easily try it out yourself. This seems slightly better than what the GoLang folks have been able to do. >> >> Tim > > >

Aug. 12, 2017

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

by Ben Coman

hi Tim, That is..... AWESOME! Very nice delivery - it flowed well with great narration. I loved @2:17 "this is the interesting piece, because PharoLambda has serialized the execution context of its application and saved it into [my S3 bucket] ... [then on the local machine] rematerializes a debugger [on that context]." There is a clarity in your video presentation that really may intrigue outsiders. As a community we should push this on the usual hacker forums - ycombinator could be a good starting point (but I'm locked out of my account there). An enticing title could be... "Debugging Lambdas by re-materializing saved execution contexts on your local machine." cheers -ben On Fri, Aug 11, 2017 at 3:37 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > This is cool Tim. > > So what image size you deployed at the end? > > 2017-08-10 15:47 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: > >> I just wanted to thank everyone for their help in getting my pet project >> further along, so that now I can announce that PharoLambda is now working >> with the V7 minimal image and also supports post mortem debugging by saving >> a zipped fuel context onto S3. >> >> This latter item is particularly satisfying as at a recent serverless >> conference (JeffConf) there was a panel where poor development tools on >> serverless platforms was highlighted as a real problem. >> >> In our community weâve had these kinds of tools at our fingertips for >> ages - but I donât think the wider development community has really >> noticed. Debugging something short lived like a Lambda execution is quite >> startling, as the current answer is âadd more loggingâ, and we all know >> that sucks. To this end, Iâve created a little screencast showing this in >> action - and it was pretty cool because it was a real example I encountered >> when I got everything working and was trying my test application out. >> >> Iâve also put a bit of work into tuning the excellent GitLab CI tools, so >> that I can cache many of the artefacts used between different build runs >> (this might also be of interest to others using CI systems). >> >> The Gitlab project is on: https://gitlab.com/macta/PharoLambda >> And the screencast: https://www.youtube.com/watch?v=bNNCT1hLA3E >> >> Tim >> >> >> On 15 Jul 2017, at 00:39, Tim Mackinnon <tim(a)testit.works> wrote: >> >> Hi - Iâve been playing around with getting Pharo to run well on AWS >> Lambda. Itâs early days, but I though it might be interesting to share what >> Iâve learned so far. >> >> Usage examples and code at https://gitlab.com/macta/PharoLambda >> >> With help from many of the folks here, Iâve been able to get a simple >> example to run in 500ms-1200ms with a minimal Pharo 6 image. You can easily >> try it out yourself. This seems slightly better than what the GoLang folks >> have been able to do. >> >> Tim >> >> >> >

Aug. 12, 2017

Re: [Pharo-users] including Pillar in Pharo image by default

by Esteban Lorenzano

and btw, this kind of threads belongs to pharo-dev, not to pharo-users :) Esteban > On 12 Aug 2017, at 16:35, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > >> On 12 Aug 2017, at 12:46, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >> I would very much like this path. What would constitute tiny? > > no idea, we need to think on it :) > but I see no point in create a new (even small) parser/scanner each time we need one. At the end you have several small parsers that repeat always same process when PetitParser is good for most of our problems (and if you need to improve it. you can always load PP compiler, etc.). > > Esteban > >> >> Cheers, >> Doru >> >> >>> On Aug 11, 2017, at 9:10 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>> hi, >>> >>>> On 11 Aug 2017, at 18:57, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: >>>> >>>> Another step would be to get a minimal parser not relying on >>>> PetitParser. >>> >>> Letâs think differently: why not to include a tiny PetitParser? >>> Then we can think on: >>> >>> - pillar sintax (better than just a restricted version) >>> - simplify other âsmall parsersâ that are already on the image. >>> - we provide a tool to o cool stuff (instead relying as always in regexp, etc.) >>> >>> cheers, >>> Esteban >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "Beauty is where we see it." >> >> >> >> >> >

Aug. 12, 2017