I've been doing some reading and some quick mock ups to see if I can grasp the idea behind the Model-View-Presenter design pattern. After a few hours looking today, I'll be honest, I don't get it. Maybe it's just because I can't see how it applies to my specific need. The plusses I do see is that you can more easily test presentational logic through NUnit since that logic has been moved from the codebehind to a testable "object".
Is that it?
I think in most cases the view and presenter need to be extremely coupled. The presenter needs to know exactly what UI elements are on the the page so that it can populate and retrieve user data from those UI elements. If that's the case isn't a codebehind the perfect item to act as the "presenter"? I must be missing something because I know the answer is a resounding NO. But the way I understand things now you can't switch Views out with any presenter becuase the presenter needs to know a lot about the view in order to get things to work properly. What am I missing? Everything I read is really trivial talking about the benefits of TDD with MVP but that's it.