I'm trying to wrap my head around the new MVC functionality of Sencha Touch these days.
I'm comparing it a bit with server-side MVCing. So far my oberservation is that it doesn't seem as easy and clear as on the server-side, where basically one controller action responds to on client/user request.
When looking at the Twitter example, I see "actions" in the controller as well as in the views, which confuses me.
For example the following methods:
All those methods have quite some lines of logic and respond to user actions.
twitter.views.Searches: onItemTap(), onItemSwipe()
Shouldn't that stuff go into controllers? If yes, how? If no, why? How do you difference those actions with the actions managed by the controllers?
Thanks for any help for finding me the missing piece.
P.S. @Sencha, with ST 1.0 out the door, any info on when we can expect more info/documentation on the MVC stuff?