Works under test sources roots. Creates new class derived from GWTTestCase.
UiBinder class and ui.xml file
Creates new *.ui.xml file with the corresponding Java class
"Go to declaration", "Find Usages", "Rename" actions, completion and highlighting works for GWT specific references in the following places:
- parameters of methods UIObject.setStyleName, addStyleName, removeStyleName
- parameter of RootPanel#get method
- @Key annotation
- <inherits> tag in .gwt.xml file
- the return statement in "getModuleName" method in classes derived from GWTTestCase
- parameter of ServiceDefTarget#setServiceEntryPoint method
- @RemoteServiceRelativePath annotation
- <meta> and <script> tags in GWT html file
- tags and attributes in ui.xml files
- @UiHandler annotation
GWT Studio have inspections to report the following problems:
- RemoteService-derived interface is not synchronized with its asyncronous version
- Asynchronous version of RemoteService-derived interface is not synchronized with the original interface
- Type of parameter or return type of method in RemoteService-derived interface is not serializable
- GWT Remote service is not registered as a servlet in web.xml
- Classes not from JRE emulation library (and not from client code of inherited modules) are used in client code
- Class marked as serializable contains non-serializable fields
- Style name used as parameter of "addStyleName" or "setStyleName" is not presented in CSS file
- Localizable interface is not synchronized with the corresponding .properties file
- Interfaces derived from Constants contains methods with parameters
- Deprecated @gwt.key JavaDoc tag usages
- Deprecated @gwt.typeArgs JavaDoc tag usages
- AsyncCallback class is used without type parameters
- ServiceDefTarget.setServiceEntryPoint is used instead of @RemoteServiceRelativePath annotation
- Usages of event listeners classes deprecated in GWT 1.6
- Inconsistencies between fields with @UiField annotation and 'ui:field' attributes in ui.xml files
- Wrong signatures of @UiHandler methods
Each inspection suggest a quick-fix to resolve the corresponding problem.
An output of GWT compiler can be automatically copied to an exploded directory or a war file of a Web Facet artifacts on make. Just select the desired Web Facet in GWT Facet settingsinclude the GWT Compiler Output element in the artifact layout. An individual relative output path for each GWT module can be specified in GWT Facet settings as well.
Use "GWT configuration" to run/debug a GWT application in the hosted mode. Also "Run" action is available in the popup menu for GWT entry point classes and html files allowing to run a GWT application the hosted mode immediately. If AppEngine is used in the project GWT configuration allows to specify AppEngine Dev Server as a target server.
GWT Studio comes bundled with IntelliJ IDEA starting from IDEA 6.0.