Hi guys,

so I just started developing Wave Gadgets and I'm currently using GWT.
While there are obvious benefits such as unit testability, cross-
browser support and code-splitting, there are also some downsides. For
instance I cannot easily test gadgets locally (not to mention testing
robots!). I had to create a local mock implementation of the wave API
for testing and every time I use a new API feature I have to add it to
my mock implementation. All in all it feels kind of clunky and
strange.

Are there any easier ways to develop (possibly very complex) wave
gadgets? What do you guys use?

In case you are interested, I wrote a tutorial in how to get started
developing gadgets with gwt. Also, I guess I will be uploading my
WaveMock framework to Google Cloud this week (if anybody is
interested):

http://thezukunft.com/2010/02/08/a-wave-gadget-robot-using-gwt-2-0-and-google-app-engine-part-1/

Cheers, Jonas

-- 
You received this message because you are subscribed to the Google Groups 
"Google Wave API" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-wave-api?hl=en.

Reply via email to