Tonight's Google Wave Meetup presented by David Byttow

David Byttow presented Wave API in tonight's Bay Area Google Wave Meetup. Here are some of the notes I wrote down.

In the beginning of today’s session, David goes through embed, gadget, and robot API. Then he went into something new and exciting: Zombies (I know... it is not really not great a name). Zombies are robots running on the client-side, most likely inside the gadgets.

Zombies

- robots running on the client

- client-side sandbox environment

- allows gadgets to have robots-like api

example uses:

- syntax highlighting

- auto-correction and formatting

- client ui modification

Zombies is an internal name, it may not be released under this name. Several people in the meetup suggested the name Implant instead of Zombies as they feel that is a more accurate description.

Google Wave Actionscript API - v0.2 out

Most of the major functionalities are working. It is tested on Wave developer sandbox. Yes, I get the sandbox access. :)

Google Wave Actionscript API - status update

Most of the major functionalities should work. Will fix a couple more issue on Sunday.

The code can be downloaded at http://code.google.com/p/wave-as-client/source/checkout

Google Wave API Introduction

What type of things you can do beyond the standard Wave:

Developers can use the Wave API to extend the functionalities. Wave API allow us to implement new application that runs on Wave server (ie. Robot api), or client-side application that runs within a wave (ie. Gadget api). It also allows external website to add Wave functionalities to their site (ie. Embed api).

3 types of Wave API

1. Robot
2. Gadget
3. Embed

Robot

Robot api allows developer to build an automated program that fills the role of a Wave participant.

API Language: Java, Python

The example of what this api can do include:

Translation robot: robot that automatically translates the text.

Link robot: robot that automatically change the typed link into a hyperlink.

Gadget

Gadgets are client-side program that can be run inside a wave. Wave itself is a gadget container.

API language: javascript

example: putting a voting gadget within the conversation to allow people to vote on a particular choice.

Embed

Embed api allows another web site to embed Wave on it. Right now, this is still quite limited. It basically contains an iframe where you can place a WavePanel in it. Then the website can add participant, add reply, or load an existing conversation.

API language: javascript