Hot answers tagged presentation-model
MVP is somewhat open to interpretation. I've written a large scale Flex 3 app with MVP so I'll give my input based on experience. From the presenter's perspective it would be the view's responsibility to add subviews (because views are interfaced -- think console app replacement). Nothing view-specific should exist in the presenter (ie. you should be able ...
Perhaps a better solution is to use a factory class or method that knows how to build a presenter? The view would pass itself to the factory method and store the return value in it's presenter member. This decouples information about how a presenter is constructed (dependencies on services or whatever) from the view itself.
The basic reason for a controller is Separation of Concerns... What you describe is a combination of the MVC and the MVVM patterns, which indeed is my approach of choice. Basically you have your usual Model View Controller, but you add in the ViewModel. This helps you build more reusable code and have a true separation between you Data Layer, your Business ...
Only top voted, non community-wiki answers of a minimum length are eligible