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

[Pharo-project] splitters in table layout
by Tudor Girba Jan. 24, 2011

Jan. 24, 2011

Hi, I would like to have splitters used inside a table layout, but I cannot seem to manage. In particular, I would like to have these splitters work with the GeneralScrollPane. I tried something like below, but it seems that the splitters expect a frame layout. What can I do about it? | m scroll | m := PanelMorph new. m hResizing: #shrinkWrap; vResizing: #spaceFill; changeTableLayout; listDirection: #leftToRight. m addMorphBack: (PanelMorph new minWidth: 100; hResizing: #shrinkWrap; vResizing: #spaceFill). m addMorphBack: (PanelMorph new minWidth: 100; hResizing: #shrinkWrap; vResizing: #spaceFill). m addPaneSplitters. scroll := GeneralScrollPane new changeScrollerTableLayout; scrollTarget: m. scroll openInWindow. Cheers, Doru -- www.tudorgirba.com "Speaking louder won't make the point worthier."

5 19

Re: [Pharo-project] [squeak-dev] Xtreams up to date
by mkobetic＠gmail.com Jan. 24, 2011

Jan. 24, 2011

"Hannes Hirzel"<hannes.hirzel(a)gmail.com> wrote: > If I explore the resulting object I got what is shown in the screen > shot. I am not sure how to interpret the result. Yes, it's not the best possible representation, but it does show the full parse tree. The tree can be rather complicated depending on how complicated is the grammar. That's why I suggested playing with simpler grammars. But the reason why I even mentioned the TreeBuilder is that it's the simplest possible Actor, it implements single method that packages the result of each successful production as it's own node. Maybe using an array instead of associations would create a slightly more "tree like" 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? I've attached a fileout of the class that you can file into Squeak, except it references VW XML classes, so it won't work. If you fix it up to use the Squeak XML stuff you should be able to get it to work. All you really need is XML.Element and XML.Tag equivalent. The second fileout shows how the class variables are initialized in VW. You might need to turn the initializers into equivalent class side initialize methods. > 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. OK, let's try something really simple. The wikipedia page shows a simple arithmetic expression grammar. Here it is transcribed for Xtreams: grammar := ' Number <- [0-9]+ Parenthesised <- "(" Expr ")" Value <- Number / Parenthesised Product <- Value (("*" / "/") Value)* Sum <- Product (("+" / "-") Product)* Expr <- Sum'. I expanded the Value from the wiki grammar into separate Number and Parethesised expression productions. It'll hopefully be clear why shortly. You already know how to get a parser from grammar. That's always the same and for anything more complex you'll probably want to cache the parser instead of recreating it every time, but this will do fine for now: parser := PEG.Parser parserPEG parse: 'Grammar' stream: grammar actor: PEG.ParserParser new. With this you can already parse expressions (note that the grammar as it is written cannot handle whitespace) parser parse: 'Expr' stream: '3+4*(10-4)' reading actor: nil you'll get this (roughly formatted to provide at least some resemblance of the expression tree): #( #(OrderedCollection ($3 "16r0033") OrderedCollection ()) OrderedCollection (# ('+' #(OrderedCollection ($4 "16r0034") OrderedCollection (# ('*' #( '(' #( #(OrderedCollection ($1 "16r0031" $0 "16r0030") OrderedCollection ()) OrderedCollection (# ('-' #(OrderedCollection ($4 "16r0034") OrderedCollection ())))) ')'))))))) That's obviously not very easy to take apart to work with, that's why you want an Actor that will receive rule specific callbacks and do whatever. Let's say we want to evaluate the expression and return the result. We'll make a subclass of Actor called Evaluator. As I mentioned earlier, the Actor class provides pragma based mechanism for expressing rule specific callbacks so you simply write a method for each rule for which you want to do something and annotate it with a pragma. Let's first try to turn the digit collections into numbers: Evaluator>>Number: digits <action: 'Number'> ^digits inject: 0 into: [ :total :digit | total * 10 + ('0123456789' indexOf: digit) - 1 ] With this you can parse numbers parser parse: 'Expr' stream: '3456' reading actor: Evaluator new Now let's try to add. We'll want a method for the Sum production but there's a slightly tricky part there. Note that the rule is defined as Sum <- Product (("+" / "-") Product)* which means that you get a term (Product) and then zero or more pairs of + or - and another term. What the method receives will be collection of the first term and then pairs of the operator with its term. So parsing this: parser parse: 'Expr' stream: '3+4+5+6+7' reading actor: Evaluator new will give you #(3 OrderedCollection (#('+' 4) #('+' 5) #('+' 6) #('+' 7))) So if you add a method for Sum, that's what it will need to deal with: Sum: terms <action: 'Sum'> ^terms last inject: terms first into: [ :total :next | (next first = '+') ifTrue: [ total + next last ] ifFalse: [ total - next last ] ] The Actor pragmas provide another convenience for taking more complex input apart. You can write the above as Sum: first rest: pairs <action: 'Sum' arguments: #(1 2)> ^pairs inject: first into: [ :total :pair | (pair first = '+') ifTrue: [ total + pair last ] ifFalse: [ total - pair last ] ] The arguments: keyword simply says invoke this method with elements 1 and 2 of the rule input (terms) as arguments. Obviously the method must take the corresponding number of arguments as well. So with the above rules the addition expression should give you 25. The Product rule handling is analogous: Product: first rest: pairs <action: 'Product' arguments: #(1 2)> ^pairs inject: first into: [ :total :pair | (pair first = '*') ifTrue: [ total * pair last ] ifFalse: [ total / pair last ] ] Finally the parenthesised expression is rather simple: Parenthesised: expression <action: 'Parenthesised' arguments: #(2)> ^expression It receives a three element array: the left bracket, the expression inside and the right bracket. All we really need to do is return the expression in the middle. The above is using the arguments: pragma again to achieve that, the following would be equivalent: Parenthesised: expression <action: 'Parenthesised'> ^expression at: 2 I hope by now it's also clearer why it was useful to factor the Value definition out into separate Number and Parenthesised rule. Otherwise we'd have to handle both cases in a single Value: method, which would make the code messier. > For example besides the classes PEGParserPEGTest and > PEGParserSmalltalkTest (6 test cases) a class PEGParserHttpUrlTest or > PEGParserJavaScriptTest would be helpful. Yup, the tests are seriously wanting as well. Hopefully we'll get there soon. BTW, the parsing stuff doesn't work for me out of the box in either Squeak or Pharo in the images that I use (which should be quite clean). The problem I'm seeing is that the Dictionary>>addAll: in ParserParser>>Grammar: doesn't work as expected. It's trying to add collection of associations to a dictionary but ends up adding them as values indexed by integers. I can fix it but I wonder what do people have loaded that makes it work for them. Anyway, hopefully the above can get you going. Cheers, Martin

2 1

[Pharo-project] Issue 3585 in pharo: UIManager>>grafPort
by pharo＠googlecode.com Jan. 24, 2011

Jan. 24, 2011

Status: Started Owner: siguc...(a)gmail.com New issue 3585 by siguc...(a)gmail.com: UIManager>>grafPort http://code.google.com/p/pharo/issues/detail?id=3585 This is strange use pattern: bitBlt := UIManager default grafPort used by Character/display scanners of paragraphs. Conceptually, paragraph should ask a canvas (where it will be drawn on) for providing a graph port, not UIManager, which is too high level for such kind of queries. I suggest to deprecate usage of #grafPort and remove grafPort from UIManager protocol.

1 0

[Pharo-project] How to browse users of a Trait
by laurent laffont Jan. 24, 2011

Jan. 24, 2011

Hi, in the browser, when selecting a Trait -> right-click -> browse references the References browser is empty. Is it supposed to work or there's an another way to browse users of a Trait ? Laurent Laffont Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/

2 1

Re: [Pharo-project] Deprecations and Hudson
by Marcus Denker Jan. 24, 2011

Jan. 24, 2011

On Jan 23, 2011, at 10:57 AM, Mariano Martinez Peck wrote: > Hi. With Hudson we want to automatically build images. It can happens that external packages did not yet update their code and that are still using depreacted methods. So, by default we raise an exception. This is good because when the developer see an annoying popup, maybe he fix it ;) > > Now, the problem is that Hudson FAILS if there is a deprecated. So, I suggest changing the hudson dev build script to: > > > Deprecation raiseWarning: false. > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfPharo'; > load. > > ((Smalltalk at: #ConfigurationOfPharo) project lastVersion) perform: #silently: with: true; perform: #load. > Deprecation raiseWarning: true. > > > This way, the build image can be always build and then at runtime, the user will see the popups. > > Marcus, please, let me know if you change this becasue I need it to fix a problem with Metacello. done. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

5 6

Re: [Pharo-project] default styler is shout
by Marcus Denker Jan. 24, 2011

Jan. 24, 2011

Hi, We need the imperfect, intermediate solution that is good enough for people to live with in 1.2. On Jan 22, 2011, at 4:25 PM, Tudor Girba wrote: > Hi, > > In the latest Morphic version, the default styler of the PluggableTextMorph is given by: > useDefaultStyler > "This should be changed to a proper registry but as long as there is only shout this will do" > > Smalltalk globals > at: #SHTextStylerST80 > ifPresent: [ :stylerClass | self styler: (stylerClass new view: self) ] > ifAbsent: [ self styler: ( NullTextStyler new view: self) ] > > Thus, if Shout is loaded, you will get it in all text morphs by default. Given that TextMorph should be general and be used in all sorts of contexts, the default behavior should be the original: > > useDefaultStyler > "This should be changed to a proper registry but as long as there is only shout this will do" > > self styler: (NullTextStyler new view: self; yourself). > > > What do you say? > > Cheers, > Doru > > -- > www.tudorgirba.com > > "We are all great at making mistakes." > > > > > > > > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

3 2

Re: [Pharo-project] Pharo Refactoring Tool
by ashubair＠scs.ryerson.ca Jan. 23, 2011

Jan. 23, 2011

Hi all, I'm really more than happy to be one of your super-active and supportive community.. Thank you for your ideas, and I will try my best to keep you updated with any achieved preogress.. Any new ideas are more than welcome! Mr.Ducasse, seems that the thread has been deleted from my inbox by mistake, I'll try to look for it in the archive and I'll get back to you as soon as I find it.. Mr.Peck, thanks for your valuable advice. Thanks all for your time and suggestions, Alia

1 0

[Pharo-project] Deprecations and Hudson
by Mariano Martinez Peck Jan. 23, 2011

Jan. 23, 2011

Hi. With Hudson we want to automatically build images. It can happens that external packages did not yet update their code and that are still using depreacted methods. So, by default we raise an exception. This is good because when the developer see an annoying popup, maybe he fix it ;) Now, the problem is that Hudson FAILS if there is a deprecated. So, I suggest changing the hudson dev build script to: Deprecation raiseWarning: false. Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfPharo'; load. ((Smalltalk at: #ConfigurationOfPharo) project lastVersion) perform: #silently: with: true; perform: #load.Deprecation raiseWarning: true. This way, the build image can be always build and then at runtime, the user will see the popups. Marcus, please, let me know if you change this becasue I need it to fix a problem with Metacello. mariano

1 0

[Pharo-project] Issue 3575 in pharo: [Failing Tests] Tests.Release.ReleaseTest.testObsoleteClasses
by pharo＠googlecode.com Jan. 23, 2011

Jan. 23, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.1.2 New issue 3575 by marcus.d...(a)gmail.com: [Failing Tests] Tests.Release.ReleaseTest.testObsoleteClasses http://code.google.com/p/pharo/issues/detail?id=3575 Full Build 1.1.1 hudson Tests.Release.ReleaseTest.testObsoleteClasses would be nice to fix that...

1 1

[Pharo-project] [update 1.1] #11418
by Marcus Denker Jan. 23, 2011

Jan. 23, 2011

11418 ----- [Failing Tests] Hudson Full 1.1 ToolsTest.Inspector.WeakSetInspectorTest.testSymbolTableM6812 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0