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.google.com/p/pharo/issues/detail?id=421 - Button 'over' produces error in OTDebugger http://code.google.com/p/pharo/issues/detail?id=422 I'd like to help, but frankly I would not know where to start, e.g. learning about what happens when I step through a method. Cheers Matthias On Mon, Dec 22, 2008 at 11:00 AM, Damien Cassou <damien.cassou@gmail.com> wrote:
On Sun, Dec 21, 2008 at 11:44 PM, Bill Schwab <BSchwab@anest.ufl.edu> 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 framework) inside the pharo-dev images. I put OB-Tools inside the list of packages that will be part of the official Pharo distribution. This was a mistake because no discussion happened about this package at all on this mailing list. I've just moved OB-Tools to the list of pending packages. Now, we have to discuss (in this new thread):
- Do we want an OB-based version of the tools inside Pharo? - Do we want all tools implemented by Lukas or just some of them? - What features are missing? - What are the bugs? - Who maintains this package?
-- Damien Cassou http://damiencassou.seasidehosting.st
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project