Timeline for Model-View-Presenter implementation thoughts
Current License: CC BY-SA 2.5
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 27, 2012 at 16:03 | comment | added | Marcel Toth | The important point for decoupling is that presenter ONLY accesses view through well defined interfaces (UI library independent), so that is how UI library can be replaced for another one (another one that will implement the same interface for form/window/dialog/page/control/whatever) | |
| Mar 22, 2011 at 18:14 | comment | added | Philip Regan | I think the real power comes from two directions: The first being that the View and the Model don't have anything to do with other, and the second that the majority of development work, the app's engine, is done in a neatly-contained unit, the Controller. But some bleeding of responsibility is bound to happen. At least the majority of swapping of interfaces will be done in the Controller and any linking from the View would be minimum. As others have said, some bleeding of logic is expected and allowed. MVC isn't a magic bullet. | |
| Mar 22, 2011 at 16:22 | comment | added | trycatch | I certainly agree the P/C should be responsible for the View, but I thought part what was supposed to make MVP powerful was the ability to pull the entire UI library out and plug a new one in and with some massaging (dllimporting and whatnot) be able to run another one in it's place. Wouldn't this be more difficult with the Controller/Presenter accessing the dialogs directly? I'm certainly not trying to argue, just further understand :) | |
| Mar 22, 2011 at 16:13 | comment | added | Philip Regan | I think the Presenter/Controller should be fully responsible for the Views, so the latter. Again, some coupling is bound to happen, but at least if the direction of responsibility is clear, then maintenance should be easier in the long run. | |
| Mar 22, 2011 at 16:10 | comment | added | trycatch | This is definitely my goal. My main problem is how to set up the View - whether it should be a class with an instance of each dialog, and then use View.Getters which call Dialog.Getters, or if the Presenter should be able to call Dialog.Getters directly (this seems too tightly coupled, so probably not?) | |
| Mar 22, 2011 at 16:09 | history | edited | Philip Regan | CC BY-SA 2.5 | added 428 characters in body |
| Mar 22, 2011 at 16:02 | history | answered | Philip Regan | CC BY-SA 2.5 |