February 2018 - Pharo-users

Re: [Pharo-users] PetitParser: Building composed (dependent) parsers and isolating productions code

by Diego Lont

Hi, I have never used dependents (^ (self dependencyAt: StatementBParser) ruleB), but here are my thoughts when reading this. When parsing it makes sense to make a separation between syntax and semantics. Applying this functional distinction in your technical design usually makes sense. In practical terms making a class for the syntax (i.e. StatementASyntax) and one class for the semantics, subclassing the syntax (i.e. StatementASyntax subclass: StatementAParse). So the question here is what class is responsible for the semantics and what class is responsible for the syntax. Depending on the answer on this question you should build your tree. Do you want your statement parsers to know the semantics of the statements as well, then I would suggest separate these in a syntax and a parser (and only having production rules in PLParser for rules that combine things and no production rules when the rule is merely forward them to your statement parser). Or do the statement parsers merely do the syntax, and does the PLParser apply the semantics (maybe because the semantics is context sensitive), the you should not create a duplicate structure in your statement parsers, but have the production rules i the PLParser (or a subclass of PLParser). As to your maintenance nightmare: - I would add a superclass for the syntax, and not a subclass for the semantics. - And maybe you should consider referring to the parser as a resource / factory method, so you only have one reference to each of your statement parsers. PLParser>> ruleB ^ (self dependencyAt: self statementBParser) ruleB PLParser>> statementBParser ^ StatementBParser Regards, Diego > On 01 Feb 2018, at 14:42, Arturo Zambrano <arturo.zambrano(a)gmail.com> wrote: > > Hi All, > Could you please share some advice on the following situation? > I wrote my first Petit Parser. > From the documentation I read that: > 1) it is possible to depend on other parsers making the development more modular. > 2) The docs also suggest that, in order to separate grammars rules from productions, we can make a parser with productions a subclass of a parser which defines the grammar. > > I started applying 1) so my structure is something like > > AbstractParser " contains some common basic elements common to all subclasses) > StatementAParser > StatementBParser > PLParser "this guy uses the StatementX parsers" > > So there is a parser for different statements of the programming language. > The PLParser uses PetitParser dependency mechanism to rely on the Statement*Parsers. For instance: > PLParser>> ruleB > ^ (self dependencyAt: StatementBParser) ruleB > > > So far so good, the grammar is working, the parser works. > > Now, I would like to write the productions, separately from the grammar part (remember 2) ), so I should make subclasses adding the productions in the form > >>ruleA > ^super ruleA ===> [ my production code] > > The point is that PLParser explicitly depends on Statements*Parser, and the name of the Statement*Parser appears here and there, so creating subclasses would result in maintenance nightmare. The new layer of parsers with productions will duplicate the dependencies and I foresee it will be a mess. > > So now, I think that having just one big class with all the rules for the grammar is better if you plan to separate productions code isolated from the grammar. > > Am I right? Maybe I'm missing some point regarding writing composed parsers and separating productions from grammar. > > Any pointer or comment is welcome. > > Arturo >

Feb. 2, 2018

Re: [Pharo-users] Metacello with Git

by Pavel Krivanek

the pull request was against the issue branch, not the development one, so the merging of it had no real effect. I created a new one ( https://github.com/pharo-project/pharo/pull/790) -- Pavel 2018-02-02 9:47 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > yes, I asked Pavel to look at itâ¦ > > Esteban > > > On 2 Feb 2018, at 09:38, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > > I've seen that the other day. The package is in the repository but is not > loaded in the image. Probably somebody committed it but not added it into > any baseline. > > On Fri, Feb 2, 2018 at 4:35 AM, Sean P. DeNigris <sean(a)clipperadams.com> > wrote: > >> An image with build 454 seems still not to have MCGitlabRepository >> present. >> What am I missing? >> Same for build 462 with sha 3641442f3ba0613cd9a6428181487ea29e62418c, >> which >> has the package in its source: >> https://github.com/pharo-project/pharo/tree/3641442f3ba0613c >> d9a6428181487ea29e62418c/src/Metacello-Gitlab >> >> Ditto for build 487.sha.58ee23aadcd15e0a969ed675e8141c0cfd95594a >> >> >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> > > > -- > > Guille Polito > Research Engineer > > > Centre de Recherche en Informatique, Signal et Automatique de Lille > CRIStAL - UMR 9189 > 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 <+33%206%2052%2070%2066%2013> > > >

Feb. 2, 2018

Re: [Pharo-users] Metacello with Git

by Esteban Lorenzano

yes, I asked Pavel to look at itâ¦ Esteban > On 2 Feb 2018, at 09:38, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > I've seen that the other day. The package is in the repository but is not loaded in the image. Probably somebody committed it but not added it into any baseline. > > On Fri, Feb 2, 2018 at 4:35 AM, Sean P. DeNigris <sean(a)clipperadams.com <mailto:sean@clipperadams.com>> wrote: > An image with build 454 seems still not to have MCGitlabRepository present. > What am I missing? > Same for build 462 with sha 3641442f3ba0613cd9a6428181487ea29e62418c, which > has the package in its source: > https://github.com/pharo-project/pharo/tree/3641442f3ba0613cd9a6428181487ea… <https://github.com/pharo-project/pharo/tree/3641442f3ba0613cd9a6428181487ea…> > > Ditto for build 487.sha.58ee23aadcd15e0a969ed675e8141c0cfd95594a > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> > > > > > -- > > Guille Polito > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > CRIStAL - UMR 9189 > 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

Feb. 2, 2018

Re: [Pharo-users] is OSSubProcess working in Pharo 6.1?

by Guillermo Polito

Bah, in fact the tag works well for that purpose :) The problem is that suddenly our builds started to break and the log in the terminal was not clear, leading us to think that it was related to OSSubprocess. But it was related to another dependency ^^. On Thu, Feb 1, 2018 at 9:57 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > Hi Guille, > > On 1 February 2018 at 10:49, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > > Yeh, but loading master will load always a different version. But to > have a > > reproducible build, we would like to load always the same version v0.2.5. > > > If you want a completely reproducible build, you can always specify > the commit id (if there isn't a tag), e.g.: > > > Metacello new > configuration: 'OSSubprocess'; > repository: 'github://marianopeck/OSSubprocess:4c4e76d0/repository'; > load. > > > (I'm not recommending this particular commit, I chose it at random > just to see if it loads, not if it works). > > Cheers, > Alistair > > > > > On Tue, Jan 30, 2018 at 11:47 PM, Alistair Grant <akgrant0710(a)gmail.com> > > wrote: > >> > >> Hi Stef, > >> > >> On 30 January 2018 at 23:13, Stephane Ducasse <stepharo.self(a)gmail.com> > >> wrote: > >> > Hi > >> > > >> > in pillar 70 we have > >> > baseline: spec > >> > <baseline> > >> > spec > >> > for: #common > >> > do: [ spec blessing: #baseline. > >> > spec repository: 'http://smalltalkhub.com/mc/Pier/Pillar/main/'. > >> > spec > >> > baseline: 'OSSubprocess' > >> > with: [ spec > >> > repository: 'github://marianopeck/OSSubprocess:v0.2.5/repository' ]; > >> > baseline: 'Mustache' > >> > with: [ spec > >> > repository: 'github://noha/mustache:v1.0/repository' ]; > >> > project: 'Cocoon' > >> > > >> > but travis reports this: > >> > > >> > > >> > Fetched -> OSSubprocess-cypress.1 --- > >> > github://marianopeck/OSSubprocess:v0.2.5/repository [1d56f81:v0.2.5] > >> > --- github://marianopeck/OSSubprocess:v0.2.5/repository > >> > Fetched -> OSSubprocess-Tests-cypress.1 --- > >> > github://marianopeck/OSSubprocess:v0.2.5/repository [1d56f81:v0.2.5] > >> > --- github://marianopeck/OSSubprocess:v0.2.5/repository > >> > ...RETRY > >> > ...RETRYMessageNotUnderstood: receiver of "withSqueakLineEndings" is > nil > >> > UndefinedObject(Object)>>doesNotUnderstand: #withSqueakLineEndings > >> > MCFileTreeStCypressReader>>addClassAndMethodDefinitionsFromEntry: > >> > > >> > and I do not get why? > >> > > >> > Stef > >> > > >> > >> I use the following to load OSSubProcess in Pharo 7.0 32 bit: > >> > >> Metacello new > >> configuration: 'OSSubprocess'; > >> repository: 'github://marianopeck/OSSubprocess:master/repository'; > >> version: #stable; > >> load. > >> > >> > >> i.e. just replace the "v0.2.5" with "master". > >> > >> HTH, > >> Alistair > >> > > > > > > > > -- > > > > > > > > Guille Polito > > > > Research Engineer > > > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > > > CRIStAL - UMR 9189 > > > > French National Center for Scientific Research - http://www.cnrs.fr > > > > > > Web: http://guillep.github.io > > > > Phone: +33 06 52 70 66 13 > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 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

Feb. 2, 2018

Re: [Pharo-users] Metacello with Git

by Guillermo Polito

I've seen that the other day. The package is in the repository but is not loaded in the image. Probably somebody committed it but not added it into any baseline. On Fri, Feb 2, 2018 at 4:35 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > An image with build 454 seems still not to have MCGitlabRepository present. > What am I missing? > Same for build 462 with sha 3641442f3ba0613cd9a6428181487ea29e62418c, > which > has the package in its source: > https://github.com/pharo-project/pharo/tree/3641442f3ba0613cd9a6428181487e > a29e62418c/src/Metacello-Gitlab > > Ditto for build 487.sha.58ee23aadcd15e0a969ed675e8141c0cfd95594a > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 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

Feb. 2, 2018

Re: [Pharo-users] How can a Morph display a context menu on a mouse click?

by Stephan Eggermont

Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > Letâs say that we have a StringMorph: âHello' asMorph. > Can I attach a MenuMorph (or a menu building logic) and display the > context menu on a mouse click in the StringMorph? > > Or the only way to do it is to subclass the StringMorph and write the > logic in the #mouseDown: method? #when:send:to:, or replace the eventhandler, or subclass Stephan

Feb. 2, 2018

Re: [Pharo-users] Metacello with Git

by Sean P. DeNigris

An image with build 454 seems still not to have MCGitlabRepository present. What am I missing? Same for build 462 with sha 3641442f3ba0613cd9a6428181487ea29e62418c, which has the package in its source: https://github.com/pharo-project/pharo/tree/3641442f3ba0613cd9a6428181487ea… Ditto for build 487.sha.58ee23aadcd15e0a969ed675e8141c0cfd95594a ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 2, 2018

Re: [Pharo-users] is OSSubProcess working in Pharo 6.1?

by Alistair Grant

Hi Guille, On 1 February 2018 at 10:49, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Yeh, but loading master will load always a different version. But to have a > reproducible build, we would like to load always the same version v0.2.5. If you want a completely reproducible build, you can always specify the commit id (if there isn't a tag), e.g.: Metacello new configuration: 'OSSubprocess'; repository: 'github://marianopeck/OSSubprocess:4c4e76d0/repository'; load. (I'm not recommending this particular commit, I chose it at random just to see if it loads, not if it works). Cheers, Alistair > On Tue, Jan 30, 2018 at 11:47 PM, Alistair Grant <akgrant0710(a)gmail.com> > wrote: >> >> Hi Stef, >> >> On 30 January 2018 at 23:13, Stephane Ducasse <stepharo.self(a)gmail.com> >> wrote: >> > Hi >> > >> > in pillar 70 we have >> > baseline: spec >> > <baseline> >> > spec >> > for: #common >> > do: [ spec blessing: #baseline. >> > spec repository: 'http://smalltalkhub.com/mc/Pier/Pillar/main/'. >> > spec >> > baseline: 'OSSubprocess' >> > with: [ spec >> > repository: 'github://marianopeck/OSSubprocess:v0.2.5/repository' ]; >> > baseline: 'Mustache' >> > with: [ spec >> > repository: 'github://noha/mustache:v1.0/repository' ]; >> > project: 'Cocoon' >> > >> > but travis reports this: >> > >> > >> > Fetched -> OSSubprocess-cypress.1 --- >> > github://marianopeck/OSSubprocess:v0.2.5/repository [1d56f81:v0.2.5] >> > --- github://marianopeck/OSSubprocess:v0.2.5/repository >> > Fetched -> OSSubprocess-Tests-cypress.1 --- >> > github://marianopeck/OSSubprocess:v0.2.5/repository [1d56f81:v0.2.5] >> > --- github://marianopeck/OSSubprocess:v0.2.5/repository >> > ...RETRY >> > ...RETRYMessageNotUnderstood: receiver of "withSqueakLineEndings" is nil >> > UndefinedObject(Object)>>doesNotUnderstand: #withSqueakLineEndings >> > MCFileTreeStCypressReader>>addClassAndMethodDefinitionsFromEntry: >> > >> > and I do not get why? >> > >> > Stef >> > >> >> I use the following to load OSSubProcess in Pharo 7.0 32 bit: >> >> Metacello new >> configuration: 'OSSubprocess'; >> repository: 'github://marianopeck/OSSubprocess:master/repository'; >> version: #stable; >> load. >> >> >> i.e. just replace the "v0.2.5" with "master". >> >> HTH, >> Alistair >> > > > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - http://www.cnrs.fr > > > Web: http://guillep.github.io > > Phone: +33 06 52 70 66 13

Feb. 1, 2018

How can a Morph display a context menu on a mouse click?

by Juraj Kubelka

Hi, Letâs say that we have a StringMorph: âHello' asMorph. Can I attach a MenuMorph (or a menu building logic) and display the context menu on a mouse click in the StringMorph? Or the only way to do it is to subclass the StringMorph and write the logic in the #mouseDown: method? Thanks! Juraj

Feb. 1, 2018

Re: [Pharo-users] New booklets organisation and new booklet

by Offray Vladimir Luna CÃ¡rdenas

Hi, On 30/01/18 11:36, Ben Coman wrote: > On 30 January 2018 at 15:54, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> Now I wonder if it makes sense to have all the docs of drGeo here. I >> can do it but I'm thinking about it. >> May be I could create another category. > Perhaps a category named "Applications" or "Libraries" I agree with Ben. On the "Applications" front, showing a healthy ecosystem with proper documentation could be useful. Pharo seems too oriented towards programmers and can provide a lot to people outside this particular field. > >> I "read" your handbook and I >> do not think that it should be listed among the pharo books. >> Now what I would love to have is a handbook: Pharo for the Data >> Journalist. Do you have something like that? We have Grafoscopio interactive notebooks used for our Data Week, on topics like data activism and digital citizenship, but they are complementary material to a intense hackathon alike face to face meeting, so they're not ready as stand alone material. But we will be doing other publications talking about "technologies for autonomy", including Indie Web and Pocket Infrastructures. Grafoscopio and Pharo will be enablers of such publications and technologies, but we want to use a diverse ecosystem of tools beyond Pharo. Once I have such prototypes and books/booklets, I will share them back with this community. Cheers, Offray

Feb. 1, 2018