What is Model View Presenter. (Was: Hairy generics question)

[Daniel Pitts]

On 2/26/12 9:13 AM, Arved Sandstrom wrote:
> I'm laying this stuff out there simply to indicate that despite all the
> terminology, much of it redundant and confusing and artificial, that MVC
> and MVP are usefully different and real architectures, and that
> Presenter is definitely not Controller.

I guess I had never heard of MVP, and just assumed the OP was recreating
MVC without clearly understanding the concept. This apparently was
hubris on my part, and I humbly apologize for that.

I'm going to do a web search to learn more about MVP architecture later
today, but I want to know what it means to people in this group as well,
X-Posting to clj.gui, since it seems relevant.

So, fellow Java engineers and Pragmatic Programmers, how would you
compare and contrast MVC vs MVP? Are there design/clarity benefits to
one over the other? That does "Presenter" mean to you?

Thanks,
Daniel.

[Lew]

Only what I find on the Web:
<http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93presenter>

According to the fully authoritative and always-correct Wikipedia, it's a
particular variant of MVC, much as the front-controller pattern is a
particular variant of MVC.

Apropos of which, someone somewhere around these newsgroups complained that
MVC was bad for them because it centralized the controller. That's only the
one flavor of MVC that does that - it's not an essential feature of MVC that
there be only one controller.

--
Lew
Honi soit qui mal y pense.
http://upload.wikimedia.org/wikipedia/commons/c/cf/Friz.jpg

[Arne Vajhøj]

It do say:
Model–view–presenter (MVP) is a derivative of the
model–view–controller (MVC) software pattern

But I would more call it a brother or cousin than a son.

> much as the front-controller pattern is a
> particular variant of MVC.
>
> Apropos of which, someone somewhere around these newsgroups complained
> that MVC was bad for them because it centralized the controller. That's
> only the one flavor of MVC that does that - it's not an essential
> feature of MVC that there be only one controller.

I don't even think it is that common. Struts 1 is probably the most
widely used true MVC framework out there and it has multiple actions
(and actions are controller not model!).

Arne