I've read two articles on MVP: "Twisting the Triad" by Bower and
McGlashan of Object Arts (cited by Dave Harris in an earlier post:
(
http://www.object-arts.com/Papers/TwistingTheTriad.PDF), and "MVP:
Model-View-Presenter: The Taligent Programming Model for C++ and Java"
by Mike Potel of Taligent(/IBM?)
(
http://www-106.ibm.com/developerworks/library/mvp.html).
The separations between Model and Presenter and between Model and View
are quite clear in my mind: the Model knows nothing about the
Presenter and the View; it only provides hooks for them via its API
and, in particular, its ability to register and notify
observers/listeners.
But, after reading the papers above, it is still not clear to me
exactly how the Presenter and the View are separated. There seems to
be a rather intimate interaction between the two in that each has to
know quite specific details about the other. I still can't see how
these two components are "separated" in any meaningful way.
I can think of two ways in which the Presenter and the View could be
separated. One is that either the Presenter observes the View (just
like the View observes the Model), or vice versa. The second way is
to define very small interfaces for either the Presenter or the View
or (preferably) both. This ensures a weak coupling between the actual
Presenter and the View classes. (I'm more familiar with the technique
of defining interfaces in Java than in Smalltalk, so this approach may
or may not be relevant in the context Smalltalk).
Does Dolphin MVP use either of these general approaches? If not, how
are the Presenter and the View separated in Dolphin's version of MVP?
Thanks!
bill
Locked
