Hello: I'm new to C::A and so I apologize in advance if my questions are obvious. I've read the docs and looked at some sample applications but I'd like some community feedback around how people structure their C::A applications.
Specifically, I want to understand how people factor their application into different classes/packages. I've seen many examples where people create an "application base class" that sets up session management and initializes config parameters and then perform the heavy lifting (setting up the dispatch table and associated target methods) in derived classes. What are some of the best practices around splitting up the derived classes? Do people create "sub-applications" for major pieces of functionality and then tie them together with multiple instance scripts from a "top level" page? I find that C::A applications end up being large single files. I understand that C::A takes a centralized approach versus an distributed embedded approach but this makes team development difficult. Does anybody have any best practices they'd like to share around this? --Brian
