No offense to the other posters, but I wouldn't go anywhere near "platform"
or "mvp4g" right off.  Just confuses the issue.  Having recently been where
you're at, I'd go here first: http://martinfowler.com/eaaDev/uiArchs.html.
 That should shed more light on why MVP is of interest period.  "Humble
View" is definitely an item to read.  I had to implement "The Humble Dialog
Box" with gwt-presenter and all unit/integration tests before I groked just
the _why_ of why I'd want to pursue MVP.  As of this post, I have checked
out gwt-platform, mvp4g, Guice 2.0 and Guice 3.0 MVP -- still haven't
decided the direction I'm headed.

IMHO, Schilly was right in that the code muddles the theoretical discussions
or visa-versa.  MVP is a concept.  The frameworks are based upon that, but
they possess different implementations based upon the concept.

Good luck!

On Tue, Apr 5, 2011 at 3:04 PM, Alex <alex...@gmail.com> wrote:

> I've been looking into GWT and MVP recently and to be honest I'm very
> confused. My project involves around 40 different pages / individual
> views, or whatever the correct terminology is. I've been reading
> tutorials that follow Model-View-Presenter and others that use
> Activities and Places.
>
> Which one should I be using?
>
> Many thanks,
> Alex
>
> --
> 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-web-toolkit@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>

-- 
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-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Reply via email to