I use MVP straight out of the Google videos and docs, and I love it. When I need to swap a view in or out, or change a url structure, or change a bit of communication with the server, I go strictly to the 1-2 files involved, make the changes I need, and never fear that some hidden bug will appear somewhere else. The Places/Activity framework works beautifully, and gives me the flexibility to navigate programmatically in response to events without having to put History-manipulating code anywhere but in my PlaceController. We've got 46,000 lines of GWT code running now, and it's easy to debug, easy to maintain, and is really delivering on the cross-browser compatibility promise.
What I love about GWT is how loosely coupled the different frameworks are. I started out with GWT-RPC, and then moved to RequestFactory. Then I wanted to switch to a plain JSON format so that the API could be usable to others w/o RF, and so I chucked most of RF... but I could still use parts of it like AutoBean to make parsing a snap! If I have to pay for this modularity with 3x the code size, I'll do it - I'm a one-man dev team and GWT helped me launch a complex data-processing app in a few months. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/3W0KCPXKhGwJ. 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.
