...
There are many opportunities surrounding Fedora to create user interface experiences. Many times it is preferred that these interfaces be deployed via a web browser. One specific example of this is seen in the plan to replace the Some examples of potential interfaces to build using these tools are a replacement Fedora Administrative GUI with a web-based solution, a Fedora Share application, object builder applications, and server monitoring applictaions. This comparison considers the capabilities and benefits of several tools for building rich internet applications. The goal of this comparison is to aid developers in determining the appropriate tool(s) to use when building UIs for Fedora. Since many of these tools will need to work directly against the existing Fedora REST and SOAP APIs, special attention will be given to each tool's ability to connect to these services.
Disclaimer
These write ups are generally completed after conducting research about the tool and experimenting with using it for a day or two. If you have implementation experience with a particular tool feel free to add notes or comments.
...
Being able to work in Java in a manner resembling Swing is nice, but it also reminds me how long it takes to create even a simple UI. Learning how to use all of the GWT-specific classes (and learning which standard Java classes and libraries to not use) would take time similar to that of learning how to use components in an XML syntax. Not being able to access REST or SOAP interfaces directly without being on the same host/port is a major drawback.
Others
Echo2/3
Similar to GWT except that rather than compiling to Javascript, the Java code runs on the server, producing the UI and storing state on the server side. See: Comparing the Google Web Toolkit to Echo2 . Creating an application which runs only on the client is not possible with Echo.