Google Web Toolkit 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.
No, Google Web Toolkit is completely free. In fact, all of GWT's source code is available under the Apache 2.0 open source license.
We just have a thing for web-based apps. We've gained quite a lot of experience developing AJAX applications with products like Google Maps and Google Calendar, and GWT is our way of helping developers leverage that expertise in their own AJAX apps.
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 hosted mode and erasing your compiler output (usually in the directory www/<package name>. Then, restart hosted 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 distributed binaries as per the Apache 2.0 terms. Please note that some libraries used in the Google Web Toolkit 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 Google Web Toolkit 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 Google Web Toolkit 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.
If you have an idea for an enhancement to GWT, please search through the Issue Tracker. If it isn't there, you might want to first suggest it to the Google Web Toolkit developer discussion group.
You can submit requests for enhancements at the Google Web Toolkit 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.
The GWT source code, licensed under Apache 2.0, is available here. If you are interested in contributing a patch, please visit the Making GWT Better guide.
As of mid 2008, GWT supports the following browsers:
Generally, no. GWT was designed in such a way to have all browser-specific code in user-level libraries. What's more, JavaScript itself has very consistent support across browsers, so when the GWT compiler performs its Java-to-JavaScript compilation, it doesn't need to worry about which browser the JavaScript is being generated for.
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.
With GWT development, your Java client code gets compiled into equivalent JavaScript that is loaded into your host pages. The generated product is totally independent from the server-side technology that you choose to use in your web application.
You can go ahead and use your favorite server-side templating tool and include your template directives into your host pages along with your GWT-generated JavaScript files. The server-side technology you're using to realize the templates is invisible to the browser and works just as it does without your GWT modules.
|
