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"<http://code.google.com/intl/de-DE/webtoolkit/articles/mvp-architecture.html>and
 had problems to get the view humble enough (gwt 
discussion<https://groups.google.com/d/topic/google-web-toolkit/3wqCUQpz2d4/discussion>).
 
But digging deeper led to 
MvpActivitiesAndPlaces<http://code.google.com/intl/de-DE/webtoolkit/doc/latest/DevGuideMvpActivitiesAndPlaces.html>(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 <http://code.google.com/p/gwt-platform/> and 
Errai<http://www.jboss.org/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<http://blog.hivedevelopment.co.uk/2009/08/google-web-toolkit-gwt-mvp-example.html>).
 
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"<http://code.google.com/intl/de-DE/webtoolkit/articles/mvp-architecture.html>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 [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Reply via email to