Well, that's just the way I've done it ... Added some inst vars and 
tried to redefine only
the bare minimum ... I think the code is something like 2 classes, and 
15 methods ..
so it's not what we could call huge ;-)...

Romain

On Dec 15, 2004, at 9:35 PM, stéphane ducasse wrote:

> Hi romain
>
> this is cool. Unfortunately I do not have the time to look at it.
> Do you think that subclassing is necessary? Because may be we could 
> change SystemNavigation and
> add a protocol that take into account a context.
>
> Stef
>
>
>> It basically does ;-)
>>
>> I subclassed and overriden a few methods so that SystemNavigation 
>> considers only a list
>> of classes and methods to do it's searches, and it works quite well, 
>> at least for the simple case...
>> You can find that in Services, although it should be separated from 
>> it ..
>>
>> Romain
>>
>> On Dec 15, 2004, at 4:10 PM, stéphane ducasse wrote:
>>
>>>
>>> On 15 déc. 04, at 12:04, Romain Robbes wrote:
>>>
>>>>
>>>> I think this is really doable. I have some code lying around, 
>>>> subclassing SystemNavigation
>>>> to work on part of the system. I use it in my services-base 
>>>> package, to have senders and implementors
>>>> on various parts of the image (package, category, image, and class 
>>>> hierarchy).
>>>
>>> I think that it would be nice that systemNavigation would work on a 
>>> context this way we could build all the cool
>>> browsers and hide complexity.
>>>
>>> Stef
>>>
>>>
>>
>>
>>
>
>