January 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] for coral

by Marcus Denker

On Jan 22, 2011, at 12:41 PM, Esteban Lorenzano wrote: > Hi, > this is a side question... does coral had a file format for classes and extensions, more human readable than current file out results? > Yes! It's not final yet... but you can see what is there: http://www.auverlot.fr/pharo/coralinstall/ Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 22, 2011

Re: [Pharo-project] for coral

by Esteban Lorenzano

Hi, this is a side question... does coral had a file format for classes and extensions, more human readable than current file out results? Cheers, Esteban El 22/01/2011, a las 5:19a.m., Marcus Denker escribiÃ³: > > On Jan 22, 2011, at 9:15 AM, StÃ©phane Ducasse wrote: > >> We should: >> >> - use this list >> - have a plan > > Item 1: Hudson Project for Coral. > > :-) > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

Jan. 22, 2011

Re: [Pharo-project] Some important news

by Esteban Lorenzano

+1 El 21/01/2011, a las 11:47p.m., Tony Fleig escribiÃ³: > Excellent. Where do I sign up? > > On Fri, Jan 21, 2011 at 11:26 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Hi guys >> >> some important news today, we decided that we will set up a pharo association >> so that we can promote pharo. We would like to be able to collect money and >> create bounties to improve pharo. >> >> Stef >> >

Jan. 22, 2011

Re: [Pharo-project] Fwd: Thanks !!!

by Mariano Martinez Peck

Indeed, it was a cool srptint. Lot of people (20 aprox.) and a lot of hacking :) Thanks ESUG for the sponsor of chocolates, cookies, drinks, etc. Cheers mariano On Fri, Jan 21, 2011 at 11:01 PM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > Hi lille/douai/bruxelles pharo sprinters > > Thanks for all this good energy. Yesterday I went to a javascript > conference > and my energy was low to see how we (smalltalkers) would better organized > and pushing. > Now today it was good energy. Thanks again. > > Stef > > > > >

Jan. 22, 2011

Re: [Pharo-project] [squeak-dev] Xtreams up to date

by Hannes Hirzel

Thank you Martin, your explanations got me some steps further. I found the page http://pdos.csail.mit.edu/~baford/packrat/ by Bryan Ford which seems to be a good entry point for reading about PEG parsing. That page refers to http://en.wikipedia.org/wiki/Parsing_expression_grammar as a good technical overview. I took the wiki example from http://code.google.com/p/xtreams/wiki/Parsing and adapted the names so that it fits the Squeak implementation A Parser is created from a PEG grammar by parsing the grammar rules using the ParserParser. wikiGrammar := PEGParser grammarWiki reading. wikiParser := PEGParser parserPEG parse: 'Grammar' stream: wikiGrammar actor: PEGParserParser new. input := 'Single paragraph with *bold* and _italic_ text and a [link]' reading. "As you indicated I used the PEGTreeBuilder" wikiParser parse: 'Page' stream: input actor: PEGTreeBuilder new If I explore the resulting object I got what is shown in the screen shot. I am not sure how to interpret the result. "Regarding the wiki example: the class PEGWikiGenerator is not included" wikiParser parse: 'Page' stream: input actor: PEGWikiGenerator new. Where can I get this class? The comment of the method #parse:stream:actor: of class PEGParser is helpful "Parse @definition from aStream using @anActor to act on the matching rules. "" definition <String> identifies the rule of the grammar to apply to the input aStream <ReadStream> the input to parse anActor <Actor> receives callbacks from the parser for the successfully rules with the matching the input ^ <Object> result of the actor action for the @definition " As class methods of PEGParser there are 8 grammars included - CSS3, HttpUrl, JSON, JavaScript, PEG, Smalltalk, Wiki, XML. I think a simple complete example which actually does something would be helpful for me. TreeBuilder seems to do nothing and I do not see the tree. For example besides the classes PEGParserPEGTest and PEGParserSmalltalkTest (6 test cases) a class PEGParserHttpUrlTest or PEGParserJavaScriptTest would be helpful. Actually I would like to parse some simple Javascript like mySent = new aswExample('') mySent.addWord('Ninatoka') mySent.currentWord().firstLetterUppercase=true mySent.currentWord().addMorpheme('ni-','S1s-') mySent.currentWord().addMorpheme('na-','Pres.-') mySent.currentWord().addMorpheme('tok','come_from') mySent.currentWord().addMorpheme('-a','-VF') mySent.addWord('Uswisi.') mySent.currentWord().addMorpheme('Uswisi','Switzerland.') mySent.writeHTML() It is used for web pages on which Swahili text is displayed. On request a morphological analysis is shown. A note: this example could be parsed with some manually constructed code without PEG I assume, just string matching and some branching. So there is no pressure on this. But I'd like to use it to learn PEG parsing. The goal is to translate the JavaScript code to Smalltalk code (and later one to an XML representation for printing). --Hannes On 1/21/11, mkobetic(a)gmail.com <mkobetic(a)gmail.com> wrote: > "Hannes Hirzel"<hannes.hirzel(a)gmail.com> wrote: >> Besides http://code.google.com/p/xtreams/wiki/Parsing are there more >> examples how to use Peg parsing? > > Unfortunately that one is still waiting for documentation. Even the little > bit that is on the wiki page uses an example that wasn't ported because it > uses VW's XML Elements. > > It's actually not that complicated to use. Basically you take a PEG grammar, > you parse it as the wiki example shows (the first 2 lines). Then you need an > 'actor' that will get callbacks from the parser when it parses some input. > The Actor class provides simple pragma based dispatch mechanism for > convenience, but ultimately the actor simply receives > #process:object:start:stop: callbacks from successfully applied grammar > rules. The TreeBuilder in the Tests package shows the simplest Actor that > just collects all the callback arguments. The return value of the callback > is important, the object: argument of the callback is a collection of what > the lower level rules returned from their callbacks. Anyway that's real > quick description of how the parsing mechanism works from user point of > view. Real documentation needs a lot of simple examples to make that > clearer, but hopefully this could get you going if you experiment with > simpler grammars and the TreeBuilder a bit. I'll try to answer any more > specific questions as I can. > > HTH, > > Martin >

Jan. 22, 2011

Re: [Pharo-project] Issue 3569 in pharo: Error logging cleanup

by pharo＠googlecode.com

Updates: Status: Closed Labels: Milestone-1.3 Comment #1 on issue 3569 by marcus.d...(a)gmail.com: Error logging cleanup http://code.google.com/p/pharo/issues/detail?id=3569 130014

Jan. 22, 2011

Re: [Pharo-project] Issue 3570 in pharo: EdgeGripMorph DNU when resizing

by pharo＠googlecode.com

Updates: Status: Closed Comment #3 on issue 3570 by marcus.d...(a)gmail.com: EdgeGripMorph DNU when resizing http://code.google.com/p/pharo/issues/detail?id=3570 13015

Jan. 22, 2011

[Pharo-project] [update 1.3] #13015

by Marcus Denker

13015 ----- Issue 3500: Create deprecated13 Issue 3563: PCCByCompilationTest tests sometimes fail randomly Issue 3179: Failing Tests for Monticello Issue 3570: EdgeGripMorph DNU when resizing -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 22, 2011

Re: [Pharo-project] Issue 3179 in pharo: Failing Tests for Monticello

by pharo＠googlecode.com

Updates: Status: Closed Labels: Milestone-1.2 Comment #9 on issue 3179 by marcus.d...(a)gmail.com: Failing Tests for Monticello http://code.google.com/p/pharo/issues/detail?id=3179 13015

Jan. 22, 2011

Re: [Pharo-project] Issue 3568 in pharo: Remove SelectorBrowser

by pharo＠googlecode.com

Comment #3 on issue 3568 by marcus.d...(a)gmail.com: Remove SelectorBrowser http://code.google.com/p/pharo/issues/detail?id=3568 Issue 3493 has been merged into this issue.

Jan. 22, 2011