Hi James, Thanks much for the reply!
On Mon, 2009-03-30 at 03:59 +0200, James Byrne wrote: > bill walton wrote: > > > > > Any thoughts / discussion is much appreciated. > > The original concept of controllers in MVC was that they handled > terminal events like mouse and keystrokes. The elaboration of MVC into > MVP moved that responsibility into another layer between views and > controllers called a presenter. Interesting. My understanding / impression is that the presenter sits between a controller and a set of models. > One could argue that what one really > has with Rails 2.x is MVP, with the browser acting as the presenter, > rather than MVC. Don't think I understand this perspective. Say more, plz. My understanding is that one 'purpose' of the Presenter pattern is to restore the 'silo-like' source code organization that MVC brings to the table. With MVC, if I need to modify the customer info section of an app, I know I'll be looking at customers_controller.rb, .rhtml files in the views/customers folder, and the customer.rb file in the models folder. Best regards, Bill --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
