Re: [Pharo-project] Inclusion of OB-Tools inside Pharo

2008-12-22 Thread Matthias Berth
Hi Damien, I'm glad you started this discussion of OB-Tools. I have filed two issues that were more or less show-stoppers for me when using the new default OTDebugger included in the current pharo-dev: - Method source snippets cannot be evaluated in Debugger (OB Tools OTDebugger) http://code.g

Re: [Pharo-project] Inclusion of OB-Tools inside Pharo

2008-12-22 Thread Stéphane Ducasse
I was not questioning the presence of RB engine Now people can join to help improving. Gwenael is cleaning the parser and scanner for example > Stef, > > One nice thing about the new browser is the RB integration. Given my > general aversion to having it rewrite my code (showing no respect at >

Re: [Pharo-project] Inclusion of OB-Tools inside Pharo

2008-12-22 Thread Bill Schwab
David, The glaring examples are probably comments in cascades. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bsch...@anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> pennell.da...@gmail.com 12/22/08

Re: [Pharo-project] Inclusion of OB-Tools inside Pharo

2008-12-22 Thread David Pennell
Bill, Can you give an example of the kind of comments that RB doesn't respect for you? I've used RB extensively on VW, but not much at all on Squeak yet. It had problems with end of line comments, but didn't do badly with comments on there own line. I adopted to its limitations rather than try t

Re: [Pharo-project] Inclusion of OB-Tools inside Pharo

2008-12-22 Thread Bill Schwab
Stef, One nice thing about the new browser is the RB integration. Given my general aversion to having it rewrite my code (showing no respect at all for the dated comments therein), I'm an unlikely advocate. Still, I use the RB for up/down refactorings (no rewrites needed), and will sometimes tur

Re: [Pharo-project] Inclusion of OB-Tools inside Pharo

2008-12-22 Thread Stéphane Ducasse
I think that we should pay attention of the ratio of effort and number of people participating. My take would be to not include tools if they are not complete and at the same time may be create a group of people working on an specific issue for the next milestone. In the long run I would like to

Re: [Pharo-project] Inclusion of OB-Tools inside Pharo

2008-12-22 Thread Michael Roberts
I'm interested at least in a discussion on the OB debugger. This is because 1) there are definitely some bugs in the core debugger. Is it worth trying to fix them? I think yes, but I'm not sure I have the skills to identify and fix them. I just know from using the core debugger it sure does som

[Pharo-project] Inclusion of OB-Tools inside Pharo

2008-12-22 Thread Damien Cassou
On Sun, Dec 21, 2008 at 11:44 PM, Bill Schwab wrote: > Sounds good. And in that case (OB Tools at the end of the list), I urge > serious attention to having a notifier. Learning from history, and all > that. Hi Bill, I decided to load OB-Tools (a reimplementation of some tools using the ob fra