Hi tim

I remember you position and you fix for Plugin :) When I sa the way you 
did it I found the solution elegant. Now I would like to see how 
SystemNavigation can handle it if possible.
This is just that I'm flooded.

Stef


On Tuesday, August 12, 2003, at 07:23 PM, Tim Rowledge wrote:

> Roel Wuyts <wuyts at iam.unibe.ch> wrote:
>
>> I was too quick in replying, so I replied to your first mail. I wanted
>> to sketch some of the context for these decisions from my point of 
>> view.
>>
>> Again, I'd like some views from other people.
> I've already offered suggestions and criticisms very similar to 
> Andreas'
> in previous exchanges. I prefer a singleton/global becasue it just 
> feels
> better and saves some mental space when typing and reading. As for
> messages like #allCallsOn:, I'd keep them in classes and delegate to
> SystemNavigation _when appropriate_. Remember the suggestions I made 
> for
> refactoring class refernce browsing? That worked by letting the classes
> override the message so that Plugin classes could add more searching 
> and
> cope with the way that plugin primitives are called.
>
>
> tim
> --
> Tim Rowledge, tim at sumeru.stanford.edu, http://sumeru.stanford.edu/tim
> Useful random insult:- A 20th century man...  The guy has no future.
>