Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!caesar.cs.montana.edu!ogicse!orstcs!mist!jasmerb
From: jasmerb@mist.cs.orst.edu (Bryce Jasmer)
Newsgroups: comp.sys.next
Subject: Re: NeXT Browser Info
Message-ID: <14556@orstcs.CS.ORST.EDU>
Date: 28 Dec 89 18:42:17 GMT
References: <158@csi2.UUCP>
Sender: usenet@orstcs.CS.ORST.EDU
Reply-To: jasmerb@mist.CS.ORST.EDU (Bryce Jasmer)
Distribution: na
Organization: Oregon State Univ. -- Computer Science
Lines: 31

In article <158@csi2.UUCP> john@csi2.UUCP (John Kowalski) writes:
>Hello all you Browser fans (I don't know if someone else posted this
>info here, I don't read this group often enough) I found what most
>people writing software would like to have: A Browser Class.
>
>Well first be aware that this is not documented yet and that the
>interface may change when published (if published). This info is
>only method names. I fell on this while writing my own class named
>"Browser" and finding that it looked to good to be mine. Obviously I
>looked around in the libNeXT shared library and Presto! the Browser Class.
>
>these are the methods, getting them to work is left as an exercise :-)

Great idea. I wanted to take this a little bit further so I started mucking
around with InterfaceBuilder. I wanted to extract the nib file from IB
and see what is going on when they use a Browser (if it installed in
a Window, etc.)

I used "size -m" on IB and found there were tons (35+) different nib
files. Much to my joy, I found there was a "BrowserInspector__NIB"
section. I used fsectbyname to extract it and when I tried to open
it, an error came up "Can't open file". Is this because InterfaceBuilder
was created with an older version of InterfaceBuilder and so couldn't 
open its older nib files?

This was a little bit of a dissapointment. Anyway, I will keep on plugging
away on trying to decipher the Browser class. If anyone makes any progress
please let us all know.

Bryce Jasmer
jasmerb@cs.orst.edu