> The distinguishing factor between M2 and MG for controller code is a name -- > controller (MG) or listener (M2). In essense, they act in the same way. > It's merely a semantic difference IMHO.
On that narrow point, yes. ;) MG has the (significant, in my view) advantage that control returns to the XML after every controller action. With M2, you can announce arbitrary events in your controllers, and your XML needn't care. MG forces you to clearly document the flow through the app with the XML. By keeping the controllers (the the UI flow) tightly bound to the XML, you can easily see what is the controller and what isn't. Now if we were all infallible programmers, this wouldn't be an issue. Controllers/Listeners are the UI controller and not the model, while the model is what the controller interfaces with. But I know I'm not infallible, so it's nice to have those 'guideposts' along the way. cheers, barneyb -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 100 invites. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:224734 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
