Re: [Pharo-users] Metacello with Git

[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 
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
*


*Web:* *http://guillep.github.io* 

*Phone: *+33 06 52 70 66 13

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

[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 
wrote:

> Hi Guille,
>
> On 1 February 2018 at 10:49, Guillermo Polito 
> 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 
> > wrote:
> >>
> >> Hi Stef,
> >>
> >> On 30 January 2018 at 23:13, Stephane Ducasse 
> >> wrote:
> >> > Hi
> >> >
> >> > in pillar 70 we have
> >> > baseline: spec
> >> > 
> >> > 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
*


*Web:* *http://guillep.github.io* 

*Phone: *+33 06 52 70 66 13

Re: [Pharo-users] Metacello with Git

[Esteban Lorenzano]

yes, I asked Pavel to look at it…

Esteban

> On 2 Feb 2018, at 09:38, Guillermo Polito  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  > 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/3641442f3ba0613cd9a6428181487ea29e62418c/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 
> 
> 
> Web: http://guillep.github.io 
> Phone: +33 06 52 70 66 13

Re: [Pharo-users] Metacello with Git

[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 :

> yes, I asked Pavel to look at it…
>
> Esteban
>
>
> On 2 Feb 2018, at 09:38, Guillermo Polito 
> 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 
> 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
> *
>
> *Web:* *http://guillep.github.io* 
> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>
>
>
>

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

[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  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
> 

Re: [Pharo-users] Metacello with Git

[Esteban Lorenzano]

thanks!

> On 2 Feb 2018, at 10:12, Pavel Krivanek  wrote:
> 
> 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  >:
> yes, I asked Pavel to look at it…
> 
> Esteban
> 
> 
>> On 2 Feb 2018, at 09:38, Guillermo Polito > > 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 > > 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/3641442f3ba0613cd9a6428181487ea29e62418c/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 
>> 
>> 
>> Web: http://guillep.github.io 
>> Phone: +33 06 52 70 66 13 
> 

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

[Stephan Eggermont]

Guillermo Polito 
wrote:
> 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 ^^.

Well yes, and depending on tags instead of branches is still going to give
you reproducible brittle builds and dependency problems. 

Stephan

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

[Stephane Ducasse]

We will have a journalist visiting us and I would like to show her
roassal and show her your work :)


On Thu, Feb 1, 2018 at 7:54 PM, Offray Vladimir Luna Cárdenas
 wrote:
> Hi,
>
>
> On 30/01/18 11:36, Ben Coman wrote:
>> On 30 January 2018 at 15:54, Stephane Ducasse  
>> 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
>
>

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

[Hernán Morales Durand]

Hi,

One can make money by writing a Pharo-related book?
It takes a significant amount of effort to write a book, you know
better of course.

Is there a plan for monetization so people maybe gets more motivated
to write Pharo material?

Cheers,

Hernán



2018-01-27 16:55 GMT-03:00 Stephane Ducasse :
> Hi
>
> We reorganised the books.pharo.org web site to make the distinction
> between technology and teaching oriented booklet.
> We will have specific covers soon and print available on lulu.
>
> In addition we got the new booklet from C. Bera that explains Call
> Stack Management.
>
>  http://books.pharo.org
>
> Stef
>

Re: [Pharo-users] [ANN] Updating Consultants Listing

[Marcus Denker]

> On 17 Jan 2018, at 17:27, Marcus Denker  wrote:
> 
> Hi,
> 
> We have http://consultants.pharo.org  
> 
> I want to change it to
>   - not be a forward to files.pharo.org 
DONE:

http://consultants.pharo.org 


TBD:
>   - be auto-generated from the https://association.pharo.org 
> 
>  


Marcus

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

[Juraj Kubelka]

Thank you Stephan!

There is my exercise: 

“when:send:to"
morph := 'Hello' asMorph.
morph when: #click send: #traceCr: to: morph.
morph openInWindow.

—> it does not work for me. I do not know what the announcement should be

"Handler"
morph := 'Hello' asMorph.
morph eventHandler: MorphicEventHandler new.
morph eventHandler
on: #click send: #traceCr: to: morph.
morph openInWindow.

—> It works and there are examples in MorphicEventHandlerTest

Thanks!

> El 02-02-2018, a las 03:43, Stephan Eggermont  escribió:
> 
> Juraj Kubelka 
> 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
> 
> 
> 

[Pharo-users] global exception handler mechanism

[Peter Uhnák]

Hi,

is there a way to install a global handler for exceptions?

Right now if I want to log all exceptions, I use approach from ShoreLine
and create a PreDebugAction which is activated when any "unhandled"
exception occurs.

That would be good enough, however the Debugger has zero knowledge of the
exception that is actually occuring, as Exception>>debug passes on only the
title. So if I want to get back to the original exception and maybe log it
with beacon, I need to do a lot of stack and context shenanigans:

MyPreDebugAction>>logException
MyLogger
runDuring: [ (debugger session interruptedProcess suspendedContext stack
detect: [ :context | context receiver isKindOf: Exception ]) receiver emit ]


Is there a better way to approach this?

Thanks,
Peter

[Pharo-users] From Roassal RTView to html

[Andrei Stebakov]

I was wondering if it's a good idea to expose some of the Roassal models
via web (say Seaside) using the ability of Roassal to generate HTML for the
view.
In this case how could I "spice up" the HTML making for example those
ellipces or lablels clickabe so the click could take me to some web page
bases on the data in the model?

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

[Stephane Ducasse]

On Fri, Feb 2, 2018 at 2:05 PM, Hernán Morales Durand
 wrote:
> Hi,
>
> One can make money by writing a Pharo-related book?

Since most of the books I wrote are free I did not earn much.
Most of the time if ESUG would not sponsor I would earn 200 Euros max.


Now the association could sponsor book too.
We could also create a bounty for booklets.
I would love to read books or booklets written by others and I'm ready
to pay for it.
I would like to read a book on IA, Bloc, And many topics in fact.

> It takes a significant amount of effort to write a book, you know
> better of course.
>
> Is there a plan for monetization so people maybe gets more motivated
> to write Pharo material?

I'm planning to make my last book on lulu (it is there but I'm waiting
for the first printout)
and to offer a good reduction to the association members.

Stef
>
> Cheers,
>
> Hernán
>

Re: [Pharo-users] Metacello with Git

[Sean P. DeNigris]

Pavel Krivanek-3 wrote
> the pull request was against the issue branch, not the development one, so
> the merging of it had no real effect

Oops, he he thanks.



-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

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

[Hernán Morales Durand]

Hi Stef,

2018-02-02 16:16 GMT-03:00 Stephane Ducasse :
> On Fri, Feb 2, 2018 at 2:05 PM, Hernán Morales Durand
>  wrote:
>> Hi,
>>
>> One can make money by writing a Pharo-related book?
>
> Since most of the books I wrote are free I did not earn much.
> Most of the time if ESUG would not sponsor I would earn 200 Euros max.
>

Ok, please note that 200 euros is about half of the minimum salary at
least here:

http://www.xe.com/currencyconverter/convert/?Amount=200&From=EUR&To=ARS
https://es.wikipedia.org/wiki/Anexo:Salario_m%C3%ADnimo_en_Argentina

And the min salary is an absolute crap.
Yes, that's how bad it is.

>
> Now the association could sponsor book too.
> We could also create a bounty for booklets.
> I would love to read books or booklets written by others and I'm ready
> to pay for it.
> I would like to read a book on IA, Bloc, And many topics in fact.
>
>> It takes a significant amount of effort to write a book, you know
>> better of course.
>>
>> Is there a plan for monetization so people maybe gets more motivated
>> to write Pharo material?
>
> I'm planning to make my last book on lulu (it is there but I'm waiting
> for the first printout)
> and to offer a good reduction to the association members.
>
> Stef

Thank you for the reply.

Let me know if you'd like to add a bioinformatics or geographic
information retrieval chapter. I wrote the chapters in Markdown for
pandoc but I can convert them to Pillar once it's ready for Windows.

Cheers,

Hernán

>>
>> Cheers,
>>
>> Hernán
>>
>