On Fri, Jun 19, 2009 at 7:32 AM, Stéphane Ducasse <[email protected] > wrote:
> I should say that I hate the popups "do you want to do that or remove > this variable but wait it is assigned tooo." > > May be we should have a menu > clean code! > but for now let is accept it I agree with that. When coding I do not pay to much attention to those things because after I'm done (or I thing the code is stable enough) I run SmallLint to fix all those things.... When I'm coding I want to be as fast as possible... of course, not everybody has to agree with this. > > > > 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? > > I'm not sure in fact because when you are not in TDD you just often > close the predebug. > but we could change. But what is the difference with closing the debugger? I worked with VisualAge that does not have the notifier and now with pharo/squeak I feel the notifier bothers me... > > > > 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 > > larger but not to big :) > > > 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? > > No preference. Now if the system could guess typos :) > > > > 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 > > Yes right now when you do alt-t you run the test but you cannot get a > debugger on them. Yes, but alt-t is if the focus is on the method list (or category list or class list or package list). The option I added is when the focus is in the code panel > I would love to > click to run the tests > get a small widgets with the result of the execution and that I can > rerun or get a debugger on the tests. I did this: 1) you write the test 2) when done, press ctr+t (I could not make alt+t) work... 3) It will not ask you for bad selectors (your are doing tdd, so you are sending messages that are not implemented) 4) It will save the method 5) Run the test. If it runs ok, the green button will appear on the method list 6) If it fails or err, the yellow/red button will appear on the method list and the debugger will open 7) If you fix the error, go to 3 :-). I think it is very helpful and agile. If you want to steep the test, just press ctrl+r > > > > 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. > > in Squeak we could show the class and its superclass. Yes, but I found that I always implement the method in the class not in any of it superclasses... Anyway, I know it is not easy to satisfy everybody... I'll publish the code in squeak source so everybody can try it and give me feedback and make it better. Bye, Hernan. > > > > > > What do you think? Comments welcome. > > Bye, > > Hernan. > > > > > > > > > > _______________________________________________ > > Pharo-project mailing list > > [email protected] > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
