Calls to handlers/functions (usually) pass through what is called "the message path", going from object -> grouped objects -> card -> substack -> stack. This path is also enhanced by frontscripts and backscripts (code placed in the path either before the initial object or behind the stack).
So well-organized code does not have to be scattered among 100s of objects, but is instead centralized and placed in the most appropriate location.
In 2016 "script only stacks" were introduced. The normal stack is a binary file containing code and GUI elements. The script only stack is a text file, meaning it can be diffed and put under normal version control.
So well-organized code does not have to be scattered among 100s of objects, but is instead centralized and placed in the most appropriate location.
In 2016 "script only stacks" were introduced. The normal stack is a binary file containing code and GUI elements. The script only stack is a text file, meaning it can be diffed and put under normal version control.
https://livecode.com/script-only-stacks/