The answer lies in the terminology I think. If you have a stack file that contains a main stack and several substacks, then all of them are compiled into the standalone. On the other hand, if you are using the so called "splash screen" approach that has one stack file with a main stack that then launches another stack file, then the standalone will only include the splash screen stack and the other stacks will not be compiled.
If you are on a Mac, you can verify this by right clicking your standalone in the Finder and selecting "Show Package Contents" and looking at the contents of the MacOS folder. The main usage for the splash screen approach seems to be that you can store data in the stacks in the other stack file, whereas you cannot store data in a stack within a standalone. If I remember correctly, you are using an SQL database so I'd guess you probably aren't using the splash screen approach. The other thing to remember is that, if your stacks are password protected, then not only can people not access the scripts without the password but many other things are encrypted (e.g. custom properties). You can still see them OK in the IDE but unless your customers own a copy of Livecode, it will be very hard for them to find out what is stored in them. Hope that helps Pete lcSQL Software <http://www.lcsql.com> On Thu, Sep 13, 2012 at 11:57 AM, Dr. Hawkins <doch...@gmail.com> wrote: > After many recent posts, I'm starting to wonder: what does and > doesn't get complied in a standalone? > > Several messages have suggested, if I'm reading them write, that the > main stack is compiled, while the others, even if password protected, > are interpreted at runtime. Am I getting that right? > > And if so, what is the performance hit? > > So should all of the more intensive work be moved into routines in the > main stack? > > -- > The Hawkins Law Firm > Richard E. Hawkins, Esq. > (702) 508-8462 > hawkinslawf...@gmail.com > 3025 S. Maryland Parkway > Suite A > Las Vegas, NV 89109 > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode