First off, Senchacon 2011 was great. So much info and very promising roadmap. The performance enhancements are enough to make me seriously consider moving my native applications to senchatouch 2.x. Thank you all very much for all the hard work. My question is probably directed more to Ed Spencer.
Ed, Could you please update the senchacondemo you have on github to have controllers for each tab, while still having the main controller handling things for the main viewport and tabpanel? I have the scenario (and I'm sure others do as well) where I want the main controller to handle some things things, but I want delegation to other controllers to handle those specific concerns. This is a standard pattern I've followed in native apps (I'm sure others have as well). I believe this would be a very valuable tutorial / contribution that would help steer all of us in the right direction. Don't need a write up, just another branch on that codebase.
I'm beginner and when you search something related to MVC, we are redirected to the twitter example, it's so hard to make a Hello Word demo with MVC approach. From this examples I can't figure out how the connection is made between layers, and if I try to modify something the hole app crash. Maybe I'm the stupid but it's so hard to make a diagram or something where we can see (you can explain) the connections, the possible solutions we can use, with pros & cons, why, when & how we use this or other solution. Not a full implemented application and we need to guess why was made this way.