- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Automatically (OB?) run class methods?

by Mariano Martinez Peck

On Tue, Sep 14, 2010 at 12:04 PM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > Hi Mariano, > > Before I propose the test integration in system browser a few years ago, > people used a lot comments like "self debug: #testFoo". > Adding the command cmd-T greatly reduced these kind of comment. > > Probably a kind of "send" like method will help reduce these kind of > comment. > > As Lukas said, I personally often select the method body. But it happens > that the method body is larger than the code pane, which requires too much > time to select. > > At least a cmd+a and then a cmd+d anyway, I wasn't ware of cmd+d :) Maybe adding that to the menu in the case of class side methods? These will help to remove those kind of comments > Cheers, > Alexandre > > > On 14 Sep 2010, at 11:38, Mariano Martinez Peck wrote: > > > HI guys. I tend to see these pattern everywhere: > > > > openLoadAndQueryWorkspace > > "self openLoadAndQueryWorkspace" > > (Workspace new > > acceptContents: ' > > â¦â¦ > > > > > > Having to have that kind of thing from my point of view, reveals a > weakness in our IDE. Furthermore, when we rename the method, the comment is > not refactored. > > > > Now I was thinking if it would be interesting or not, to be able to > directly run class side methods. It would be nice: > > > > - To have an entry in the context (right click) menu, only when selecting > a class method, to directly evaluate it. Maybe we can call it "Evaluate it" > or "Send message" or "Do it" â¦ I don't know. > > > > - To have a shortcut for that. Thenâ¦we are inside that method for > example, and with a shortcut we can evaluate itâ¦no need to go up to the name > and evaluate the comment. > > > > What do you think? > > > > Cheers > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 14, 2010

Re: [Pharo-project] Strange behavior with TestRunner

by Alexandre Bergel

You probably rely on what has to be found in a method dictionary. "Run Coverage" replaces compiled methods by a plain object, in which run:with:in: is executed [*]. If in your test you expect to find a compile method, then you may surprises. Cheers, Alexandre [*] http://www.iam.unibe.ch/~scg/Archive/Papers/Bergel06bRDLPrototyping.pdf On 14 Sep 2010, at 14:14, Noury Bouraqadi wrote: > On the pharo 1.2-12141, I run the SocketStreamTest. All green. > But, when I try the "Run Coverage" all turn red. > > Any hint? > > Noury @ ESUG 2010 - Barcelona :-) > --- > 18th International Smalltalk Joint Conference, September 13 -17 2010 Barcelona, Spain. > http://www.esug.org/Conferences/2010 > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 14, 2010

[Pharo-project] Strange behavior with TestRunner

by Noury Bouraqadi

On the pharo 1.2-12141, I run the SocketStreamTest. All green. But, when I try the "Run Coverage" all turn red. Any hint? Noury @ ESUG 2010 - Barcelona :-) --- 18th International Smalltalk Joint Conference, September 13 -17 2010 Barcelona, Spain. http://www.esug.org/Conferences/2010

Sept. 14, 2010

Re: [Pharo-project] Settings for Shout syntax highlighting

by Simon Denier

Following some hints from Alain, a new version (it just removes a method extension) Settings-Shout-simon_denier.2 in PharoInbox On 13 sept. 2010, at 11:00, Simon Denier wrote: > Hi > > A new package Settings-Shout in the Pharo Inbox for issue 1611 > > SLICE-Issue-1611-ShoutSettings-simon_denier.1 > > You can now set how (for example), instance variables, selector patterns, class references appears in the Shout pane. > One point is that Shout comes with a list of hundred token types which can be individually customized, some of which I have no idea what they represent (externalCallTypePointerIndicator?). To keep things manageable, I defined some groups of logically related token types (like the gorup 'selector patterns' for token types patternKeyword, patternBinary, patternUnary). > > "Class SHGroupStyle manages settings for the Shout syntax highlighting. Token types are organized in logical groups which will share the same style. Currently, only color and emphasis can be edited through Shout settings. Text font and size are managed through the more general appearance setting. Changing a style setting on a SHGroupStyle automatically applies the style. > > Groups are defined in the class-side method initializeGroups. Alternatively, one can set its own style table using Shout tokens by calling #customStyleTable (see SHTextStylerST80 class>>defaultStyleTable for the format)." > > > Help needed: > 1) code review > 2) review group definition, because I made some groups based partly on my intuition, partly on styling difference in the current difference: there may be a better partition of token types. > 3) review description for group, setting organization... > > > Thanks to Alain for helping with settings and especially polymorph widgets. > > -- > Simon > > > -- Simon

Sept. 14, 2010

Re: [Pharo-project] DemoMode should not change Fonts only sizes?

by Serge Stinckwich

2010/9/14 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Hi Alain, I was trying the DemoMode before my talk at ESUG and I thought > that it would be better if this guy only changes the size of the fonts. I am > not sure if changing the fonts is good. > > For example, right now it is using FreeType with DejaVu. Since Pharo1.1 dev > doesn't use them, there is no folder "Fonts" with themâ¦..thus they are not > found and ugly fonts are rendered. Yes i already talk with Alain about this problem. One option was to include severals sizes of bitmap DejaVu font. BTW, we fix with Alain a problem of browser switches rendering with the demo font during the Smalltallk Camp here in Barcelona. -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

Sept. 14, 2010

[Pharo-project] Some thoughts...

by Alexandre Bergel

Hi, I really would like to see projects like Opal and Ocean happening. Even though I may not have the time to directly contribute to them, they are important and I will use them. I am struggling these days to instrument the whole Pharo image and this is not easy. I am eagerly waiting for Opal. I got burned in the past with networks. So, please continue... Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 14, 2010

[Pharo-project] Thanks Marcus for the presentation of Pharo

by Alexandre Bergel

I like very much the way you described the role of Pharo for doing Research. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 14, 2010

Re: [Pharo-project] One order of magnitude faster sets/dicts?!

by Toon Verwaest

To be fair, the text below just shows that Dictionary / Set in Pharo degrade from O(1) to O(n) as it has to search through all the elements in the Set/Dictionary. It's not that those high factors are constants because of better implementation. Pinocchio dictionaries just stay O(1). The only way to degrade Pinocchio dictionaries is by giving it bad hashes; but that's something you can't solve in all cases anyway. cheers, Toon > This forces the dictionary to miss a lot more often. Since all the > keys are grouped together this is the worst case for Squeak/Pharo > dictionaries if you want to look something up that's not there. This > are the results on Squeak 4.1: > > PBDictionary 0.0261 +/-0.0017 > PBSTDictionary 5.235 +/-0.01 > > So around 200x faster in case of PDictionary. > > While PDictionary stays stable (even slightly faster, go figure), > Squeak dictionaries degrade immensely! On Pharo the results are a bit > better, but still very much degraded: > > PBDictionary 0.02387 +/-0.00014 > PBSTDictionary 1.6577 +/-0.0036 > > So around 60x faster in case of PDictionary. > > > If on Set I ensure that all elements will be found, I get the > following result for #includes: > > PBSetIncludes 0.00440 +/-0.0001100000000000001 > PBSTSetIncludes 0.004000 +/-9.6e-5 > > making PSet marginally slower. However, once you start not finding > elements, with the same change as before, (to: size*10 by: 10): > > PBSetIncludes 0.00443 +/-0.0001 > PBSTSetIncludes 0.9844000000000005 +/-0.0017 > > So around 220x faster in case of PSet. While PSet and PDictionary > never really suffer from collisions, normal Squeak/Pharo dictionaries > suffer immensely and grow up to 200x slower. Btw, this last benchmark > was run on Pharo.

Sept. 14, 2010

Re: [Pharo-project] Automatically (OB?) run class methods?

by Alexandre Bergel

Hi Mariano, Before I propose the test integration in system browser a few years ago, people used a lot comments like "self debug: #testFoo". Adding the command cmd-T greatly reduced these kind of comment. Probably a kind of "send" like method will help reduce these kind of comment. As Lukas said, I personally often select the method body. But it happens that the method body is larger than the code pane, which requires too much time to select. Cheers, Alexandre On 14 Sep 2010, at 11:38, Mariano Martinez Peck wrote: > HI guys. I tend to see these pattern everywhere: > > openLoadAndQueryWorkspace > "self openLoadAndQueryWorkspace" > (Workspace new > acceptContents: ' > â¦â¦ > > > Having to have that kind of thing from my point of view, reveals a weakness in our IDE. Furthermore, when we rename the method, the comment is not refactored. > > Now I was thinking if it would be interesting or not, to be able to directly run class side methods. It would be nice: > > - To have an entry in the context (right click) menu, only when selecting a class method, to directly evaluate it. Maybe we can call it "Evaluate it" or "Send message" or "Do it" â¦ I don't know. > > - To have a shortcut for that. Thenâ¦we are inside that method for example, and with a shortcut we can evaluate itâ¦no need to go up to the name and evaluate the comment. > > What do you think? > > Cheers > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 14, 2010

Re: [Pharo-project] Refactor class name should check also in comments?

by Lukas Renggli

That will be extremely expensive (in terms of minutes) to load all class and method comments to check for string matches. We can do that if we can read the sources faster. Lukas 2010/9/14 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > Hi Lukas. Several times I refractor a class name and I forget to update a > lot of references to it in comments, class comments, etcâ¦Â Do you think we > can adapt RB so that it also checks there? > > Thanks > > Mariano > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch

Sept. 14, 2010