Personally, I'm fairly new to GWT, and yes, the docs are pretty confusing, unhelpful, and inconsistent, and I'm not new to web frameworks. I wish I had taken down all the problems, contradictions, and lack of clarity that I noticed. Very strange for "Google".
Regarding MVP, I steer clear of Activities and Places because I think for more complicated UIs and nested views, etc., things become too messy and even impossible. They're too new and there isn't a single decent example that implements them. The updated Expenses sample app which uses Activities and Places -- and is shipped with GWT -- uses them but totally incorrectly in terms of MVP (tonnes of UI code in presenters, etc., if I recall). There's nothing wrong with do-it-your-own-way MVP as described in the two links at the top of: http://code.google.com/webtoolkit/doc/latest/DevGuideMvpActivitiesAndPlaces.html ... Trying to tie MVP with history and event management, etc, and everything else, is confusing for the beginner. The docs are not doing GWT any justice and if it hadn't got "Google" in the name I would have thought more than twice about adopting it. I'm not unhappy with my choice though, but I still feel the docs need a complete re-work. Slightly off topic, sorry. </rant> On Apr 7, 11:36 pm, Jens <[email protected]> wrote: > On Thursday, April 7, 2011 5:39:35 PM UTC+2, David Chandler (Google) wrote: > > Ray Ryan's famous I/O talk in 09 also mentioned place/history management and > > > the Command pattern, which are very useful ideas but not part of MVP proper. > > Various 3rd party MVP frameworks offered all these capabilities together as > > "MVP" and the GWT docs refer to Activities and Places as the MVP framework, > > but they're really not MVP proper, which has no doubt led to some > > confusion. > > Thats why I would change the GWT docs as soon as time allows. Someone new to > MVP and activity/places will definitely get the wrong idea of both and gets > confused. There are many topics/posts like this one in this group. > > @Alex: As David points out, the MVP pattern has nothing in common with GWT's > Place/History management framework (often referred to as GWT MVP). If you > use GWT places/activities your app will gain bookmarkable urls that > represent a place/application state and whenever such a url is visited a > corresponding activity will be started. This activity is then responsible > for attaching some UI/widgets to an area of your webpage. If this UI is > complex and has user interaction elements then you could implement this UI > with the MVP pattern to separate the UI from the logic that will be > performed when the user interacts with this UI. And once you decide to use > the MVP pattern then its in most cases easier to let the activity be the > presenter. But its also possible to implement a separate presenter and let > the activity hold a reference to it. > > J. -- 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.
