- Pharo-dev - lists.pharo.org

[Pharo-project] Issue 3566 in pharo: Changes needed to update Sound for 1.2
by pharo＠googlecode.com Jan. 22, 2011

Jan. 22, 2011

Status: Accepted Owner: ryd...(a)gmail.com Labels: Milestone-1.2 Milestone-1.3 New issue 3566 by ryd...(a)gmail.com: Changes needed to update Sound for 1.2 http://code.google.com/p/pharo/issues/detail?id=3566 Some changes are needed to update the external PharoSound package and still be able to stay reasonably in synch with Squeak updates. Mainly this means moving soundsEnabled and useThemeSounds from a separate class into other, appropriate classes.

1 9

[Pharo-project] [update 1.2] #12320
by Marcus Denker Jan. 22, 2011

Jan. 22, 2011

12320 ----- Issue 3566: Changes needed to update Sound for 1.2 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] Fwd: Thanks !!!
by Marcus Denker Jan. 22, 2011

Jan. 22, 2011

On Jan 22, 2011, at 1:41 PM, Luc Fabresse wrote: > Yes, Smalltalk coding, eating and drinking. A picture: And yes -> We managed to squeze double that people in the room -> We will organize the big INRIA room next time again. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Fwd: Thanks !!!
by StÃ©phane Ducasse Jan. 22, 2011

Jan. 22, 2011

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

3 2

Re: [Pharo-project] for coral
by Marcus Denker Jan. 22, 2011

Jan. 22, 2011

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.

2 1

Re: [Pharo-project] [squeak-dev] Xtreams up to date
by Hannes Hirzel Jan. 22, 2011

Jan. 22, 2011

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 >

1 0

[Pharo-project] Issue 3569 in pharo: Error logging cleanup
by pharo＠googlecode.com Jan. 22, 2011

Jan. 22, 2011

Status: Started Owner: siguc...(a)gmail.com New issue 3569 by siguc...(a)gmail.com: Error logging cleanup http://code.google.com/p/pharo/issues/detail?id=3569 Not best, but little better than before. - remove repetitive use of 'PharoDebug.log' all over the places. Now Debugger have #logFileName and keeps name in class var (should expose it in settings later). - deprecated #logError:inContext:to: , one should use #logError:inContext: instead. Attachments: DebuggerLog.3.cs 12.1 KB

1 1

[Pharo-project] Issue 3570 in pharo: EdgeGripMorph DNU when resizing
by pharo＠googlecode.com Jan. 22, 2011

Jan. 22, 2011

Status: Accepted Owner: tudor.gi...(a)gmail.com Labels: Milestone-1.2 Type-Patch Importance-Low New issue 3570 by tudor.gi...(a)gmail.com: EdgeGripMorph DNU when resizing http://code.google.com/p/pharo/issues/detail?id=3570 From Andreas Wacknitz: 1. downloaded 12303: https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/67/artifa… 2. filed in the attached CS 3. executed | m leftMorph scroll | m := PanelMorph new. m hResizing: #shrinkWrap; vResizing: #spaceFill; changeTableLayout; listDirection: #leftToRight. m addMorphBack: (leftMorph := Morph new color: Color red; minimumExtent: 150@10; extent: 150@10; hResizing: #rigid; "shown for clarity, is the default" vResizing: #spaceFill). m addMorphBack: (EdgeGripMorph new width: ProportionalSplitterMorph splitterWidth; hResizing: #rigid; "not the default this time, vResizing is also #spaceFill by default" target: leftMorph). m addMorphBack: (Morph new color: Color green; minWidth: 100; hResizing: #shrinkWrap; vResizing: #spaceFill). scroll := GeneralScrollPane new changeScrollerTableLayout; scrollTarget: m. scroll openInWindow. 4. When I execute the code in a Workspace a little dialog will open. It has a horizontal scroll bar that I can use. As soon as I move the splitter I will get the aforementioned DNU. I am on Mac OS 10.6.6.

1 3

[Pharo-project] [update 1.3] #13015
by Marcus Denker Jan. 22, 2011

Jan. 22, 2011

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.

1 0

Re: [Pharo-project] Issue 3179 in pharo: Failing Tests for Monticello
by pharo＠googlecode.com Jan. 22, 2011

Jan. 22, 2011

Comment #1 on issue 3179 by marcus.denker: Failing Tests for Monticello http://code.google.com/p/pharo/issues/detail?id=3179 Current state: >>> Tests.Monticello.MCChangeNotificationTest.testExtMethodModified 0.0050 >>> 50 >>> Tests.Monticello.MCPackageTest.testUnload 0.636 50 The Tests.Monticello.MCPackageTest.testUnload only fails on Hudson.

1 8