Shared publicly  - 
 
What's new in GWT 2.5
I've got the chance to attend the +Ray Cromwell  talk about the history and the future of GWT.

Lets me summarize quickly the presentation:

The first part of the presentation was dedicated to the history of GWT. Its evolution from 2006 until now -> GWT is mature, well tested and is widely used inside and outside Google.

Then, Ray presented the new features of GWT:
- Compiler optimizations that can reduce significately the size of generated code. You have also the possibility to use the Closure compiler

- The super dev mode : recompile quickly your GWT applications just by clicking on the "Dev Mode On" bookmarklet and see the result in the browser. Unfortunately, due to the poor quality of the wifi, the demo didn't reflect the power of this feature. (It's not the only one demo that "failed" during the conference because of the bad quality of the wifi...)

- Source Maps : possibility to debug the java code directly in the browser by mapping the lines of obfuscated javascript to the corresponding line of Java

- Elemental, a new experimental library giving you access to all of the features/API provided by the browser.  For instance, you can display the flow of the camera inside your GWT application if the browser allows it.

- Full coverage of ARIA, UiBinder and CellWidget improvements

- Goodbye SVN, hello git !!

- Announcement : creation of the GWT steering committee that will drive the next GWT releases.

The most cool feature that was showed by Ray was the possibility to write Java code directly in your html page :)

<script type="text/java">
   String helloWorld = "Hello world";
   Window.alert(helloWorld);
</script>

The trick is to use a ServletFilter in the server side. This servlet filter use the gwt compiler to compile this java code in javascript and inject it in the html returned to the client.

The session ends with the presentation of  GXT 3 done by the CEO of Sencha and the presentation of Vaadin done by the CEO of Vaadin.

GWT is not ready to die !!!!

Edit : link to the session slides : https://docs.google.com/presentation/d/1pC9WK80-fzIs2iMQOO3Jsvfmqv2erI9xucuF3lHOE7Q/edit#slide=id.p18 #gwt #io12
36
30
Josh Ryan's profile photoVivek Thakyal's profile photoEmanuele Ziglioli's profile photoPrayag Upd's profile photo
7 comments
 
All that in 1 hour ?  ;-)
Thanks for your report from the field, waiting for the video to be made available !
 
Thanks for share!!!!!
I join: "GWT is not ready to die !!!!"
 
Nice writeup.

"The trick is to use a ServletFilter in the server side." It's funny that in the very, very, very first version of GWT, this is how it worked -- it strictly required a servlet filter, actually -- but we later convinced ourselves that people might find it weird or onerous, so we changed things around so that GWT would compile everything to standalone JS that didn't require server support. At that time, deferred binding happened completely on the server, too, so you ever only compiled the permutations that the user actually requested.
 
Funny to think that we were in the same room and didn't even met while we're working together now :D
Add a comment...