Google Wave Dev Preview
As a visitor to Google I / O Broadcasts, they gave me access to the Google Wave development preview.
Impressions, in short, are: a useful and funny thing, but unfinished, which, in principle, is normal for a preview.
What is ready:
In general, you can go to the russianversion post and watch a demo with Google I / O. They really showed everything that is.
Why not:
Actually, access to Wave is granted upon request . And the application implies that you want to write an extension. 8)
So I’ll talk a little about how it works.
You have contacts. And there are wavelets. You can create a “wave” and write it alone, or you can add contacts there and they will see it and be able to edit it. A wavelet consists of wavelets and contains at least one wavelet. A wavelet is a type of stream of comments, in their terminology of "blip" (blip). Flat, not branching. But any blip can be the beginning of a new wavelet and branching comes out in total. Blip contains some content. Text, pictures ... And it can be edited not only by the creator, but by anyone who sees it. Now it’s possible about extensions.
Extensions come in three types: Robot, Gadget, and Embed.
Robot is a robot. Some type of user, which you can add to your contact list and from there to the wave. For example, the Tweety bot, when added to a wave, immediately throws a Twitter login form into it and, when completed, throws out the Twitter feed of the logged in user onto the same wave. And the Rosy bot translates interlinearly from one language to another all the inscriptions that appear in the wave. But, as I said, Rosie has not yet been able to touch.
Gadgetthis is a piece of code that can be placed in a wave and everyone will see it. For example, put a Google map there, look for the right way and put markers. Everyone who is currently looking at 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 in the wave and collectively solve it ... In principle, anything can be. 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. A blog, for example. Or in the comments feed on Youtube. Or where you come up with.
That's all for now. It looks, it seems, very promising. In any case, I would love to try to chat with friends in this style. But there’s no one yet. If anything, my account is alexzam@wavesandbox.com, write. And hands itch already write an extension is another. I choose an idea. 8)
By the way, links: Official site , Site API .
Impressions, in short, are: a useful and funny thing, but unfinished, which, in principle, is normal for a preview.
What is
What is ready:
- Interface with nice windows
- List of folders that are not actually folders, but search queries
- List of contacts
- List of e ... wave`ov. "Waves"? Waves? I wonder how they will translate it into Russian ...
- Waves themselves. Editing them.
In general, you can go to the russianversion post and watch a demo with Google I / O. They really showed everything that is.
Why not:
- Any little things. Type of check for an empty name when adding a contact to the list. Or remove a contact from the list. Or the opportunity to look at the userpics of other users, if these are not service developers. 8)
- Central repository extensions. There is a documentation section with code examples, but there, say, there is no Rosy bot from the demo. And that Rosie, by the way, is a simultaneous interpreter!
- Glitches ...
What can be done
Actually, access to Wave is granted upon request . And the application implies that you want to write an extension. 8)
So I’ll talk a little about how it works.
You have contacts. And there are wavelets. You can create a “wave” and write it alone, or you can add contacts there and they will see it and be able to edit it. A wavelet consists of wavelets and contains at least one wavelet. A wavelet is a type of stream of comments, in their terminology of "blip" (blip). Flat, not branching. But any blip can be the beginning of a new wavelet and branching comes out in total. Blip contains some content. Text, pictures ... And it can be edited not only by the creator, but by anyone who sees it. Now it’s possible about extensions.
Extensions
Extensions come in three types: Robot, Gadget, and Embed.
Robot is a robot. Some type of user, which you can add to your contact list and from there to the wave. For example, the Tweety bot, when added to a wave, immediately throws a Twitter login form into it and, when completed, throws out the Twitter feed of the logged in user onto the same wave. And the Rosy bot translates interlinearly from one language to another all the inscriptions that appear in the wave. But, as I said, Rosie has not yet been able to touch.
Gadgetthis is a piece of code that can be placed in a wave and everyone will see it. For example, put a Google map there, look for the right way and put markers. Everyone who is currently looking at 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 in the wave and collectively solve it ... In principle, anything can be. 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. A blog, for example. Or in the comments feed on Youtube. Or where you come up with.
That's all for now. It looks, it seems, very promising. In any case, I would love to try to chat with friends in this style. But there’s no one yet. If anything, my account is alexzam@wavesandbox.com, write. And hands itch already write an extension is another. I choose an idea. 8)
By the way, links: Official site , Site API .