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

[Pharo-project] Issue 3380 in pharo: UnhandleError remove dependence to UIManager
by pharo＠googlecode.com Jan. 22, 2011

Jan. 22, 2011

Status: Fixed Owner: Benjamin.VanRyseghem.Pharo Labels: Type-Seed New issue 3380 by Benjamin.VanRyseghem.Pharo: UnhandleError remove dependence to UIManager http://code.google.com/p/pharo/issues/detail?id=3380 fix Attachments: UnhandleErrorExtension.1.cs 231 bytes

1 1

[Pharo-project] Issue 3427 in pharo: two methods from BlockContext to BlockClosure
by pharo＠googlecode.com Jan. 22, 2011

Jan. 22, 2011

Status: FixedWaitingToBePharoed Owner: stephane.ducasse Labels: Milestone-1.3 New issue 3427 by stephane.ducasse: two methods from BlockContext to BlockClosure http://code.google.com/p/pharo/issues/detail?id=3427 Levente Uzonyi uploaded a new version of Kernel to project The Trunk: http://source.squeak.org/trunk/Kernel-ul.519.mcz ==================== Summary ==================== Name: Kernel-ul.519 Author: ul Time: 8 December 2010, 2:52:41.144 am UUID: 630c1710-46b8-5248-bdb8-e08d99d6d9c0 Ancestors: Kernel-ul.518 - copied another two methods from BlockContext to BlockClosure. One of them fixes http://bugs.squeak.org/view.php?id=7579 . =============== Diff against Kernel-ul.518 =============== Item was added: + ----- Method: BlockClosure>>newProcessWith: (in category 'scheduling') ----- + newProcessWith: anArray + "Answer a Process running the code in the receiver. The receiver's block + arguments are bound to the contents of the argument, anArray. The + process is not scheduled." + <primitive: 19> "Simulation guard" + ^Process + forContext: + [self valueWithArguments: anArray. + Processor terminateActive] asContext + priority: Processor activePriority! Item was added: + ----- Method: BlockClosure>>valueWithExit (in category 'evaluating') ----- + valueWithExit + self value: [ ^nil ]!

1 1

Re: [Pharo-project] Issue 3227 in pharo: Remove all MethodFinder
by pharo＠googlecode.com Jan. 22, 2011

Jan. 22, 2011

Updates: Labels: -Milestone-1.2 Milestone-1.3 Comment #3 on issue 3227 by siguctua: Remove all MethodFinder http://code.google.com/p/pharo/issues/detail?id=3227 (No comment was entered for this change.)

1 1

Re: [Pharo-project] Issue 3172 in pharo: NewInspector really really slow while parsing XMLNode
by pharo＠googlecode.com Jan. 22, 2011

Jan. 22, 2011

Updates: Cc: jaa...(a)zoho.com Comment #2 on issue 3172 by laurent.laffont: NewInspector really really slow while parsing XMLNode http://code.google.com/p/pharo/issues/detail?id=3172 From jaayer: Hi Laurent. First, thank you for your screencasts. I am writing to you concerning this issue: http://code.google.com/p/pharo/issues/detail?id=3172&q=xml&colspec=ID%20Typ… I only discovered the above last night, as I am not a Pharo core developer and only check the issue tracker occasionally. I am a maintainer of XML-Support, however, so feel free to mail me directly with any issues you have in the future, or at the very least, please post them to the Pharo-Project, Squeak-dev or Moose-dev lists. Now, in your video, which was made back in August, you used version .74 of XML-Parser. If you look at the changelogs of XML-Parser, it is clear that much has changed since that time. It would not be unreasonable to assume that one or more of those changes is responsible for the difficulties you experienced inspecting that XML document. However, if you load version .74, the same version used in your screencast, into a Pharo 1.1 image, the problem is still there (and is in fact much worse), meaning that whatever has changed since August to bring this about, I can say with some confidence that it is not in XML-Parser. Using the latest version of XML-Parser and ignoring the question of causality for a moment, the bottleneck we're observing is in XMLNode>>printOn:. The proof is that disabling XMLNode>>printOn: makes our problem go away. Why then is XML generation suddenly such a bottleneck? The main reason appears to be that the document being inspected is, when printed, roughly 40K in size, and by inspecting it you are causing it to be printed over and over again. I tracked sends of #printOn: and found that inspecting the document and navigating to the "title" element results in #printOn: being sent 300-400 times. The recipients were the document object and the root "feed" element ~350 times. By the time you've navigated to the "feed" element and clicked the "Elements" entry to display its children, #printOn: has already been sent ~150 times. That means the remaining 150-250 sends come when you click on the "title" element or some other child element of the root, and that single additional click results in the generation of roughly 6-10 MBs of XML (150 * 40K to 250 * 40K). *That* is why it's so slow. Now, why does NewInspector cause #printOn: to be sent so much? I honestly don't know. I will forward this to the maintainers of NewInspector to get their input. Maybe NewInspector can be changed to not print inspected objects so often, or to provide them with some way to suppress its printing behavior. It must be pointed out that Pharo also comes with an object explorer that is designed specifically for this usecase of browsing deep object hierarchies. I tried exploring the document with cmd-I (capital i) and encountered no trouble.

1 2

[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

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