February 2014 - Pharo-users

Re: [Pharo-users] Which one should I download?
by Stephan Eggermont Feb. 26, 2014

Feb. 26, 2014

Robert, Iâve looked at your log. You are using an old VM. (288) Please retry with a newer one (stable/latest) Stephan

1 0

Re: [Pharo-users] Moose: Problem in Petit Parser
by Damien Cassou Feb. 25, 2014

Feb. 25, 2014

On Mon, Feb 24, 2014 at 6:01 PM, PBK Research <peter(a)pbkresearch.co.uk> wrote: > but I shall take good care to read everything I can find before > raising queries. asking question is not a problem, please continue, even if you believe the answer is somewhere already. Don't hesitate to use stackoverflow (tag #pharo) for your questions instead of the mailing list. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

1 0

[Pharo Consortium] New Sponsor: Object Profile
by Marcus Denker Feb. 25, 2014

Feb. 25, 2014

The Pharo Consortium is very happy to announce that Object Profile is supporting the Pharo Consortium as a Sponsor. More about - Object Profile: http://objectprofile.com - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: http://association.pharo.org ==== ( This actually happened some weeks ago alreadyâ¦ sorry for the late announce. There is already another member listed (to be announced) and yet another will be added soon. In addition, we are nearly finished with setting up the infrastructure for the consortium membersâ¦ so if you are one of those and wonder: Soon (as in: this week). Sorry for the delay! )

2 1

The new versionner is cool
by Usman Bhatti Feb. 25, 2014

Feb. 25, 2014

Hello, I found Versionner very productive tool. I was able to create a new configuration "from scratch" within a few minutes with the packages that I wanted to put into it. Though, I couldn't commit my new config through its interface because Komitter kept asking for a issue number but I didn't have it. So, it is excellent to have such a tool in Pharo. Great work guys. regards, Usman

2 2

collecting Pharo Youtube videos...
by Marcus Denker Feb. 24, 2014

Feb. 24, 2014

Hi, There are a lot of videos on youtube about pharoâ¦ from conferences, demos, jamesâ Smalltalk4U, fosdem, ESUG, and others. I am (very slowly) adding playlists for all of them to the Pharo Youtube channel: https://www.youtube.com/channel/UCp3mNigANqkesFzdm058bvw/playlists If you have videos that you want to see added, send me a mail. The channel itself is here: https://www.youtube.com/channel/UCp3mNigANqkesFzdm058bvw It could use some more subscribers ;-) Marcus

1 0

Re: [Pharo-users] Moose: Problem in Petit Parser
by Damien Cassou Feb. 24, 2014

Feb. 24, 2014

On Mon, Feb 24, 2014 at 12:09 PM, PBK Research <peter(a)pbkresearch.co.uk> wrote: > c. The chapter in Lukas Renggli's PhD thesis. > It may be unfair to call this 'sparse'; the problem is perhaps my inability > to understand it. If you think 'Deep into Pharo' will give me more than > these sources, I may well get hold of it. please have a look at this chapter and please send us feedback (or better send us a patch for the chapter, I can give you access to the book sources). -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

2 1

Re: [Pharo-users] Moose: Problem in Petit Parser
by Damien Cassou Feb. 24, 2014

Feb. 24, 2014

On Sat, Feb 22, 2014 at 6:00 PM, PBK Research <peter(a)pbkresearch.co.uk> wrote: > The documentation is rather sparse did you read the dedicated book chapter of Deep into Pharo? http://deepintopharo.com/ -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

2 1

Re: [Pharo-users] Moose: Problem in Petit Parser
by Tudor Girba Feb. 22, 2014

Feb. 22, 2014

Hi, For Moose related questions, there exists a dedicated mailing list: http://www.moosetechnology.org/about/contact Related to your problem, "not" does consume the input. You want to use "negate", which is implemented as: PPParser>>negate "Answer a new parser consumes any input token but the receiver." ^ self not , #any asParser ==> #second Keep the questions flowing :) Cheers, Doru On Sat, Feb 22, 2014 at 5:25 PM, PBK Research <peter(a)pbkresearch.co.uk>wrote: > Hello All > > Not sure whether this is the right forum for this question - please excuse > and point me in the right direction if I'm wrong. > > I have been playing with Moose 4.8, downloaded last October, mainly > because I am interested in PetitParser. I have been constructing fairly > trivial parsers to get to understand the system. I took as an example a > typical HTML tag, i.e. any text enclosed in angle brackets <>. My first > attempt was: > > ($< asParser, $> asParser not star, $> asParser). > > This seemed to send the parser into a loop, except in the case where there > was no text between the brackets. Floundering around, I tried: > > ($< asParser, (PPPredicateObjectParser anyExceptAnyOf: '>') star, $> > asParser). > > This worked as expected, but I was not happy with the apparent clumsiness > of the middle term. So I tried: > > ($< asParser, (PPPredicateObjectParser char: $>) not star, $> asParser). > > This again sent the parser into a loop. > > It looks as though I have some fundamental misunderstanding of the > function of 'not' in a parser, or else it is not working as specified. > Could someone kindly explain to an inquisitive idiot what is going wrong? > > Many thanks in advance > > Peter Kenny > -- www.tudorgirba.com "Every thing has its own flow"

2 1

Moose: Problem in Petit Parser
by PBK Research Feb. 22, 2014

Feb. 22, 2014

Hello All Not sure whether this is the right forum for this question - please excuse and point me in the right direction if I'm wrong. I have been playing with Moose 4.8, downloaded last October, mainly because I am interested in PetitParser. I have been constructing fairly trivial parsers to get to understand the system. I took as an example a typical HTML tag, i.e. any text enclosed in angle brackets <>. My first attempt was: ($< asParser, $> asParser not star, $> asParser). This seemed to send the parser into a loop, except in the case where there was no text between the brackets. Floundering around, I tried: ($< asParser, (PPPredicateObjectParser anyExceptAnyOf: '>') star, $> asParser). This worked as expected, but I was not happy with the apparent clumsiness of the middle term. So I tried: ($< asParser, (PPPredicateObjectParser char: $>) not star, $> asParser). This again sent the parser into a loop. It looks as though I have some fundamental misunderstanding of the function of 'not' in a parser, or else it is not working as specified. Could someone kindly explain to an inquisitive idiot what is going wrong? Many thanks in advance Peter Kenny

1 0

Dowser edges
by rosariosm Feb. 21, 2014

Feb. 21, 2014

Hi all, Is there a way in dowser to open a builder wich edges are immediately shown instead of appearing when you pass the mouse over the different nodes? I want to create a sort of static image. Thanks, Rosario -- View this message in context: http://forum.world.st/Dowser-edges-tp4744705.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

2 2