Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!uwm.edu!uakari.primate.wisc.edu!ames!coherent!next!jadams
From: jadams@next.com (Jayson Adams)
Newsgroups: comp.sys.next
Subject: Re: What exactly is the docView of an IB ScrollView?
Summary: Using the IB ScrollView (or not)
Message-ID: <88@next.com>
Date: 6 Jan 90 03:49:47 GMT
References: <219@toaster.SFSU.EDU>
Organization: NeXT Inc., Palo Alto
Lines: 19

In article <219@toaster.SFSU.EDU>, eps@toaster.SFSU.EDU (Eric P. Scott) writes:
> I want to replace the docView with a Text subclass.  There are
> some things I can't do with a delegate, and IB doesn't let me
> specify the class of the docView (grr).

> Next dumb question: am I better off freeing the Text and newing :-)
> a replacement (as Yap does), or avoiding IB's ScrollView
> altogether in favor of a ScrollView-flavored CustomView?

You might just want to avoid the IB ScrollView.  You can force a
CustomView to be a ScrollView (or any other View class IB knows about)
with the Inspector's Attributes panel.  Without the IB ScrollView,
your program should start faster 'cause you avoid creating a Text
Object that you're just going to throw away.  This solution might take
more work, though, 'cause it looks like you can just modify the Yap
code.  Hope this helps.

Jayson Adams
NeXT Developer Support