This video provides excellent information on developing a high performance web application using the Google Web Toolkit. The video presents the best practices by showing how real web applications achieve high performance event handling, UI creation, and more. Read more
Developers often asked what’s the best way to go about building custom widgets. There are of course a number of best practices to consider when answering this question. In this post I’ll highlight a few I like to start off with.
Google Web Toolkit Blog: Widget Best Practices / Widget Building.
In this tutorial we are going to work on creating a form in GWT, and then we are going to work through processing the form from a Java servlet. File uploads with AJAX is certainly one of the more difficult aspects of programming on the client side, but with GWT you can easily implement an AJAX file upload. On the server side we are going to work with Apache Commons to process the content of the GWT form. Read more
GWT 2.0 is scheduled to be release later this year, and I wanted to keep you informed on an interesting new feature coming in the next milestone build. The UIBinder will allow you to develop GWT widgets using XML files, and I think the entire GWT community should be excited by this new feature. The UIBinder will certainly bring new web developers into the GWT community, since the layout of an entire GWT web site can be done using XML files, and then all events are captured using Java. The UIBinder will use annotations for communications back and forth between the XML files and your Java code.
For a first look at GWT UIBinder you can click here
I will keep you informed once more information on GWT 2.0 and the UIBinder comes available.
In this tutorial we are going to work through creating multiple modules for a GWT web application. Multiple modules are a great way to organize and reuse your GWT code, and it is a good way to develop multiple GWT pages with only one entry point. If you are not familiar with the structure of a GWT application then you should probably read this tutorial first. Read more
JSNI stands for JavaScript Native Interface, and it allows for you to quickly use native JavaScript right in your Java code. With the use of JSNI, you are also able to pass parameters back and forth between JavaScript code and Java code, which increases your capabilities for writing client side applications. So why should you use JSNI? Well if you can implement a piece of code that is better suited to be written in JavaScript then you should probably implement it with JSNI. Also JSNI gives you the freedom to pick and choose which GWT capabilities you want to use. Read more
The browser history has always been finicky at best when working with AJAX, but I believe GWT has one of the best frameworks for handling browser history. For this tutorial, you should have a good idea on how to use GWT’s Anchor widget, and also you should know what a hash is, but if not you can click here for the tutorial on Anchors. One more thing you need to remember, I am using GWT version 1.7, so if you are using an earlier version you might want to consider upgrading. Read more
This tutorial is going to cover the use of the Anchor widget in GWT. The Anchor widget is important because it is going to allow you to link to other pages as well as to pages within your own project. The primary reason why I am writing a specific tutorial on the Anchor widget is because without it you will not be able to easily use GWT’s history framework. So let’s begin by writing some code. Read more
This tutorial is meant to be a quick introduction to using events in GWT. For the most part if you want your web application to do anything, you need to know what events are and how to use them. With that said, we can begin by creating a new GWT project, and primarily this tutorial is going to work within the MainEntryPoint.java file. Read more
This post is going to walk you through setting up and using Google Maps with GWT. The concept of using the Google Maps API is the same for the AJAX version of the API, and many of the same functions are included. The only exception to this is the naming of the functions. In the AJAX version of the API many of the functions begin with a “G”, while the GWT version of the API has omitted the “G”. So for information on the concepts of the Google Maps API, you should take a look at the AJAX version of the API. Read more
Google Web Toolkit Blog