what kind of MVP to use, what is "current" best practice

first i thought it is hard to decide which front end/ widget framework to use (i decided to use pure gwt because of flexibility) but now after writing first small prototypes and reading about "best practices" and MVP, i came to conclusion that the much harder decision is how to implement MVP or how the backbone of my app would/should look like.
Currently i implemented my like this "Large scale application development and MVP" and had problems to get the view humble enough (gwt discussion). But digging deeper led to MvpActivitiesAndPlaces (at first sight this isn't "pure" MVP anymore?! it feels like a contradiction to MVP wit humble views?!) but i dug even deeper and found GWTP and Errai. I also found articles about dependency injection and Gin/Guice and that this should be a part of a "good" Gwt-App (google-web-toolkit-gwt-mvp-example). are frameworks that include dependeny injection preferable?
So how to construct the backbone of my app? how comparable (or probably "combineable") are this 3 "frameworks". Is "Large scale application development and MVP" out of date?


(the application i am about to construct is a large scale (at least the budget is large) -public - statistical data - presenting - web-application)

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