- Pharo-dev - lists.pharo.org

Re: [Pharo-project] _ into := changes based on RB

by Lukas Renggli

-=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=- rule := RBUnderscoreAssignmentRule new. SmalllintChecker runRule: rule onEnvironment: BrowserEnvironment new. rule open -=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=- The second expression takes a few minutes, because it parses the complete image. Note, that the resulting browser won't show a diff of the changes, because it pretty prints the AST using ':=' in both cases. Apply the changes and use the Monticello changes to see the real difference. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Oct. 17, 2009

Re: [Pharo-project] Issue 1311: Refactoring scope is broken

by Lukas Renggli

I fixed this and several other issues in RBScanner. It should again be able to parse the complete image. Name: AST-lr.176 Author: lr Time: 17 October 2009, 1:24:59 pm UUID: b80f7c84-c776-4f37-a86d-a092d07dd527 Ancestors: AST-DamienCassou.175 - fixed the RBScanner to parse literals like #( . ; ^ [ ] { } ) - removed all conditionals of the RBScanner for other platforms (VisualWorks, IBM) for additional speed - removed unused code from RBScanner - moved RBParser test from Refactoring-Tests to this package, because it tests functionality in this package Cheers, Lukas 2009/10/17 Lukas Renggli <renggli(a)gmail.com>: > The question is what should the expression > > Â Â #( . ) > > should parse as? Neither the ST-80 book, nor the ANSI standard define > anything. Another nice example where the Smalltalk language is > underspecified ;-) > > Squeak and VisualWorks parse the dot as a the symbol #'.', which is a > good choice, I guess. Unfortunately not that easy to fix in RBScanner > ... > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > -- Lukas Renggli http://www.lukas-renggli.ch

Oct. 17, 2009

Re: [Pharo-project] Follow us on twitter!

by Niko Schwarz

Just for context, I'm referring to the Pharo Sprint in Lille, taking place today. We're already 12 sprinters. On Sat, Oct 17, 2009 at 1:20 PM, Niko Schwarz <niko.schwarz(a)googlemail.com> wrote: > You can follow our progress on twitter! Just open this page: > > http://twitter.com/#search?q=%23pharolille > > We're using the twitter tag #Pharolille > > niko >

Oct. 17, 2009

Re: [Pharo-project] _ into := changes based on RB

by Lukas Renggli

I first need to fix the parser, before you will be able to do that. Lukas 2009/10/17 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > lukas > > we would like to clean the image using your _ -> := rewrite rules. > How can do that? > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli http://www.lukas-renggli.ch

Oct. 17, 2009

[Pharo-project] Follow us on twitter!

by Niko Schwarz

You can follow our progress on twitter! Just open this page: http://twitter.com/#search?q=%23pharolille We're using the twitter tag #Pharolille niko

Oct. 17, 2009

[Pharo-project] _ into := changes based on RB

by StÃ©phane Ducasse

lukas we would like to clean the image using your _ -> := rewrite rules. How can do that? Stef

Oct. 17, 2009

Re: [Pharo-project] Input problems

by StÃ©phane Ducasse

thanks mike stef On Oct 17, 2009, at 12:54 PM, Michael Rueger wrote: > Hi all, > > after looking at the different input problems again it seems to me > that they might all go back to problems with SharedQueue. > Attached is a small change file for all who regularly experience > problems with loosing characters while typing or double pastes. > > Please let me know if after filing in the change set the issues are > fixed, less often or unchanged. > > Thanks > > Michael > > <inputSensor- > fix.cs.st.gz>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 17, 2009

[Pharo-project] [update] 10473

by StÃ©phane Ducasse

- Issue 1258: .1 asNumber = 0 This is true in Pharo, likely resulting in an adventure for the developer - Issue 987: stack top variable on debugger crashes it

Oct. 17, 2009

[Pharo-project] Input problems

by Michael Rueger

Hi all, after looking at the different input problems again it seems to me that they might all go back to problems with SharedQueue. Attached is a small change file for all who regularly experience problems with loosing characters while typing or double pastes. Please let me know if after filing in the change set the issues are fixed, less often or unchanged. Thanks Michael

Oct. 17, 2009

[Pharo-project] TabGroupMorph does not show the labels of the tabs

by Niko Schwarz

Consider this code: w := SystemWindow labelled: 'LatestInspector'. t := TabGroupMorph new addPage: (RectangleMorph new color: Color green ) label: 'Instance' ; addPage: (RectangleMorph new color: Color red) label: 'Methods' . w openInWorld w addMorph: t fullFrame: (LayoutFrame fractions: (0@0 corner: 1@1) offsets: (0@30 corner: 0@0)) w openInWorld . The tab will not have the labels in the right place. This only happens if (1) you actually set colors to the RectangleMorphs (2) The TabGroupMorph is embedded in another morph (SystemWindow (3) There are at least two tabs (for 1 tab, it works great). I suspect the code triggered by color: to be guilty. It triggers a change to the morph, which then triggers relabelling, presumably. I filed this as bug http://code.google.com/p/pharo/issues/detail?id=1316.

Oct. 17, 2009