My team uses an MVP pattern for GWT in our large scale web applications. Its worked pretty well. We typically break the web application down into small modular widget objects using UIBinder and Composites, but within these widgets, we still organize classes into an MVP pattern. Separating out a model layer and a presenter allows you to do isolated unit tests against the presenter. So we try to put as much logic there as possible and never refer directly to GWT implementation classes. We also tend to keep the view objects as "dumb" as possible.
Fowler has a classic article where he describes the common ways of designing UI apps. Its a good intro: http://martinfowler.com/eaaDev/uiArchs.html. Our implementation resembles the "Humble View" pattern he describes. Thanks, Todd On Wednesday, April 17, 2013 1:42:40 AM UTC-4, kedar vyawahare wrote: > > > Hi all, > > We are Building a large scale application in GWT. We are a little bit > confused about the pattern we should use.Can anyone please suggest me > shall we go with GWT simple pattern or shall we use patterns like MVP? > > -Regards > > Kedar > > > > > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
