Wednesday, February 17, 2010

Who's @ Google I/O: all things Google Web Toolkit

The Google Web Toolkit (GWT) team had an exciting 2009 -- ending the year with a Campfire One where the team announced the release of GWT 2.0 with Speed Tracer. Developers are quickly adopting GWT to build compelling apps in the browser, and we're excited that we'll have the following companies demoing their applications and talking about how they leveraged GWT (and other Google technologies) in the Developer Sandbox at I/O:
Clarity Accounting, Dimdim, DotSpots, Entrinsik, Hydro4GE Inc., JetBrains, Lombardi, Media Beacon, RedHat, Rosetta, SAS, and StudyBlue.
In addition to developers from these companies, we'll also have Google engineers in the Sandbox, talking about how our internal teams have used GWT to build products like Google Wave.

And members of the GWT team will be hosting a number of advanced sessions at Google I/O. Here's a quick preview of some of the sessions (there are 4 more on the I/O website):

How can you take advantage of new HTML5 features in your GWT applications? In this session, we answer that question in the form of demos -- lots and lots of demos. We'll cover examples of how to use Canvas for advanced graphics, CSS3 features, Web Workers, and more within your GWT applications.

Architecting for performance with Google Web Toolkit
Modern web applications are quickly evolving to an architecture that has to account for the performance characteristics of the client, the server, and the global network connecting them. Should you render HTML on the server or build DOM structures with JS in the browser, or both? Bruce Johnson -- one of the founders of Google Web Toolkit -- will discuss this, as well as several other key architectural considerations to keep in mind when building your Next Big Thing.

At its core GWT has a well-defined and customizable mechanism -- called Linkers -- that controls exactly how GWT's compiled JavaScript should be packaged, served, and run. Matt Mastracci of DotSpots will discuss how to create linkers and explains some of the linkers we've created, including a linker that turns a GWT module into an HTML5 Web Worker and one that generates an HTML App Cache manifest automatically.

Architecting GWT applications for production at Google
For large GWT applications, there's a lot you should think about early in the design of your project. GWT has a variety of technologies to help you, but putting it all together can be daunting. This session walks you through how teams at Google architect production-grade apps, from design to deployment, using GWT.

If you're a GWT developer or considering using GWT for your next project, we hope to see you at Google I/O! It'll be a great place to meet and chat with other engineers, including the team behind Google Web Toolkit.

To learn more and to sign up for Google I/O, visit code.google.com/io.

2 comments:

  1. What about the session on continuous integration testing by Ray Ryan that was announced earlier?

    ReplyDelete
  2. That session is still planned for:

    http://code.google.com/events/io/2010/sessions/gwt-continuous-build-testing.html

    We just included 4 of the 8 sessions in the blog post with a link to all the GWT sessions that'll take place at I/O.

    ReplyDelete