On 2011/04/25 16:24, Balázs Kósi wrote:
> Hi,
>
> Similar to the previous problem: you get debuggers when you delete a
> class, with a method of it selected.

Thanks, Balázs. It's the same bug, in a way: "things go wrong when the 
class we were browsing isn't there anymore." Tools-fbs.344 tries to 
address the problem more directly, by making the Browser treat a missing 
class like having no class selected.

These bugs are manifesting because of poor test coverage, because the 
tests are difficult to write. I don't want to actually install new 
classes in global structures just to test the Browser (although I must 
admit I haven't looked at what Monticello does - maybe it does exactly 
this?).

What I'd like is to define a minimal interface between Browser and its 
currently implicit dependencies. Like, for instance, how Browser depends 
on Smalltalk, Preferences and other global things. It starts to sound 
like I'd like to have a Newspeak-like explicit parameterised Browser...

frank