Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!gatech!cica!iuvax!ndcheg!ndmath!milo
From: milo@ndmath.UUCP (Greg Corson)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Sublaunching (really user extendable programs)
Message-ID: <1531@ndmath.UUCP>
Date: 14 Aug 89 16:20:03 GMT
References: <30610@ucbvax.BERKELEY.EDU>
Organization: Math. Dept., Univ. of Notre Dame
Lines: 31

From article <30610@ucbvax.BERKELEY.EDU>, by oster@dewey.soe.berkeley.edu (David Phillip Oster):
> Greg, you should definately get a copy from APDA of the docuementation for
> Apple's Communication Toolbox, since it gives an Apple sanctioned standard
> for doing exactly what you want to do.  You should read Inside Macintosh,
> particularly the Package Manager chapter. Here is what you do:
> You create your applications as files containing resources, including
> code resources of a private type, (i.e., not PACK).  Your frame
> application opens the file, loads, MoveHHi()s and calls the resource,
> passing it a pointer to a record of global variables, including a slot for
> it to put a handle to its own storage, and a vector of call back
> procedures so the satellite can call the core program for services like
> actually reading and writing data from the port.
> 
I have only one small problem...the "satelite" programs are likely to be
quite large, need their own set of globals...etc.  At least one of the 
programs which I would LIKE to make into a satelite is already 93k (as a
stand alone) contains a number of segments and occupies nearly 512k when
running.

The system you describe sounds like it would work ok if the satelites were
smaller (single segments) but I need the ability for a satelite to be
potentially as big as a commercial game or utlitiy program.

Any more comments?

Greg Corson
19141 Summers Drive
South Bend, IN 46637
(219) 277-5306 
{pur-ee,rutgers,uunet}!iuvax!ndmath!milo