🚀 go-pugleaf

In article <729@unccvax.UUCP> cbenda@unccvax.UUCP (carl m benda) writes:
<My question then becomes:  Is this "application" a single file which I can
<then bring to any unsuspecting mac, see the applications icon in the finder,
<double click on the icon and then have it run in the manner in which it did
<on the system I developed it on, assuming of course similar memory and 
<other hardware configurations were taken into consideration while creating the
<application...

No.  That will take an additional five seconds to build the applicaton,
and whatever it takes to create an icon.  You don't need any of this
during development, which is the slow part.

Here's how it works with LightspeedC:

	1:	Start up Switcher

	2:	Start LightspeedC version >= 2, and open your project

	3:	Edit files

	4:	issue the run command

	5:	10 or 15 seconds later your application appears
		running in another switcher partition ( sort of ).

	6:	if you don't want to see any more, GOTO 9

	7:	switch to LightspeedC and look at your source
		code to try and figure out what is going wrong.

	8:	switch back to your program.  GOTO 6

	9:	If more work to do, GOTO 3

	10:	Select "build application", and wait about 5 seconds.

The main slowness comes from the fact that the Mac has no MMU.  You have
to insert one more step in the above:

	5.1:	Your program crashes the Mac.  Reboot, GOTO 1.

If you have TMON running, you can often select "relaunch current application",
or "relaunch finder" to save having to reboot, or if you do have to reboot,
you can at least get TMON to unmount all volumes first, so you don't wait
forever for the system to rebuild things when you boot.
-- 
Tim Smith			"Well if you want to say yes, say yes
{seismo,sdcrdcf}!ism780c!tim     And if you want to say no, say no
				'Cause there's a million ways to go
				 You know that there are"