smb@datran2.uunet (Steven M. Boker) (08/04/89)
Does anyone know why the Browser and BrowserScroll classes aren't
documented? These two classes seem to me to be essential elements
of many of the distributed NeXT Applications. I have built a
scrolling SelectionCell Matrix as a workaround, but it seems silly
to have to re-invent the browser, so to speak.
Interface Builder has an inspector panel for the Browser class. If
you load the nib file for the OpenPanel or FontPanel you can see it.
You can even use Interface Builder to copy the Browser from the
OpenPanel into your own application. This application will compile
and link and running gdb gives me a list of the Browser and BrowserScroll
methods.
Its all there... WHY NO DOCUMENTATION?
Bemused,
Steven M. Boker
smb@datran2.uunetstone@grumpy.cs.unm.edu (Andrew Stone) (08/07/89)
In article <410@datran2.uunet> smb@datran2.uunet (Steven M. Boker) writes: >Does anyone know why the Browser and BrowserScroll classes aren't >documented? These two classes seem to me to be essential elements >of many of the distributed NeXT Applications. I have built a >scrolling SelectionCell Matrix as a workaround, but it seems silly >to have to re-invent the browser, so to speak. From email with ali and bruce, I gather that this class was still in too much flux in .9 to be granted public class status. There will be a "ClipView" class in 1.0 that will probably do what you need. But didn't you learn a lot about prototypes and other cell trivia during the reinvention? andrew ||<<++>>||<<-->>||<<==>>||<<++>>||<<??>>||<<++>>||<<-->>||<<==>>||<<++>>|| !! Andrew Stone !! the fictive milieu of !! !! stone@rye.cs.unm.edu <> contemporary society! !! ||<<++>>||<<-->>||<<==>>||<<++>>||<<??>>||<<++>>||<<-->>||<<==>>||<<++>>||
ali@polya.Stanford.EDU (Ali T. Ozer) (08/07/89)
In article <268@unmvax.unm.edu> stone@grumpy.cs.unm.edu () writes: >In article <410@datran2.uunet> smb@datran2.uunet (Steven M. Boker) writes: >>Does anyone know why the Browser and BrowserScroll classes aren't >>documented? > From email with ali and bruce, I gather that this class was still in > too much flux in .9 to be granted public class status. That's right. Please don't try to use the Browser class using information gleaned from the executables or IB as the interface, implementation, and various side-effects & such are all likely to change. You might also run into a few problems, discovering the hard way the reasons why the class isn't public yet. Ali Ozer, NeXT Developer Support aozer@NeXT.com