Announcements  - 
Thanks to everyone who presented in or watched the #GWT  community hangout!

The video link: GWT Community Hangout January 2014  

I'll give a brief summary and set of links (in the order of presentation):

+Leif Åstrand: Dev mode in javascript
Leif presented an interesting proof-of-concept app for a dev mode plugin that runs entirely without browser plugins, as well as a nice rundown of how devmode and superdevmode work.

+Nikolas Gauvreau: The Universe Project
Project: G+:
This is a real-time MMORPG written entirely in GWT; parts of it are open source, and if we encourage him and his team, it sounds like we can get more open sourced goodies!

+Andrés Testi: Extending GWT.create
Slides: Discussion:!topic/google-web-toolkit-contributors/zA_JfcxrIq0
Formal Proposal Document:

Andrés has been working extensively to add support for multiple arguments to GWT.create, as well as "rebound methods" which allow passing values from a method call into GWT.create, for added robustness.

+Colin Alworth: Parsers in GWT with JavaCC
Source: Slides:

Colin presented an implementation of JavaCC that allows you to create a syntax parser which runs in GWT, and can understand java, arithmetic or any other syntax JavaCC can support (almost anything).

Last, but certainly not least: Job offers!
A link with full descriptions is here:


"Vaadin is hiring. We can offer different types of tasks depending on customer demand and your own preferences:
* Contribute fixes and new features to the core GWT framework.
* Help customers build custom widgets or applications and provide support for their GWT projects.
* Hold GWT trainings and improve the training material.
You can find out all the details at "


VisualDna: "We migrated most of our existing PHP+UI Templates+JS to GWT. What was built in 5 years we moved to GWT in less than 3 months. We are looking now for experienced GWT developers to help us improve the existing codebases and build new ones for the next projects. There are so much to do and big things to achieve. 
We also use maven, cassandra, mysql, guava, guice, angularjs, grunt, kafka, jenkins, jira, crucible and many other exciting things.
Our main office is in London, UK.
You can expect a good salary, many benefits and share options. To apply and have more information here:"


Appian: "As a Senior Software Engineer working on the Appian platform, your mission will be to ensure Appian is always fast, scalable and up to whatever tasks our customers configure it to do. You will be solving problems of scale and flexibility that most engineers never see, building a product capable of serving our customers in ways you never imagined. Your scope extends from the high-performance data layer to the cross-platform user interface. This position requires the mental agility to jump from the deep code-level view of Appian, to the designer’s view, to the end user’s view, and back again. Learn how to write software that runs software, and enhance Appian's cross-platform functional programming language, using GWT, Android or iOS.

Appian offers excellent pay, benefits and work environment out of the Washington DC area; Appian is consistently ranked one of the best places to work in the Washington DC area!  See for details"


Finally, if you are interested in working as or hiring a GWT developer, be sure to check out the gwt-employment-group!!forum/google-web-toolkit-employment
Leif Åstrand's profile photoColin Alworth's profile photoJames “X” Nelson's profile photoJonathan Strootman's profile photo
I realized I might have given a too pessimistic answer when +Daniel Kurka asked about the performance of my devmode hack. The reason for this is that the only complex GWT module I have tested it with was Vaadin's client-side, where the reload time went from seconds to minutes compared to normal devmode. The code in question is, however, heavily "optimized" to use JavaScript arrays and objects instead of List and Map<String, ?>. These are significantly faster in the compiled code, but they do cause lots of jumping between Java and JavaScript, which is exactly the weak spot of the communication method my approach uses.

Based on that observation, my revised answer is that I don't know how slow it is because I haven't done any meaningful benchmarking.
+Leif Åstrand if you (or your users) spend a lot of time in dev mode working on code like that, you can give it a significant perf bump by marking the 'optimized' class as `@GwtScriptOnly`, sticking it in a super-source directory, and making a pure-java version in your normal source tree. Autobeans and RPC both use this to make use of JVM json libraries when in Dev Mode, but compile out to use the browser's own capabilities.
Add a comment...