- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] WhatsUp from: 2014-10-06 until: 2014-10-19

by Sebastian Sastre

- Iâve realized that this email was a social media done with email, cool :) BTW I think feeding a blog with this thread would be interesting, what do you think? - presented flow at CampSmalltalkVI2014, good reception, mostly offline but also slides have ~360 views already - added a couple of cool and very needed features to it (related to double data-binding in the frontend) - preparing to add some real-time features to it (in its Pharo backend) On Oct 6, 2014, at 2:00 AM, seaside(a)rmod.lille.inria.fr wrote: > Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: > > - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS > > ### What's next, until 2014-10-19 (*): > > - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION > > (*) we'll be expecting results by then ;) >

Oct. 6, 2014

ANNC: QR Code (v.2)

by J.F. Rick

I've got a new version of the QR Code generator: http://smalltalkhub.com/#!/~JochenRick/QRCode This one includes support for MicroQR, for UTF-8 encoding and other aspects of the latest QR standard (e.g., mirroring). I've also written a small Zinc web app which makes it easy to try out. Enjoy! Jeff -- Jochen "Jeff" Rick, Ph.D. http://www.je77.com/ Skype ID: jochenrick

Oct. 6, 2014

Re: [Pharo-dev] [Moose-dev] [ANN] Test Coverage with Hapao

by Maximiliano Taborda

Hi Alexandre. Perfect about the legends problem. Thanks. And about the best way to exclude some methods, I don't know what it is. I use the world menu to run Hapao. In fact, I made a new entry in the world menu that fit with my needs, that is: - excludes all initialization methods, i.e. selectors named like #initialize* - excludes all the #new methods - excludes all methods that are defined in a protocol named as private, i.e. 'accessing - private' This new entry checks the coverage over a class/es hierarchy and, also, - run only the tests related to this hierarchy - not take into account the abstract methods when computing the covered percentage; if I have an abstract method without a concrete one implemented in all the subclasses, I have a design error, so my real problem is the absence of the concrete method and not the absence of the test. If you are interested I leave you attached to this email the code related to this entry. Maybe is not the best way to implement what I need, but is a quickly one. Congratulations for this tool, is great to easily visualize what portion of my model are not covered by tests. Regards. Maximiliano 2014-10-05 22:27 GMT-03:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > Hi Maximiliano! > > The legend problem is now fixed. Can you double check please? > > What would be the best way to exclude some methods? This question slightly > rephrased: how do you run Hapao? Programmatically or using the World menu? > > Cheers, > Alexandre > > > On Oct 2, 2014, at 11:34 PM, Maximiliano Taborda <mtaborda(a)gmail.com> > wrote: > > > Hi Alexandre. > > > > Yes, now it works. Thank you. But, the box with the legends don't show > very well. Like in the attached image: > > > > <RelativeDate.png> > > > > And, a question. Is there a way to exclude some methods from the > analysis? I have some class methods, used for initialize some singletons > for example, that I do not want to be considered for coverage. > > > > Regards. > > Maxi > > > > 2014-10-02 18:39 GMT-03:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > > Hi! > > > > Sorry, we somehow slightly messed up with the configurations. > > I just took the last Pharo 4.0, and loaded Roassal2: > > > > -=-=-=-=-=-=-=-=-=-=-=-= > > Gofer new smalltalkhubUser: 'ObjectProfile' > > project: 'Roassal2'; > > package: 'ConfigurationOfRoassal2'; > > load. > > (Smalltalk at: #ConfigurationOfRoassal2) loadDevelopment > > -=-=-=-=-=-=-=-=-=-=-=-= > > > > Then I loaded S2py: > > -=-=-=-=-=-=-=-=-=-=-=-= > > Gofer new smalltalkhubUser: 'ObjectProfile' > > project: 'S2py'; > > package: 'S2py'; > > load. > > -=-=-=-=-=-=-=-=-=-=-=-= > > > > It works here. > > Can you confirm? > > > > Sorry for having taken long to answer... > > > > Cheers, > > Alexandre > > > > On Sep 24, 2014, at 8:24 PM, Maximiliano Taborda <mtaborda(a)gmail.com> > wrote: > > > > > Hi Alexandre, > > > > > > I want to try Hapao2 to check the coverage level of Chalten, but it's > not working (at least for me). > > > I load Roassal2 and S2py in a fresh 3.0 image like you say and the new > entries appear in the world menu, but the only option that partially works > is the one for a particular class (Hapao @ Class ...) and after run all the > tests (I see the progress showing that) a MNU is raised in the method > #addMethodEdges:scope:view: of Hapa2 class because RTEdgeBuilder is not > loaded. > > > > > > So, could you tell me what I missed please? I need to load another > thing, which?, at least the package which defines RTEdgeBuilder. > > > > > > Thanks for your help. > > > > > > Regards. > > > Maxi > > > > > > 2014-09-16 20:10 GMT-03:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > > > Excellent! > > > > > > Alexandre > > > > > > Le 16-09-2014 Ã 16:15, Tudor Girba <tudor(a)tudorgirba.com> a Ã©crit : > > > > > >> Great! > > >> > > >> I will go over it more thoroughly in the following weeks and get back > to you with feedback. > > >> > > >> Cheers, > > >> Doru > > >> > > >> > > >> > > >> On Tue, Sep 16, 2014 at 6:03 PM, Alexandre Bergel < > alexandre.bergel(a)me.com> wrote: > > >> Dear all, > > >> > > >> We are happy to release Hapao2 for Pharo. Ricard Jacas and Alejandro > Infante put quite some work on Spy2 (an Ã¼ber cool profiling framework for > Pharo) and Hapao2. > > >> Hapao2 is about assessing the test coverage of your code and is a > major revamp of Hapao1, which was presented a couple of years ago by > Vanessa. > > >> Hapao2 does not only list covered and uncovered methods, as most test > coverage tool on Earth will do. Hapao gives a great visualization to easily > navigate in your code, assess its complexity, and give you a great visual > output telling its coverage. > > >> > > >> You need Roassal in your image: > > >> > > >> Gofer new smalltalkhubUser: 'ObjectProfile' > > >> project: 'Roassal2'; > > >> package: 'ConfigurationOfRoassal2'; > > >> load. > > >> (Smalltalk at: #ConfigurationOfRoassal2) load > > >> > > >> > > >> and you need S2py: > > >> MCHttpRepository > > >> location: 'http://smalltalkhub.com/mc/ObjectProfile/S2py/main' > > >> user: '' > > >> password: '' > > >> > > >> > > >> New entries will appear in the world menu: > > >> <Screen Shot 2014-09-16 at 11.49.06 AM.png> > > >> > > >> You can run the test coverage on : > > >> - the class classes you have modified, > > >> - on a particular > > >> - on a particular class category > > >> - on the last class categories you have modified > > >> - on the last packages you have modified > > >> > > >> Here is a portion of a large coverage: > > >> > > >> <Screen Shot 2014-09-16 at 12.00.11 PM.png> > > >> > > >> A technical description of Hapao may be found on > http://bergel.eu/download/papers/Berg12c-HapaoSCP.pdf > > >> > > >> We are daily using Hapao to help us understand our tests. > > >> > > >> Cheers, > > >> Ricardo, Alejandro & Alexandre > > >> -- > > >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > >> Alexandre Bergel http://www.bergel.eu > > >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > >> > > >> > > >> > > >> > > >> _______________________________________________ > > >> Moose-dev mailing list > > >> Moose-dev(a)iam.unibe.ch > > >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > >> > > >> > > >> > > >> > > >> -- > > >> www.tudorgirba.com > > >> > > >> "Every thing has its own flow" > > > > > > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

Oct. 6, 2014

Re: [Pharo-dev] DNUs in the styler

by Marcus Denker

> On 06 Oct 2014, at 17:12, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > > > 2014-10-06 17:06 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>>: > > > On 06 Oct 2014, at 14:29, Thierry Goubier <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: > > > > I'm encountering DNUs in the Styler in Pharo 4.0. Is someone else encountering those as well? > > > > A way to reproduce: > > > > RBParser parseFaultyMethod: 'test ^ ()â > > > > When I execute that I do not get any problems with the styler, but the faulty expression parsing itself fails for > this inputâ¦ > > (dnu #addParenthesis: on the ErrorNode) > > I get the same error in Pharo3. > > Marcus > > I had the setting on "use AST styler" which explains the DNUs. I turned it off so that's solved. > Yes, this is not completely working yetâ¦ we need to do the move and fix all the bugsâ¦ > The sequence above shows that the RBParserErrorNode thing [1] works in some cases and not all. > > Are you planning something in that area? > Planning yesâ¦ but not started yetâ¦ I need to finish other things before. So every contribution is welcome... > Thierry > > [1] encapsulating a syntax error in a RBParserErrorNode so that: styling can happen on a correct part of the code; and that (maybe) parsing can continue. > > >

Oct. 6, 2014

Re: [Pharo-dev] DNUs in the styler

by Thierry Goubier

2014-10-06 17:06 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: > > > On 06 Oct 2014, at 14:29, Thierry Goubier <thierry.goubier(a)gmail.com> > wrote: > > > > I'm encountering DNUs in the Styler in Pharo 4.0. Is someone else > encountering those as well? > > > > A way to reproduce: > > > > RBParser parseFaultyMethod: 'test ^ ()' > > > > When I execute that I do not get any problems with the styler, but the > faulty expression parsing itself fails for > this input... > > (dnu #addParenthesis: on the ErrorNode) > > I get the same error in Pharo3. > > Marcus > > I had the setting on "use AST styler" which explains the DNUs. I turned it off so that's solved. The sequence above shows that the RBParserErrorNode thing [1] works in some cases and not all. Are you planning something in that area? Thierry [1] encapsulating a syntax error in a RBParserErrorNode so that: styling can happen on a correct part of the code; and that (maybe) parsing can continue.

Oct. 6, 2014

Re: [Pharo-dev] DNUs in the styler

by Marcus Denker

> On 06 Oct 2014, at 14:29, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > I'm encountering DNUs in the Styler in Pharo 4.0. Is someone else encountering those as well? > > A way to reproduce: > > RBParser parseFaultyMethod: 'test ^ ()â > When I execute that I do not get any problems with the styler, but the faulty expression parsing itself fails for this inputâ¦ (dnu #addParenthesis: on the ErrorNode) I get the same error in Pharo3. Marcus

Oct. 6, 2014

Re: [Pharo-dev] Font & Theming of GT 'composite rubricText' is weird

by Tudor Girba

Indeed. This looks like a bug. Could you open an issue? Doru On Mon, Oct 6, 2014 at 4:34 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > The font and theme rendering of GT 'composite rubricText' (like when > inspecting Strings) is a bit off, IMHO: > > > The font is different, does not appear in the settings and is not > influenced by the theme. > > Sven > > -- www.tudorgirba.com "Every thing has its own flow"

Oct. 6, 2014

Font & Theming of GT 'composite rubricText' is weird

by Sven Van Caekenberghe

The font and theme rendering of GT 'composite rubricText' (like when inspecting Strings) is a bit off, IMHO: The font is different, does not appear in the settings and is not influenced by the theme. Sven

Oct. 6, 2014

Patch GTInspector>>#printObjectAsAnItem:

by Sven Van Caekenberghe

=== Name: GT-Inspector-SvenVanCaekenberghe.243 Author: SvenVanCaekenberghe Time: 6 October 2014, 4:26:27.106938 pm UUID: c415dc4f-5808-4b0f-99ab-bef45287e5c8 Ancestors: GT-Inspector-AndreiChis.242 Patch GTInspector>>#printObjectAsAnItem: to no longer add a class name when it is already present === I don't think this can be done in Object>>#gtDisplayOn: because of the stream involved. In any case, things look *way* better now ;-) Sven

Oct. 6, 2014

GT-Inspector presentations for Core Zn objects

by Sven Van Caekenberghe

Name: GT-InspectorExtensions-Core-SvenVanCaekenberghe.65 Author: SvenVanCaekenberghe Time: 6 October 2014, 4:20:04.98872 pm UUID: 3f4e93c1-eed7-4769-81c1-9c2ac6c48702 Ancestors: GT-InspectorExtensions-Core-SvenVanCaekenberghe.64 Added multiple presentations for all Core Zinc HTTP Components objects Sven

Oct. 6, 2014