Adding GWT to an existing web project
Code completion in GWT module files
Code completion in .ui.xml files
Project/Debug: does *not* compile .java to .js, starts Tomcat in debug mode and GWT Shell (aka "Hosted Mode") in debug mode and shows the welcome page there. Please note that 2 debug sessions are started simultaneously: for the server-side code and for the client-side.
Debug/GWT Hosted Mode (w/o a J2EE server): does *not* compile .java to .js and does *not* start Tomcat, but starts GWT Shell (aka "Hosted Mode") and shows the welcome page there.
Project/Run: Calls GWT compiler to convert Java to JavaScript and runs the application using the associated web server. This action also opens a new browser window.
Synchronize methods in the asynchronous and synchronous GWT RPC interfaces:
edit GWT module files visually
Hints for classes unsupported by GWT
Support for multiple modules in a project
Hints for keys missing in the .properties file for GWT constants interfaces
Running a test case (e.g. a GWTTestCase based)
GWT Templates/Wizards for easy file creation
add a reference to an existing GWT module
upgrade to a newer GWT version
Run GWT DevMode on AppEngine - this option is only available if your GWT project runs on the Google App Engine SDK (you can download the NetBeans plugin from http://kenai.com/projects/nbappengine/pages/Home). The action starts GWT dev (aka hosted) mode and App Engine SDK in the same JVM.
GWT project settings
Insert GWT History Frame: inserts a definition of an invisible iframe into a html page for storing navigation history data by GWT
Wizard for creating a new Maven-based GWT project running on Google App Engine and using JDO for persistence
