use-livecode Digest, Vol 87, Issue 3
rjb at robelko.com
Fri Dec 3 10:30:50 EST 2010
On 02.12.10 at 20:40 -0800 John Burtt apparently wrote:
>Wouldn't more terms just add to the confusion.
>Separate stacks are called "main" stacks.
>The stacks that are part of (within) a main stack are called "sub" stacks.
>Sub stacks that are separated from their main stack, become main stacks.
>A main stack that has been turned into an application is an "executable".
>Main stacks are savable.
>Sub stacks are saved when their main stack is saved.
>Executables are not savable.
>And, sub stacks of the executable are not savable.
Stacks are really windows with objects and scripts.
Stacks are saved in stackfiles.
The mains (startup) stack in each stackfile is its mainstack.
Other stacks in that stackfile are its substacks.
When executable is produced, the runtime engine is merged with the
stacks. However, depending on the settings, the mainstack and
substacks are either kept together as in stackfile (neither can be
modified at runtime) or substacks are split to become technically own
mainstacks in own stackfiles (thus can be modified at runtime),
although logically they remain part of the package.
More information about the Use-livecode