Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!pacbell.com!iggy.GW.Vitalink.COM!widener!netnews.upenn.edu!eniac.seas.upenn.edu!gasser
From: gasser@eniac.seas.upenn.edu (Nathan Gasser)
Newsgroups: comp.sys.mac.hypercard
Subject: LARGE text fields
Message-ID: <41534@netnews.upenn.edu>
Date: 19 Apr 91 14:44:32 GMT
Sender: news@netnews.upenn.edu
Reply-To: gasser@eniac.seas.upenn.edu (Nathan Gasser)
Organization: University of Pennsylvania
Lines: 30
Nntp-Posting-Host: eniac.seas.upenn.edu



I'm making a few stacks which require *lots* of text (4.6 Mb on one)
and I desparately want to use HyperCard and not resort to some less 
cool environment.  

As of now, I spool my big document into 32k fields, making new cards 
as necessary.  I'm not sure if I should split the stack or keep it
as one.  There's something aesthetically (?) unpleasing about a 5 Mb stack,
but if I split it, I'll  have trouble searching for things, and updates
to the controlling software will have to be done to all the stacks I
split it into.

Is there a better way?  Is there a way to isolate the "features" handlers
(menus, search features, various hypermedia aids) from the bulk
text, so I'll only have one copy to update?


On a related subject, how good is Guide, by Owl?  I can't find it in
catalogs.  Anyone have a price?  Is this maybe what I need to get this 
stuff done?

Any and all comments appreciated, 

	Nate.

 
--
Nathan Gasser
gasser@eniac.seas.upenn.edu