- Pharo-dev - lists.pharo.org

[Pharo-project] Fuel out stack... other error
by phil＠highoctane.be Feb. 19, 2013

Feb. 19, 2013

I put a new istead of newFull and continued. No, I get some FuelMetalevel thing...

2 1

[Pharo-project] Fuel Out Stack: MNU in 20555
by phil＠highoctane.be Feb. 19, 2013

Feb. 19, 2013

Tried to FileOut stack from a debugger. FLSerializer class>>newFull - MNU ? Phil

2 1

Re: [Pharo-project] Phexample should methods
by Adrian Kuhn Feb. 19, 2013

Feb. 19, 2013

On Feb 10, 2013, at 12:37 PM, Stefan Marr wrote: > That gives rise to example-driven testing ala: > > Foo >> #barShouldBeSomething > > So far, I tried to avoid that, and make examples that are really focused on one specific subject, which is represented by the class name. > > Any opinions on that? Classes and methods are not the best model to structure tests. Alas in Smalltalk it's all we can work with. Other than Ruby we cannot break free from classes and methods (imposed by the Smalltalk IDE rather than the language) so its what we must work with. Personally I like to have a 1:1 mapping between classes and "test classes" as in Stack and StackExamples and then use "test method" names to describe the examples. And then other "test classes" with more complex use cases that cover features involving more than one class. I am not sure if we ever implemented the following idea, but I seem to recall that I used to name some of my "methods" inside the "example classes" with names such as #givenAnEmptyStack or #givenAStackWithTwoElements and then sending these to create the fixture in the "test methods" #shouldAddElement or #shouldFailWhenPoppingFromEmptyStack etc ... Essentially, everything you ever type and evaluate in a workspace should be turned into an example, see http://qr.ae/10yZR Think of it, having a "save as example" menu item available on *every* text selection in the system would be so awesome! > PS: It is also inconsistent with Phexample's own #isTest: implementation, which uses #beginsWith: Oops, that's a bug, #theMoreGeneralCaseShouldApply :) Even though personally I prefer to not use should inside the name in order to limit the pollution for the selection name space with regard to Smalltalk's simple autocomplete ... --AA

3 3

[Pharo-project] [update 2.0] #20555
by Esteban Lorenzano Feb. 19, 2013

Feb. 19, 2013

20555 ----- Issue 7521: Add PostMaterializationAction to Fueled out stack traces http://code.google.com/p/pharo/issues/detail?id=7521 Issue 7532: Integrate a preview of Fuel 1.9 http://code.google.com/p/pharo/issues/detail?id=7532 2nd attempt :) Diff information: http://ss3.gemstone.com/ss/Pharo20/FuelSystem-FileRegistry-EstebanLorenzano… http://ss3.gemstone.com/ss/Pharo20/Fuel-EstebanLorenzano.746.diff

1 0

[Pharo-project] [update 2.0] #20554
by Esteban Lorenzano Feb. 19, 2013

Feb. 19, 2013

20554 ----- Issue 7521: Add PostMaterializationAction to Fueled out stack traces http://code.google.com/p/pharo/issues/detail?id=7521 Issue 7403: CMD-click no longer works to activate source-links http://code.google.com/p/pharo/issues/detail?id=7403 Issue 7532: Integrate a preview of Fuel 1.9 http://code.google.com/p/pharo/issues/detail?id=7532 Diff information: http://ss3.gemstone.com/ss/Pharo20/Tools-EstebanLorenzano.1044.diff http://ss3.gemstone.com/ss/Pharo20/Morphic-EstebanLorenzano.1353.diff http://ss3.gemstone.com/ss/Pharo20/HudsonBuildTools20-EstebanLorenzano.25.d… http://ss3.gemstone.com/ss/Pharo20/FuelTests-EstebanLorenzano.306.diff http://ss3.gemstone.com/ss/Pharo20/Fuel-EstebanLorenzano.744.diff

1 0

[Pharo-project] Migrated SS/Growl to Pharo/Archive
by StÃ©phane Ducasse Feb. 19, 2013

Feb. 19, 2013

Hi guys since growl has been integrated to Pharo I migrated the SS project to the Pharo/Archive one. Stef

4 6

[Pharo-project] Smalllint for Traits
by aizcorbe Feb. 19, 2013

Feb. 19, 2013

Hi all, as part of a thesis I have been working on, I extended Smalllint to let it check Traits and Traits specific errors. The enviroment objects and the refactoring scope browsers now handles and list classes and traits (before they just handled classes). The new refactoring scope selection is available at "refactoring scope>selection all behaviors" menu option. The smalllint framework have been extended and is available at "refactor>code critics extended". These are some of the changes: smalllint rules can now check traits and traits methods. a new rule presentation schema is available, which lets to spot the place where the error is actually located and also add extra information to the rule result (but is more difficult to define the rules in this way). For extra information about the changes and how can they be used you can refer to: http://dc.uba.ar/inv/tesis/licenciatura/2012/aizcorbe.pdf (refer to chapter 4 if you want to bypass all the conceptual background ) there was also added some rules to check Traits specific errors. The Smalllint for Traits extension is available for pharo 1.3 and is located in: http://www.squeaksource.com/TesisTraitLint the packages are organized as follows: OBLintTraitExtension.1.3 (the smalltalk environment extension to add Traits handling capabilities). TraitLint.1.3 (the Smalllint extension itself and the Traits rules implementation). TraitLintTest.1.3 (the unit tests for the Smalllint extension and the rules implementation, it is not mandatory). I hope you find this useful. cheers -- View this message in context: http://forum.world.st/Smalllint-for-Traits-tp4662559.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

6 10

[Pharo-project] Magritte3 in Pharo 2.0
by DeNigris Sean Feb. 18, 2013

Feb. 18, 2013

I was pleasantly surprised that Magritte loaded without any hiccups :) The only failing tests seem to be related to: - includesSubString: -> includesSubstring: - time printing w/without milliseconds - FileDirectory Cheers, Sean

1 0

[Pharo-project] [update 2.0] #20553
by Esteban Lorenzano Feb. 18, 2013

Feb. 18, 2013

20553 ----- Issue 7504: Creating a new class does not mark the package as Dirty http://code.google.com/p/pharo/issues/detail?id=7504 Issue 7480: [Cleanup]: #giveFocusToXyzFrom: arg name http://code.google.com/p/pharo/issues/detail?id=7480 Diff information: http://ss3.gemstone.com/ss/Pharo20/Spec-Widgets-EstebanLorenzano.103.diff http://ss3.gemstone.com/ss/Pharo20/Spec-Core-EstebanLorenzano.86.diff http://ss3.gemstone.com/ss/Pharo20/Monticello-EstebanLorenzano.773.diff

1 0

[Pharo-project] Fwd: [INRIAGForge] February 26th 2013: Scheduled downtime from 8 am to 9 am
by Marcus Denker Feb. 18, 2013

Feb. 18, 2013

Begin forwarded message: > From: <noreply(a)gforge.inria.fr> > Subject: [INRIAGForge] February 26th 2013: Scheduled downtime from 8 am to 9 am > Date: February 18, 2013 5:38:42 PM GMT+01:00 > To: marcus.denker(a)inria.fr > > Due to scheduled maintenance, the INRIA Forge will be unavailable from 8 am to 9 am on Tuesday, February 26th 2013. > > The InriaForge team apologizes for any inconvenience. > > ================================================================== > You receive this message because you subscribed to INRIAGForge > site mailing(s). You may opt out from some of them selectively > by logging in to INRIAGForge and visiting your Account Maintenance > page (https://gforge.inria.fr/account/) or disable them altogether > by visiting following link: > <https://gforge.inria.fr/account/unsubscribe.php?ch=_9e77f42c8de73f76>

1 0