In this episode we discuss the following:

On the Automation simplified blog they have post an article suggesting ways  to test GWT suggestion boxes with Selinium.
The author identifies a problem where he has a textbox with suggestions then needs to select a find button.
With the suggestion box open Selenium can’t find the button.
He outlines the fix and was able to create the test.

Tutorialspoint has been adding content to their GWT section. The site has a lot of useful GWT information consolidated into one section. Kind of like what W3Schools does for Html, Javascript and CSS.
It’s like cliff notes for GWit developers.

Kenneth Gulbrandsøy released an early version of gwt-leaflet a lightweight mapping alternative to popular mapping APIs like Google Maps and OpenLayers.
The library uses Leaflet, an open-source javascript library for mobile-friendly interactive maps by CloudMade, to implement a collection of mapping Widgets which GWT projects can use to implement mapping capabilites on the client-side of a GWT application. The Leaflet API is a third-party javascript and is integrated with GWT as Java classes using JSNI and Type Overlays.

Uma on the It’s Amazing (or is it Hello It’s Crazy blog) posted a tutorial on how to utilize all of these technologies in a sample app.
The tutorial is a step by step guide on how to set the project up and getting running.

The folks at Traction Software has added some new Date/Time Pickers to their open source gwt-traction library, that work in any timezone. They have a UTCDateBox and a UTCTimeBox that return a UTC date or time but allows the display and edit to be in the user’s local timezone.
That can be a problem when you deal with users across timezones especially since Java defaults to the locale of the server.
They also have a date time range control and HTML5 date/time inputs for iOS


Google released J2ObjC  a tool aimed at making it easier to port software between the two major smartphone platforms, by converting Java code for Android into Objective-C code that can be compiled to run on Apple iOS devices.
The same Java code could be shared with GWT applications allowing developers to leverage the same core code across the 3 platforms.
The UI would still need to be developed in Objective-C but non UI code can be translated.

The Register Article
eWeek Article

The Vaadin project along with the other steering committee members has put together a survey to get developers opinions to help steer future development of GWT.
They want to know

• How should GWT develop?

• What technologies should it better support?

• What are best practices within the community?

• What is your opinion on the future of GWT?

Get your voice heard take the survey.

Vaadin is having a JavaOne meetup in San Francisco on October 2 at Hotel Serrano starting at 5pm.
Don’t worry they’ll bring the beer.