Musings on Architect, MVC, Nested Behaviors

[Bob Sneidar]

What I did to make this easier is I created a Development menu in the stack menu that I remove in standalones. Openstack builds a submenu in the Development menu for all the behavior buttons (but they could be script only stacks) so that I can click Development/Scripts/<behavior script> to edit the script of any of my behaviors. Obviously this approach could be expanded to include <any> behaviors that the IDE is presently using. 

Bob S


> On Dec 26, 2018, at 21:31 , Trevor DeVore via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> See my comments above about organizing your files. If you have clearly
> organized your files and you explicitly set up nested behaviors in your
> code that initializes a stack when it opens, then it may be clear enough
> for a new developer. A new developer may be more likely to see the chained
> behavior if the behaviors are explicitly assigned in code vs having to use
> vs going to the IDE to look up what the behavior chain is.