Hi Johan,

> We found you have implementation of an OB-Debugger in your omnibrowser repo.

Yes, in the package OB-Tools there are functional implementations of
debugger, filesystem browser, object browser (inspector), process
browser, workspace, and transcript.

> Could you comment to us what is the state of that code?

I haven't looked into the code lately, so it might be slightly out of
sync with the current OmniBrowser code. The code was functional and
provided about 90% of the functionality the original Smalltalk-80
tools provided.

At the time the tools were built they were notably slower than the
original tools. I doubt that that this is still a big problem, because
the meta-model has seen various major optimizations.

The worst thing about the code is that there are no tests. There is no
excuse for that. This is plain bad.

> Is there a newer version?

Not that I know. Dale from GemStone had been working on the tools for
a while, but I think all his changes are in my repository.

> Does it makes sense for us to pick up the project and see what we can do with 
> it?

I think that would be beneficial. Imagine we could extend our
debuggers and inspectors the same way as the browsers.

Lukas

-- 
Lukas Renggli
www.lukas-renggli.ch

_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to