I agree with cri, probably the documentation should be reviewed and updated to GWT 2.3. Reading all the stuff I miss the big picture, should be useful some schemes that summarize things.
Anyway I wil try to implement a complete example on AppEngine using Activity, Places, MWP, RequestFactory, Editor and so on. I will need help of everyone and code review :) On Jul 1, 8:40 pm, Thomas Broyer <t.bro...@gmail.com> wrote: > Le vendredi 1 juillet 2011 18:12:45 UTC+2, cri a écrit : > > > > > First, someone definitely *thought initially* that Views/ClientFactory/ > > Activities/Places/PlaceHistoryMapper/ActivityMapper described on the > > GWT *MVP* documentation page constituted a framework that could be > > *used* at least for MVP. And, indeed, it can be. > > > Secondly, to me and some others I'd guess, it seems superior in terms > > of effort required than what is described in the "Part I and II" > > articles. We have a number of people here that have used both and > > there is agreement on this. However, I'm sure there are some relevant > > pros and cons. > > That's because all of them talk about history management, not only MVP. The > *MVP* part is only the View/Display interface and the handlers vs. the > Presenter/Delegate interface (people use different names for similar those > things); everything else is not part of the MVP *pattern*. -- 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.
