On Mar 9, 2004, at 2:18 PM, Avi Bryant wrote:

>
> On Mar 9, 2004, at 10:53 AM, Alexandre Bergel wrote:
>
>> When do you replace the standard classbrowser by Colin's ?
>> Let's do the jump!
>>
>> Ok, I was really provocative. But I thing we should not be afraid by 
>> that and we should start to think about.
>
> There's no need yet to worry about which the "standard" browser is.  
> Let me propose an equally effective jump: why don't a bunch of us make 
> a pact to start using the OmniBrowser as our default browser for any 
> development?  Obviously we'll run into missing features, but we'll 
> just add them as we need them.  It really shouldn't take long before 
> the browser is ready for prime time.

This sounds like a good strategy to me. I've been doing it for a while, 
and find it surprisingly practical.

To make it a bit easier, I'll add a "view in standard browser" command 
that will open a standard browser to the same class or method. That way 
making a "detour" out to the regular tools for a missing feature won't 
be so painful.

Colin