thx for explicitly pointing to "part2" - 'til now i didn't read it because i thought it is all about how to use uiBinder but now i found "...you quickly realize that something has to give. Either the presenter needs to know more about the view (making it hard to swap out views for other platforms), or the view needs to know more about the data model..." there. So the question most hurting me at the moment is answered :-). BUT: I am confused (like many others - a search for "MVP" in this group revealed) about statements like "Activities however are in no way related to MVP" and "This article looks at Activities and Places in GWT 2.1, which relate to the presenter and view aspects of MVP." (from (i know you know it and i guess you guessed i will mention it): DevGuideMvpActivitiesAndPlaces<http://code.google.com/intl/de-DE/webtoolkit/doc/latest/DevGuideMvpActivitiesAndPlaces.html> - on first sight the "view" there differs from "part1" and "part2"?) . So the Question is how both concepts relate or how they could be put into a relationship within an GWT-App? Or how a "best practice" would construct views, presenters, places, history, server communication? (a simple union of "part1"- "part2"- and "ActivitiesAndPlaces"- Article would have contradictions, wouldn't it?)
the third part of my question drifted in background somehow: is it a good idea to achieve MVP with some framework (gwtp, mvp4g...)? my first idea on this was to keep my app "framework free" as long as possible - (analog to my decision about widget frame works). But both p frameworks promise "more app" with less code ?! -- 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.
