Reference Material Discussion Application Architecture Strategies

[prothero at earthednet.org]

Michael:
I was wrong. All I have to do to activate a substack is just
         start using stack theLibStackName
Bill

prothero at earthednet.org
http://es.earthednet.org

On Apr 20, 2014, at 9:35 AM, Michael Doub <mikedoub at gmail.com> wrote:

> My coding style has evolved to trying to put code in Libraries, Stack and Cards.  I only put stubs that call other handlers in the objects themselves.  This is the code organization part.   
> 
> I was putting my library stacks in as substacks and when I started seeing the naming conflict messages I started looking into where these should go.   I always seemed to have problems with “start using” unless the stack was already in memory, so I still feel that I am missing something relating to the basics loading stacks. 
> 
> Bill, are you building your stand alone yet?  This is where I really started to ask questions.  Why is there an option to move substacks into individual stacks?  When I made everything substacks I really didn’t think too much about the standalone builder.  Now that I have both I feel I need to understand what is going on and why.
> 
> -= Mike
> 
> 
> On Apr 19, 2014, at 6:01 PM, Earthednet-wp <prothero at earthednet.org> wrote:
> 
>> Michael,
>> Thank you for asking this question. There is certainly a need for this in the community. I am also new to livecode and am converting a rather large app from Director. I am building a cross platform app, and perhaps a mobile version later. Currently I am putting most of my code in the stack scripts of substacks, organized roughly by broad functionality. I started with external stacks that I loaded at runtime, but found it much easier to do script searches if they were substacks. All code is in stack scripts. If I need these pieces for other projects, I can always separate them. That's as far as I've gotten so far. I can imagine getting a large collection of substacks by the time the project is completed. So far all of my substack handlers are able to seamlessly call stack handlers in other substacks, which is nice. I wonder if there are consequences to this approach.
>> 
>> One of the big challenges is keeping track of all of the handlers and whether their location in the hierarchy requires special treatment (like a dispatch command). With all of my handlers in stack scripts, I don't have to do this.
>> 
>> I'd be very interested in hearing how others organize their projects.
>> Bill
>> 
>> William Prothero
>> http://es.earthednet.org
>> 
>>> On Apr 19, 2014, at 2:04 PM, Michael Doub <mikedoub at gmail.com> wrote:
>>> 
>>> Is anyone aware of any reference material that discusses strategies for architecting your application with the livecode components and their implications with the 
>> 
>> _______________________________________________
>> 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
> 
> 
> _______________________________________________
> 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