December 2014 - Pharo-users

Pharo by Example updated: Metaclass chapter

by stepharo

Hi guys I just finished to revisit the metaclass chapter for Pharo by Example based on Pharo 40. Stef

Dec. 31, 2014

Re: [Pharo-users] Traveling from Pharo Days to FOSDEM

by FranÃ§ois Stephany

With the high speed train "Lille Europe" to "Brussels South" takes around 40 minutes. You can check fares and book tickets on https://www.b-europe.com @Phil do you go back to Brussels from Lille on Friday night? On Wed, Dec 31, 2014 at 1:37 PM, Rafael Luque <rafael.luque.leiva(a)gmail.com> wrote: > Hi Pharoers, > > I will attend Pharo Days with a friend and after the conference we'd like > to attend FOSDEM. Which the best way to travel to Brussels from Lille? > > Thank you and see you in Pharo Days. >

Dec. 31, 2014

Re: [Pharo-users] PetitParser and PPBrowser in Pharo 3.0

by Tudor Girba

Ahh, it should have been: #GTImageSetupCommandLineHandler asClass *new* installFonts Doru On Wed, Dec 31, 2014 at 3:08 PM, Hartmut <krasemann(a)acm.org> wrote: > Hi Doru, > > Thanks for such a quick response. > > I had to change the fonts for Default AND for Button to a TrueTypeFont. > > PPBrowser now works for me, thanks. > > Hartmut > PS: After loading the script from 'GTToolkit' activateWithoutSaving was > still unknown > > Am 31.12.14 14:14, schrieb Tudor Girba: > > Hi, > > PPBrowser uses Roassal which relies on the Athens canvas which requires > FreeType fonts :). > > To fix this, you can go to Settings: > - Make Use Free type ... true > - Choose a Free type font as the default one. > > Or you can just use the Moose 5.0 image: > http://moosetechnology.org/#install > > Or you can use some ready made setup script we have in Moose: > Gofer new > smalltalkhubUser: 'Moose' project: 'GToolkit'; > package: 'GT-Setup'; > load. > #GTImageSetupCommandLineHandler asClass activateWithoutSaving > > Cheers, > Doru > > > > On Wed, Dec 31, 2014 at 2:10 PM, Hartmut <krasemann(a)acm.org> wrote: > >> Hi Jan, >> >> since a while I get a MessageNotUnderstood on PPBrowser open after >> ConfigurationOfPetitParser loadDevelopment. >> Has to do with fonts. >> Debugger Stack fueled out can be accessed here: >> https://dl.dropboxusercontent.com/u/4548797/Debugger-Stack-StrikeFont-2014-… >> >> Regards, Hartmut >> >> Am 16.12.14 14:34, schrieb Jan KurÅ¡: >> >> Hi, >> >> Anyone experience with Athens can help with the first issue? >> TRLabelShape>>drawOn: seem to be somehow responsible, but I don't see into >> this :( >> >> Regarding to the second issue, there are some cases, when one really >> needs a start rule, e.g when computing follow. Yet I updated the code so >> that it handles missing start rule a bit better. >> >> Please, let me know, if you have some other ideas/suggestions/issues. >> >> Regards, >> Jan >> >> On 9 December 2014 at 15:17, Hartmut <krasemann(a)acm.org> wrote: >>> >>> Hi to all, >>> >>> I'm working with PetitParser in a Pharo 3 image. >>> Until now I had to do without the PPBrowser which I loved in Pharo 2. >>> >>> On forum.world.st I now found the hint by Jan Kurs to install all of >>> the Petit suite: >>> >>> > "Configuration should be loaded like this:" >>> > Gofer new smalltalkhubUser: 'Moose' project: 'PetitParser'; >>> > configurationOf: #PetitParser; load. >>> > >>> > "All the petit parser suite:" >>> > ConfigurationOfPetitParser loadDevelopment. >>> >>> Apart from the fact that this installed a real lot into my image, I >>> notice the following problems >>> in PPBrowser: >>> >>> 1. The map of none of the 18 parsers included, is displayed (it becomes >>> red crossed). >>> However, this was the most useful part of it >>> >>> 2. My interrelated parsers consist of a tree of parsers where each leave >>> has its own start clause. >>> They define related languages. It makes no sense to add a *start* >>> clause to the root. >>> However, without such a meaningless *start* clause, only the >>> *source* is displayed, >>> neither *graph, example, first* or *follow* of any clause. >>> (this can be reproduced when you move PPJsonGrammar>>start to >>> PPJsonParser) >>> >>> I like the style of having a grammar class above a parser (or compiler) >>> class. >>> This is as seen in most of the accompanying parsers. >>> My preferred petit parser style comprises: >>> a) keeping grammar rules (without ==>) in the upper classes of the >>> grammar hierarchy tree, >>> such that we find the complete grammar there (without the *start* >>> clause). >>> b) keeping replacement rules (using ==>) as low as possible the >>> grammar hierarchy tree >>> c) writing the start clause to the class that is actually called. >>> (this gives different entries >>> in a grammar allowing for different languages with grammar >>> subsets) >>> >>> Is there an idea to have 1. and/or 2. resolved? >>> >>> Hartmut >>> >>> -- >>> Hartmut Krasemann >>> KÃ¶nigsberger Str. 41 c >>> â¨D 22869 Schenefeld >>> Tel. 040.8307097 >>> Mobil 0171.6451283â¨krasemann(a)acm.org >>> >>> >> -- >> Hartmut Krasemann >> KÃ¶nigsberger Str. 41 c >> â¨D 22869 Schenefeld >> Tel. 040.8307097 >> Mobil 0171.6451283â¨krasemann(a)acm.org >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > -- > Hartmut Krasemann > KÃ¶nigsberger Str. 41 c > â¨D 22869 Schenefeld > Tel. 040.8307097 > Mobil 0171.6451283â¨krasemann(a)acm.org > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 31, 2014

Re: [Pharo-users] PetitParser problem with plus

by Jan KurÅ¡

You mean deep into pharo? Or something else? I can do this... On 21 December 2014 at 13:27, stepharo <stepharo(a)free.fr> wrote: > Could one of you write a small paragraph for the petit parser chapter? > > Le 18/12/14 09:07, Jan KurÅ¡ a Ã©crit : > > Exactly... > > This happens so often that we should add some warning somewhere in these > cases.... > > > Cheers, > Jan > > On 18 December 2014 at 08:36, Guillaume Larcheveque < > guillaume.larcheveque(a)gmail.com> wrote: >> >> So you just have to remove the #star in notA or replace it by #plus to >> makes it succeed only when it consume at least one character >> >> 2014-12-18 7:54 GMT+01:00 Guillaume Larcheveque < >> guillaume.larcheveque(a)gmail.com>: >>> >>> With x, x it will only go to 2 level deep. >>> >>> With the plus you allow to go as far as the x rule succeed and your x >>> rule always succeed because notA always succeed due to the star without >>> consuming anything so you fall into infinite loop. >>> >>> 2014-12-18 6:47 GMT+01:00 James Foster <Smalltalk(a)jgfoster.net>: >>>> >>>> There is something about plus that I donât understand. In the following >>>> code if I parse for (x , x) then I get what I expect. If I parse for (x >>>> plus) then the image hangs. What am I doing wrong? >>>> >>>> James >>>> >>>> | a notA x y | >>>> a := $a asParser. >>>> notA := $a asParser negate star flatten. >>>> x := a / notA. >>>> y := x , x. âworks fineâ >>>> y := x plus. ânever finishesâ >>>> ^y end parse: 'abâ. >>>> >>>> >>>> >>> >>> -- >>> *Guillaume Larcheveque* >>> >>> >> >> -- >> *Guillaume Larcheveque* >> >> >

Dec. 31, 2014

Re: [Pharo-users] Traveling from Pharo Days to FOSDEM

by phil＠highoctane.be

I go back to Brussels by car. I can take 2-3 persons with me. I also go to FOSDEM. Phil Le 31 dÃ©c. 2014 13:37, "Rafael Luque" <rafael.luque.leiva(a)gmail.com> a Ã©crit : > > Hi Pharoers, > > I will attend Pharo Days with a friend and after the conference we'd like to attend FOSDEM. Which the best way to travel to Brussels from Lille? > > Thank you and see you in Pharo Days.

Dec. 31, 2014

Re: [Pharo-users] PetitParser and PPBrowser in Pharo 3.0

by Hartmut

Hi Doru, Thanks for such a quick response. I had to change the fonts for Default AND for Button to a TrueTypeFont. PPBrowser now works for me, thanks. Hartmut PS: After loading the script from 'GTToolkit' activateWithoutSaving was still unknown Am 31.12.14 14:14, schrieb Tudor Girba: > Hi, > > PPBrowser uses Roassal which relies on the Athens canvas which > requires FreeType fonts :). > > To fix this, you can go to Settings: > - Make Use Free type ... true > - Choose a Free type font as the default one. > > Or you can just use the Moose 5.0 image: > http://moosetechnology.org/#install > > Or you can use some ready made setup script we have in Moose: > Gofer new > smalltalkhubUser: 'Moose' project: 'GToolkit'; > package: 'GT-Setup'; > load. > #GTImageSetupCommandLineHandler asClass activateWithoutSaving > > Cheers, > Doru > > > > On Wed, Dec 31, 2014 at 2:10 PM, Hartmut <krasemann(a)acm.org > <mailto:krasemann@acm.org>> wrote: > > Hi Jan, > > since a while I get a MessageNotUnderstood on PPBrowser open after > ConfigurationOfPetitParser loadDevelopment. > Has to do with fonts. > Debugger Stack fueled out can be accessed here: > https://dl.dropboxusercontent.com/u/4548797/Debugger-Stack-StrikeFont-2014-… > > Regards, Hartmut > > Am 16.12.14 14:34, schrieb Jan KurÅ¡: >> Hi, >> >> Anyone experience with Athens can help with the first issue? >> TRLabelShape>>drawOn: seem to be somehow responsible, but I don't >> see into this :( >> >> Regarding to the second issue, there are some cases, when one >> really needs a start rule, e.g when computing follow. Yet I >> updated the code so that it handles missing start rule a bit better. >> >> Please, let me know, if you have some other ideas/suggestions/issues. >> >> Regards, >> Jan >> >> On 9 December 2014 at 15:17, Hartmut <krasemann(a)acm.org >> <mailto:krasemann@acm.org>> wrote: >> >> Hi to all, >> >> I'm working with PetitParser in a Pharo 3 image. >> Until now I had to do without the PPBrowser which I loved in >> Pharo 2. >> >> On forum.world.st <http://forum.world.st> I now found the >> hint by Jan Kurs to install all of the Petit suite: >> >> > "Configuration should be loaded like this:" >> > Gofer new smalltalkhubUser: 'Moose' project: 'PetitParser'; >> > configurationOf: #PetitParser; load. >> > >> > "All the petit parser suite:" >> > ConfigurationOfPetitParser loadDevelopment. >> >> Apart from the fact that this installed a real lot into my >> image, I notice the following problems >> in PPBrowser: >> >> 1. The map of none of the 18 parsers included, is displayed >> (it becomes red crossed). >> However, this was the most useful part of it >> >> 2. My interrelated parsers consist of a tree of parsers where >> each leave has its own start clause. >> They define related languages. It makes no sense to add a >> /start/ clause to the root. >> However, without such a meaningless /start/ clause, only >> the /source/ is displayed, >> neither /graph, example, first/ or /follow/ of any clause. >> (this can be reproduced when you move >> PPJsonGrammar>>start to PPJsonParser) >> >> I like the style of having a grammar class above a parser (or >> compiler) class. >> This is as seen in most of the accompanying parsers. >> My preferred petit parser style comprises: >> a) keeping grammar rules (without ==>) in the upper >> classes of the grammar hierarchy tree, >> such that we find the complete grammar there (without >> the /start/ clause). >> b) keeping replacement rules (using ==>) as low as >> possible the grammar hierarchy tree >> c) writing the start clause to the class that is actually >> called. (this gives different entries >> in a grammar allowing for different languages with >> grammar subsets) >> >> Is there an idea to have 1. and/or 2. resolved? >> >> Hartmut >> >> -- >> Hartmut Krasemannâ¨ >> KÃ¶nigsberger Str. 41 c >> â¨D 22869 Schenefeldâ¨ >> Tel. 040.8307097â¨ >> Mobil 0171.6451283â¨ >> krasemann(a)acm.org <mailto:krasemann@acm.org> >> > > -- > Hartmut Krasemannâ¨ > KÃ¶nigsberger Str. 41 c > â¨D 22869 Schenefeldâ¨ > Tel. 040.8307097â¨ > Mobil 0171.6451283â¨ > krasemann(a)acm.org <mailto:krasemann@acm.org> > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow" -- Hartmut Krasemannâ¨ KÃ¶nigsberger Str. 41 c â¨D 22869 Schenefeldâ¨ Tel. 040.8307097â¨ Mobil 0171.6451283â¨ krasemann(a)acm.org

Dec. 31, 2014

Re: [Pharo-users] PetitParser and PPBrowser in Pharo 3.0

by Tudor Girba

Hi, PPBrowser uses Roassal which relies on the Athens canvas which requires FreeType fonts :). To fix this, you can go to Settings: - Make Use Free type ... true - Choose a Free type font as the default one. Or you can just use the Moose 5.0 image: http://moosetechnology.org/#install Or you can use some ready made setup script we have in Moose: Gofer new smalltalkhubUser: 'Moose' project: 'GToolkit'; package: 'GT-Setup'; load. #GTImageSetupCommandLineHandler asClass activateWithoutSaving Cheers, Doru On Wed, Dec 31, 2014 at 2:10 PM, Hartmut <krasemann(a)acm.org> wrote: > Hi Jan, > > since a while I get a MessageNotUnderstood on PPBrowser open after > ConfigurationOfPetitParser loadDevelopment. > Has to do with fonts. > Debugger Stack fueled out can be accessed here: > https://dl.dropboxusercontent.com/u/4548797/Debugger-Stack-StrikeFont-2014-… > > Regards, Hartmut > > Am 16.12.14 14:34, schrieb Jan KurÅ¡: > > Hi, > > Anyone experience with Athens can help with the first issue? > TRLabelShape>>drawOn: seem to be somehow responsible, but I don't see into > this :( > > Regarding to the second issue, there are some cases, when one really > needs a start rule, e.g when computing follow. Yet I updated the code so > that it handles missing start rule a bit better. > > Please, let me know, if you have some other ideas/suggestions/issues. > > Regards, > Jan > > On 9 December 2014 at 15:17, Hartmut <krasemann(a)acm.org> wrote: >> >> Hi to all, >> >> I'm working with PetitParser in a Pharo 3 image. >> Until now I had to do without the PPBrowser which I loved in Pharo 2. >> >> On forum.world.st I now found the hint by Jan Kurs to install all of the >> Petit suite: >> >> > "Configuration should be loaded like this:" >> > Gofer new smalltalkhubUser: 'Moose' project: 'PetitParser'; >> > configurationOf: #PetitParser; load. >> > >> > "All the petit parser suite:" >> > ConfigurationOfPetitParser loadDevelopment. >> >> Apart from the fact that this installed a real lot into my image, I >> notice the following problems >> in PPBrowser: >> >> 1. The map of none of the 18 parsers included, is displayed (it becomes >> red crossed). >> However, this was the most useful part of it >> >> 2. My interrelated parsers consist of a tree of parsers where each leave >> has its own start clause. >> They define related languages. It makes no sense to add a *start* >> clause to the root. >> However, without such a meaningless *start* clause, only the *source* >> is displayed, >> neither *graph, example, first* or *follow* of any clause. >> (this can be reproduced when you move PPJsonGrammar>>start to >> PPJsonParser) >> >> I like the style of having a grammar class above a parser (or compiler) >> class. >> This is as seen in most of the accompanying parsers. >> My preferred petit parser style comprises: >> a) keeping grammar rules (without ==>) in the upper classes of the >> grammar hierarchy tree, >> such that we find the complete grammar there (without the *start* >> clause). >> b) keeping replacement rules (using ==>) as low as possible the >> grammar hierarchy tree >> c) writing the start clause to the class that is actually called. >> (this gives different entries >> in a grammar allowing for different languages with grammar subsets) >> >> Is there an idea to have 1. and/or 2. resolved? >> >> Hartmut >> >> -- >> Hartmut Krasemann >> KÃ¶nigsberger Str. 41 c >> â¨D 22869 Schenefeld >> Tel. 040.8307097 >> Mobil 0171.6451283â¨krasemann(a)acm.org >> >> > -- > Hartmut Krasemann > KÃ¶nigsberger Str. 41 c > â¨D 22869 Schenefeld > Tel. 040.8307097 > Mobil 0171.6451283â¨krasemann(a)acm.org > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 31, 2014

Re: [Pharo-users] PetitParser and PPBrowser in Pharo 3.0

by Hartmut

Hi Jan, since a while I get a MessageNotUnderstood on PPBrowser open after ConfigurationOfPetitParser loadDevelopment. Has to do with fonts. Debugger Stack fueled out can be accessed here: https://dl.dropboxusercontent.com/u/4548797/Debugger-Stack-StrikeFont-2014-… Regards, Hartmut Am 16.12.14 14:34, schrieb Jan KurÅ¡: > Hi, > > Anyone experience with Athens can help with the first issue? > TRLabelShape>>drawOn: seem to be somehow responsible, but I don't see > into this :( > > Regarding to the second issue, there are some cases, when one really > needs a start rule, e.g when computing follow. Yet I updated the code > so that it handles missing start rule a bit better. > > Please, let me know, if you have some other ideas/suggestions/issues. > > Regards, > Jan > > On 9 December 2014 at 15:17, Hartmut <krasemann(a)acm.org > <mailto:krasemann@acm.org>> wrote: > > Hi to all, > > I'm working with PetitParser in a Pharo 3 image. > Until now I had to do without the PPBrowser which I loved in Pharo 2. > > On forum.world.st <http://forum.world.st> I now found the hint by > Jan Kurs to install all of the Petit suite: > > > "Configuration should be loaded like this:" > > Gofer new smalltalkhubUser: 'Moose' project: 'PetitParser'; > > configurationOf: #PetitParser; load. > > > > "All the petit parser suite:" > > ConfigurationOfPetitParser loadDevelopment. > > Apart from the fact that this installed a real lot into my image, > I notice the following problems > in PPBrowser: > > 1. The map of none of the 18 parsers included, is displayed (it > becomes red crossed). > However, this was the most useful part of it > > 2. My interrelated parsers consist of a tree of parsers where each > leave has its own start clause. > They define related languages. It makes no sense to add a > /start/ clause to the root. > However, without such a meaningless /start/ clause, only the > /source/ is displayed, > neither /graph, example, first/ or /follow/ of any clause. > (this can be reproduced when you move PPJsonGrammar>>start to > PPJsonParser) > > I like the style of having a grammar class above a parser (or > compiler) class. > This is as seen in most of the accompanying parsers. > My preferred petit parser style comprises: > a) keeping grammar rules (without ==>) in the upper classes of > the grammar hierarchy tree, > such that we find the complete grammar there (without the > /start/ clause). > b) keeping replacement rules (using ==>) as low as possible the > grammar hierarchy tree > c) writing the start clause to the class that is actually > called. (this gives different entries > in a grammar allowing for different languages with grammar > subsets) > > Is there an idea to have 1. and/or 2. resolved? > > Hartmut > > -- > Hartmut Krasemannâ¨ > KÃ¶nigsberger Str. 41 c > â¨D 22869 Schenefeldâ¨ > Tel. 040.8307097â¨ > Mobil 0171.6451283â¨ > krasemann(a)acm.org <mailto:krasemann@acm.org> > -- Hartmut Krasemannâ¨ KÃ¶nigsberger Str. 41 c â¨D 22869 Schenefeldâ¨ Tel. 040.8307097â¨ Mobil 0171.6451283â¨ krasemann(a)acm.org

Dec. 31, 2014

Traveling from Pharo Days to FOSDEM

by Rafael Luque

Hi Pharoers, I will attend Pharo Days with a friend and after the conference we'd like to attend FOSDEM. Which the best way to travel to Brussels from Lille? Thank you and see you in Pharo Days.

Dec. 31, 2014

Re: [Pharo-users] pharo at google code-in

by stepharo

Created jenkins job to produce the PDFs I just realized that I lost some of my edits in the Spec chapter. https://ci.inria.fr/pharo-contribution/job/PharoBookWorkInProgress/ws/ https://ci.inria.fr/pharo-contribution/job/PharoBookWorkInProgress/1/artifa… Stef

Dec. 31, 2014