The Google Wave preview has officially been scheduled to open up to the public on September 30th according Wave API Tech Lead Douwe Osinga.
Leading up to opening up of the Google Wave preview, Osinga has outlined specific areas of improvement and new features in the official Google Wave group:
Extensions
Design good flow for adding extensions, which includes:
This is part 3 of my Google Wave developer sandbox review. Part 1 and part 2 were both an introduction to some wave concepts. In this part we’ll be taking a look at the Google Wave Gadget API by writing a simple rating gadget. If you don’t know what gadgets are or what they do, please read my previous post here.
The gadget I have written is supposed to be used when you want wave participants to rate something inside your wave (or the wave itself). You simply add the gadget to your wave, set the title and you’re good to go. I also wanted the gadget to have a settings menu that was only visible by the person who added the gadget to the wave.
The last blog post, Understanding Google Wave, discussed the architecture and technical underpinnings of Google Wave. In this post, we will look at different ways of developing with Google Wave.
There are three ways you can extend or use Google Wave in your applications.
Embedding Wave
You can embed a Wave into a web page by adding some simple JavaScript code.
The Wave Embed API provides the WavePanel object which can hold a wave. You ask the WavePanel to use an HTML element on your web page to show a wave. The conversations on the wave will be visible in the WaveClient.
The steps to embed a wave on a web page are -
