The upcoming set of posts are intended to discuss approaches for designing and developing interactive web pages using GWT (Google Web Toolkit). Most of this information is simply rehashed from various sources, but I’m rehashing again since 1) I didn’t see this all in one place and 2) the rehashing process gives me a better understanding of what is going on anyway.
The following are resources I used as I researched this:
http://robvanmaris.jteam.nl/2008/03/09/test-driven-development-for-gwt-ui-code
Test driven development for GWT UI code
http://code.google.com/events/io/2009/sessions/GoogleWebToolkitBestPractices.html
Google Web Toolkit Architecture: Best Practices For Architecting Your GWT App
http://easymock.org/Documentation.html
EasyMock Documentation
http://martinfowler.com/eaaDev/PassiveScreen.html
Passive View
http://vinaytechs.blogspot.com/2009/09/google-web-toolkit-hosted-vs-web-mode.html
Google Web Toolkit – Hosted vs. Web Mode
What a nice blog! :) I am myself trying to get my head around best GWT practices, and your texts are very helpful. But I am still struggling to see how more hierarchic GWT applications are best structured... and am also a bit confused about the different java libs out there like gwt-presenter, gwt-dispatc, gwt-mvp... do you by any chance have any plans on writing about those? :) Cheers, Stine
ReplyDeleteHi stinesplace,
ReplyDeleteGood question. I've been looking at the other libs and have been torn on how much or little I want to embrace them. I'm a little nervous about how much support they'll get for enhancements/bug-fixes so I'm leaning more toward trying to understand why they did what they did and using the pieces that are relevant to my project(s). As far as gwt-presenter and gwt-dispatch go, I did find this great blog... http://borglin.net/gwt-project/