GWT is designed to run on systems that meet the following requirements:
If you have trouble running GWT, and your system meets the requirements above, let us know on the GWT developer discussion group.
For step-by-step instructions, see Getting Started: Quick Start Installing Google Web Toolkit.
GWT is available in all countries and should work for most languages, though documentation is currently only available in U.S. English.
When you use GWT‘s development mode server or compiler, the application periodically sends a unique timestamp ID and version number of your product back to Google’s servers so that the application can notify you of new versions. The timestamp ID is generated the first time you use the complier or development mode server. As a part of this request, Google will log the timestamp ID and the version number.
The GWT developer plugin checks for updates once a day or as configured on the respective browser, sending the current plugin version number. As a part of this request, Google will log the plugin version number.
We won't log cookies or personal information about you, and we will only use any data we log in the aggregate to operate and improve GWT. We use this information internally to determine usage volume of the development mode server and compiler in the aggregate.
We‘ll release new versions of GWT on the GWT web site. Barring any unforeseen circumstances, we expect to keep all previous versions of GWT available on the web site as well. As releases become outdated, we’ll no longer actively support them on the GWT discussion group, but we'll do our best to keep old releases and documentation around as long as possible.
If you are working on a project, you may notice problems compiling and running your project if you upgrade the GWT library from one version to another. Sometimes you may see GWT compiler internal errors, or you may see odd runtime errors you've never seen before.
Before you file a bug, try stopping development mode and erasing your compiler output (usually in the directory
www/_<package>_. Then, restart development mode. If you're still having problems, though, we definitely want to hear about it!
Yes and yes! GWT is available for non-commercial, commercial, and enterprise applications. All of GWT's code is available under the Apache 2.0 open source license.
GWT has been released under the Apache 2.0 license, so you're allowed to distribute binaries as per the Apache 2.0 terms. Please note that some libraries used in the GWT are under other licenses as referenced here, so you must comply with their terms as well.
Glad you asked! Our blog is http://googlewebtoolkit.blogspot.com/
You can post your questions to the GWT developer discussion group on Google Groups. The GWT engineering and operations team will participate in the group and try to answer questions as they come up.
You can file a bug in the GWT Issue Tracker. Please be sure to search for your problem before reporting a new issue, since someone else might have already reported it. If you would like to be notified about activities on your issue, star the report and you will receive emails at your account's email address.
You can submit requests for enhancements at the GWT Issue Tracker. When you save your report, it will be labeled as a “Defect” even though you want to submit an RFE (Request for Enhancement). Don't worry! We review each item submitted to our Issue Tracker, and will mark enhancement requests appropriately when we receive them.
GWT supports the following browsers:
That said, what makes compliance to newer browsers tricky is the DOM API. For backwards-compatible browsers, it just works. For other cases, it‘s straightforward to change the user-level libraries. All that’s required is to implement a version of DOMImpl for the desired browser. In some cases an entirely new browser may require a bit more work to be supported by GWT, but this would be the exception rather than the rule.
Yes, you are free to use GWT with any server-side templating tool such as XSLT, Frontpage, Dreamweaver, WebObjects, PHP, Active Server Pages, or JavaServer Pages to name a few.