Substack vs. Library Stack

[Scott Rossi]

I imagine you'll get a lot of responses to this, but one reason to use a
library is its code is available to all open stacks in LC: functions,
commands, etc.  Sort of like having a backscript for all open stacks,
instead of just one.  A substack doesn't do this.

Another frame of reference that might help is the difference between
behaviors and libraries: code in behaviors is object-specific, available
only to those objects that have the behavior assigned to them, while code
in libraries is universal, available to all objects anywhere, and doesn't
require any assignment.

Other people will probably chime in with additional insights.

Regards,

Scott Rossi
Creative Director
Tactile Media, UX/UI Design




On 4/29/15, 9:56 AM, "Mike Kerner" <MikeKerner at roadrunner.com> wrote:

>I have not read a straight answer on this, yet.
>
>Library stacks vs. substacks why use one vs. the other?  I don't see any
>clear advantage to Libraries, per se, even for...libraries.
>
>-- 
>On the first day, God created the heavens and the Earth
>On the second day, God created the oceans.
>On the third day, God put the animals on hold for a few hours,
>   and did a little diving.
>And God said, "This is good."
>_______________________________________________
>use-livecode mailing list
>use-livecode at lists.runrev.com
>Please visit this url to subscribe, unsubscribe and manage your
>subscription preferences:
>http://lists.runrev.com/mailman/listinfo/use-livecode