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

Michael Roberts mike at mjr104.co.uk
Mon Dec 22 05:30:01 EST 2008

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 some strange things.
2) The core debugger is missing features: stack variables, arguments,
breakpoints.  How hard is it to modify the core one?
3) do we have enough volunteer effort to maintain two debuggers? I'm
not sure we do.

I have only briefly used the ob debugger and I got a bit confused with
part of the UI so i'll need to look at it some more.  What are folks
thoughts on this key part of functionality?

Then more generally i'm not sure it makes sense to have different
tools in the core vs the dev image.  I have to admit to not fully
understanding the 1.0 release plan but looking fwds to say 2.0, 3.0
there would be benefit from pushing OB + tools into the core and just
maintaining a single high quality set of tools across all variant



On Mon, Dec 22, 2008 at 10:00 AM, Damien Cassou <damien.cassou at gmail.com> wrote:
> On Sun, Dec 21, 2008 at 11:44 PM, Bill Schwab <BSchwab at 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 at lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

More information about the Pharo-dev mailing list