Google Wave Dev Preview

As a visitor, Google I / O broadcasts gave me access to the Google Wave developer preview.
Impressions, in short, are: a useful and cool thing, but unfinished, which, in principle, is normal for previews.

What is

What is ready:

• Interface with nice windows
• A list of folders that are not actually folders, but search queries
• List of contacts
• List of u ... wave `s. "Waves"? Wavewave? I wonder how they translate it into Russian ...
• Themselves wavelets. Editing them.

In general, you can go to the post russianversion and see a demonstration with Google I / O. They really showed all that is.

What is not:

• Any trifles. Type checking for an empty name when adding a contact to the list. Or remove the contact from the list. Or the opportunity to look at userpics of other users, if it is not the developers of the service. eight)
• Central storage extensions. There is a documentation section with code examples, but there is, say, no Rosy bot from the demo. And that Rosie, by the way, is a simultaneous interpreter!
• Glitches ...

What can be done

Actually, it is granted access to the Wave on request . And the application implies that you want to write an extension. eight)
So I’ll tell you how it works.
You have contacts. And there are "wave". You can create a "wave" and write it alone, or you can add contacts there and they will see and edit it. A wavelet consists of wavelets and contains at least one wavelet. A wavelet is a type of comment stream, in their blip terminology (blip). Flat, not branching. But any blip can be the beginning of a new wavelet and a total branching out. Blip contains some content. Text, pictures ... And it can be edited not only by the creator, but by anyone who sees. Now you can and about the extension.
')

Extensions

Extensions come in three types: Robot, Gadget, and Embed.
Robot is a robot. Some type of user, which can be added to your contact list and from there to the wave. For example, the Tweety bot, being added to the wave, immediately throws the login form on Twitter into it, and when filling it out, the twitter login of the logged in user casts out into the same wave. And the Rosy bot translates from insignia to language all the inscriptions that appear in the wave. But, as I said, Rosie hasn’t been able to touch it yet.
Gadget is a piece of code that can be put into a wave and everyone will see it. For example, put a google map there, look in the right way and put markers. Anyone who is currently watching the wave will see your actions in real time. Also, for example, there is an example of a sudoku gadget code. That is, put the puzzle into a wave and collectively solve it ... In principle, anything can be done. That is, the gadget has some state, which is described by a piece of XML, and Wave synchronizes it automatically.
Embed is a kind of thing that allows you to export wavelets somewhere. In a blog, for example. Or in the comments feed on Youtube. Or where you come up with.

That's all for now. It looks very promising. In any case, I would gladly try to talk with friends in this style. But no one with you yet. If anything, my account alexzam@wavesandbox.com, write. And itching already to write the extension is another. I choose an idea. eight)

By the way, links: Official website , API Website .