Group items tagged

There is an outdated archetype which creates a very simple Gwt project without tests nor RPCs. Unfortunately the generated pom.xml is for old gwt versions and needs that you do a bunch of changes by hand.   mvn archetype:generate  -DarchetypeGroupId=org.codehaus.mojo \    -DarchetypeArtifactId=gwt-maven-plugin  -DarchetypeVersion=1.1 \    -DgroupId=com.foo  -DartifactId=myApplication - Lately I have sent a patch to gwt which adds the ability to generate pom.xm to webAppCreator. But the patch is under review and it wont be available until a new gwt version (in the case it is included). http://gwt-code-reviews.appspot.com/397801/show - So, I recommend you to get the pom.xml from a working application and use it as a template for your project. Some days ago, I  ported the google contacts example application in order to use available libraries for MVP and add tests for all the code. I think It should be a good point for starting your project: http://gwt-workshop.googlecode.com/files/GwtWsMvpContacts.zip

Summary:  Google Web Toolkit (GWT) lets you use the Java™ language to implement rich client user interfaces that run in a browser. In this two-part article, David Geary brings you up to speed on the latest version of GWT and shows you how to implement a desktop-like Web application.

Mixing HTML and Widgets So how can we mix widgets and html properly? Before GWT version 2.0, the most common way was to use “RootPanel.get(’someId’)” to access an HTML element in the application host page, and then create an object there to attach the widgets to (ie. a “RootPanel”). If we need to embed only a few widgets in the host page, this technique suffices. But doing this in a real application with a large number of widgets becomes complex and slow. UiBinder scales better because it does not inject widgets into the HTML of the host page. Instead, you declare your layout in a stand-alone HTML file that can be composed with other components as many times as necessary to build more complex interfaces. Composition entails componentization, allowing the developer to create subparts of the user interface (UI components) that can be packaged, re-used and tested in isolation.

I figure it is going to take me at least four iterations to get this right. The first one will be building a GWT application with a simple UI that has no server logic behind it (just to learn how layout in GWT works). Step two will be adding a fake servlet backend (not app engine, just in memory). While not exactly App Engine yet, I should have a completely specified client-server API by the end of this process that I can subsequently implement on App Engine (iteration 3). Iteration four will handle deployment, CSS and whatever I may screw up in iterations one and two. I will log my notes of things I run into while I code.