- Pharo-dev - lists.pharo.org

[Pharo-project] Making pharo more tdd oriented
by Hernan Wilkinson June 19, 2009

June 19, 2009

Hi, I have made some changes to pharo to make it more tdd oriented. I want to share them with you to know your opinion and then make the code public. The changes I made are: 1) When there is an error, the debugger opens directly. Reason: I found that I always press Debug when an error occurs in the Notifier window. Question: Should this option be a preference? 2) The debugger opens in a big window. Reason: I always want to debug! and I want to see as much as possible when debugging. Before I found myself making the debugger window bigger all the time 3) When compiling a method that sends a message not defined, it does not ask anymore if I want to change it. Reason: When doing TDD we work top-down, so we are always sending messages that are not defined and that we are going to define when running the test. Question: Should this option be a preference? 4) I added an option to save and run the test from the code pane of the omni browser (ctr+t). If the test fails, opens a debugger to fix it. Reason: It is very handful 5) I added an option to save and step a test from the code pane of the omni browser (ctrl+r). Reason: It is very handful (Problem: The debugger does not work well with breakpoints...) 6) I added a debugCase: message to TestResult and make some changes to the omni browser to show the result of debugging a test. Reason: Before, when debugging a test the browser was showing the test as not runned. 7) When running a test, the defualtAction of the MessageNotUndertood exception will ask you if you want to implement the method (if the receiver is not nil) so you don't have to select that option from the debugger stack list menu. Reason: When running a test 95% of the time a message not understood will be implemented and answering yes or no is easier that going to the stack menu of the debugger to select the option implement. What do you think? Comments welcome. Bye, Hernan.

9 12

[Pharo-project] Strange bug...
by StÃ©phane Ducasse June 19, 2009

June 19, 2009

Hi guys Even if ObjectTracer may be broken when we evaluate (ObjectTracer on: Display) flash: (50@50 extent: 50@50) and try to understand the problem in the debugger, I get only decompileCode then when I navigate the stack I have even syntax error.... Stef

1 0

[Pharo-project] New Extensible Inspector for Pharo-Core
by Frederic Pluquet June 19, 2009

June 19, 2009

Hello, I worked on a new extensible inspector for Pharo (written without OB and so usable directly in Pharo-Core). This tool is based on a tree view of objects in which children can be dynamically extended by simple message overriding. Actions per object menu can be also defined dynamically. A definition panel shows a description of the selected object in the tree. A bottom right pane permits to evaluate some code (in which self is bound to the selected object in the tree). You can load the code from SqueakSource (NewInspector project). See the class extensions (CompiledMethod, OrderedCollection, Set, Dictionary for the moment) to know how to incorporable your needs. It is a stable but very young version (I started to code yesterday evening ;)). Any feedback is welcome :) FrÃ©d ---- FrÃ©dÃ©ric Pluquet UniversitÃ© Libre de Bruxelles (ULB) Assistant http://www.ulb.ac.be/di/fpluquet

8 32

[Pharo-project] Monticello merge tool fail - need strikethrough for deleted code - be friendly to red-green colour blind people!
by Oscar Nierstrasz June 19, 2009

June 19, 2009

Hi Folks, While updating the Monticello chapter of Pharo By Example to the current Pharo GUI, I discovered that diffs in the merge tool (and elsewhere) no longer show deleted code struck through, but only in red, with new code in green. This is a major fail for colour blind people! It also does not show when printed in grey-scale. Can we have the strike-through back? It is an important visual cue. - on

3 2

[Pharo-project] how do I rename a package?
by Oscar Nierstrasz June 19, 2009

June 19, 2009

I discovered to my astonishment that there is no contextual menu item in either the MC browser or the OB system browser to rename a package! I know how to move all classes and methods from one package to another programmatically, but shouldn't there be a way to rename a package? http://scg.unibe.ch/wiki/faq/pharofaq/howToMoveCodeBetweenPackages Couldn't figure out how to do this. - on

3 3

[Pharo-project] NewInspector
by Alexandre Bergel June 19, 2009

June 19, 2009

Hi! When I right-click in the workspace panel of a newinspector I get a rollback 'The getMenuSelector must be a 1- or 2-keyword symbol' Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 1

[Pharo-project] idea to have a better methodFinder :)
by StÃ©phane Ducasse June 19, 2009

June 19, 2009

Hi the methodFInder hard codes the methods that should not be executed. Now with pragma we should be able to have a fully dynamic method finder where nothing is hardcoded. If somebody wants to give a try it would be great because MF is a cool tool. Now too static. Stef

7 10

[Pharo-project] MIT ScaledDecimal (Issue 816) has not been integrated correctly
by Nicolas Cellier June 19, 2009

June 19, 2009

in update10307 (script385) related to http://code.google.com/p/pharo/issues/detail?id=816 : ScaledDecimal2-Part1-nice.1.cs had a postscript to mutate old instances to new instances and not losse existing ScaledDecimals (at least the literals in ScaledDecimalTests). This has not been applied, so some ScaledDecimal now have a nil numerator and denominator. This makes some tests fail. Cure: detect and recompile these methods having a broken ScaledDecimal literal. I don't have time to give a code snippet by now... Nicolas

2 3

[Pharo-project] Can not make the right mouse button work
by Hernan Wilkinson June 19, 2009

June 19, 2009

Hi, in the latest image I can not make the right mouse button work.... Preferences swapMouseButtons returns false as in the previous image that worked... any idea? Thanks, Hernan.

3 5

[Pharo-project] BlockContextTest
by Gabriel Cotelli June 19, 2009

June 19, 2009

Hi, I'm looking the failing tests... some tests defined in BlockContextTest relies on behavior not implemented in BlockClosure (but implemented in the old BlockContext)... If the only senders of this methods are in this test cases can I remove them? If I don't miss anything BlockContext should not be used anymore... Waiting for your comments... Gabriel

5 6