Musings on Architect, MVC, Nested Behaviors

[J. Landman Gay]

Besides the impact of my current workload, I'm afraid this complexity is 
what prevented me from continuing to work on Swami's project. There are now 
so many disparate parts and pieces that unless you have a firm knowledge of 
every library and behavior script, there is no easy way to participate. In 
addition, remote debugging doesn't work with script only stacks so that's 
an additional obstruction to overcome.

I know there is enthusiasm for script only stacks and they are really 
helpful for those who use git. But when git isn't a target, the old 
fashioned way is really much easier to follow and debug.
--
Jacqueline Landman Gay | jacque at hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com>
>  Trevor DeVore via wrote:
>
>    One final thought I will add is this – whatever you do come up with,
>    consider if it will be understandable to you and other developers working
>    on the project later on. It is possible to get so wrapped up in separation
>    of code that it becomes very difficult to figure out how all of the code
>    works together when you revisit the project or try to add a developer.