Check out pages 7 and 8 from the slide deck PDF linked to from that
page.
For your convenience, here is the net of it. With MVC, the model is
thick with business rules and glue code to a data access layer. The
view has lots of dependencies on the model. The controller is usually
a framework component driven by some kind of configuration, usually
XML based. With MVP, the model is lightweight POJOs. The view is
mockable. It is the presenter that is heavy with glue code and
business rules. The thinking here is that MVP is more suited for TDD
than MVC.
Another notable feature of MVP in GWT apps is the use of an event bus
instead of hard coded event handler dependencies. Typically, that
event bus is implemented as either the HandlerManager from GWT itself
or the PropertyChangeSupport class from the GWTx library.
On Apr 16, 5:57 pm, nino ekambi <
jazzmatad...@googlemail.com> wrote:
> Hi,
>
> I cant find the informations.
> Can you please tell me where to look on the page ?
>
> thx and greets
>
> Al
>
> 2010/4/16 gengstrand <
gengstr...@gmail.com>
>
>
>
> > I covered the differences between MVP and MVC in this presentation.
>
> >
http://www.dynamicalsoftware.com/gwt
>
> > I hope that helps.
>
> > On Apr 15, 5:23 am, Sabbir <
leo.sh...@gmail.com> wrote:
> > > i am having quite a difficulty in understanding MVP in gwt. Can
> > > anybody suggest a good example easy one
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google Web Toolkit" group.
> > To post to this group, send email to
google-we...@googlegroups.com.
> > To unsubscribe from this group, send email to
> >
google-web-tool...@googlegroups.com<
google-web-toolkit%2Bunsu...@googlegroups.com>
> > .
> For more options, visit this group athttp://
groups.google.com/group/google-web-toolkit?hl=en.