🚀 go-pugleaf

In article <1784@drivax.UUCP>, socha@drivax.UUCP (Henri J. Socha (x6251)) writes:
> >In article <1118@csib.UUCP>, jwhitnel@csib.UUCP (Jerry Whitnell) writes:
>    [in Lightspeed C]
> >> I just hit cmd-R, with 15 seconds and I'm in my application.
> 
> >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...
> 
> 
> For a definite answer,  yes  AND  no!
> 
> 
> It is a single file but in its normal state it can not be double clicked 
> and run.  The programme runs UNDER Lighspeed C  (sub-launch) and when it
> terminates, LSC come back.  Now, that's the NO.
> 
> There is a menu option to make a TRUE double-clickable application
> (also DA, code library, and more).  When this is done, a seperate file
> is created which is the executable version.  It is EXACTLY the same except
> the internal controls for symbol table/project/make/etc. information have
> been removed.  Also modules that are not necessary have been removed.
> (i.e. intelligent linker functions.)  Therefore it is now independent of
> LSC, a full app.  Therefore YES (with qualifications), you must go through
> this seperate step to make a double-clickable app.  NOTE: the time to generate
> this app is about the same as the <cmd> R time till running.
> (Time it takes to read the project and write the app., almost no processing
> overhead, its minimal.)
> 
> Note: I've heard mention (not tried) that double clicking with <cmd> <option>?
> down (forced execution) will run a LSC project.  So, in one unusual sense
> (if this is true), by changing the Creator-Type words you can actually
> convert the LSC project to a runnable application.  
> (Another qualified YES answer.)
> 
> 
An application refers either to a stand alone application (which may be double
clicked from the Finder or launched via the _Launch trap) or to desk
accessories, definition procedures, or any other type of code resource.

I did try to launch a LSC project via the forced launch mechanism
(cmd-opt-dlb click) and one of my applications did launch (though it
crashed later through no fault of LSC).

Also the idea of needing a similar hardware/memory configuration of the machine
that the application was built on and the application is run on is not
valid.  You can build an application on a 5Megabyte Macintosh II with a
80MByte hard disk and run it on a Macintosh 128K - provided that you follow
the rules (i.e. do not use too much memory for target machine, make 
calls that are not supported on the target machine, etc etc etc)


=====================================================================
Byron Han            |   UUCP:  {sun,voder,nsc,mtxinu,dual}!apple!han
Apple Computer, Inc. |  CSNET: han@apple.csnet 
20525 Mariani Ave,   | ATTNet: 408-973-6450
Cupertino, CA 95014  |  GENIE: BYRONHAN
MS 27Y               | CSERVE: 72167,1664
=====================================================================
All opinions and statements do not necessarily represent those of my
employer, Apple Computer Inc.
=====================================================================