Kate (![[info]](http://l-stat.livejournal.com/img/userinfo.gif){kind=small} x_mass) wrote,@ 2009-06-05 21:44:00 |
|
wave looks seriously seriously cool
Warning this is an 80 minutes intro from the google IO conference
1. Wave is an open source comms protocol and API library built on our collective knowledge of wiki's, BBS, SMS, IM, blogging, e-mail, content management, source control, etc. The google team will also be open sourcing the lions share of the code they have developed.
2. The wave is a based on a tree structure, that allows replication of any part of the tree or a complete tree. The tree is a set of objects e.g. data objects (whatever their source) and the wave itself can be embedded along with its functionality. Thus wave/tree can be embedded (by drag'n'drop) in other wave/trees. There are all the usual management tools such as folders themselves built on/in wave.
3. There are server side apps associated with the web site/host and browser side apps that run on HTML 5 or extensions written in gears. It doesn't matter which wave server you belong to, you can have access to waves anywhere. If you have been added into a particular branch of a tree, the wave propagates to your server. Equally if you don't have access to other parts of the wave/tree you won't know, nor will they propagate to your server, staying only on their host.
4. the integration of e-mail and IM with whiteboard and thread management is great
5. the replay conversation from start is both obvious and I want it now!
6. Copying data objects to and from waves is seamless (albeit requires gears). Data objects such as characters, pictures, sound, code, meta etc. Also copying waves into other formats such as blogs is also seamless yet retains all the functionality of the wave.
7. obviously it works seamless across any device with a browser
8. Being a whiteboard type app obviously data objects can be edited on and modified by anybody in the wave (and changes are recorded so that new people can follow who did what when and why). The wave is edit locked on a per data object basis, so for example N people can be interactively editing a wave simultaneously.
9. As a wave is a set of objects, the recording/playback tool can be used on individual objects or groups of objects.
10. Data objects can be searched upon.
11. Form handling is built in, allowing forms to be handled collaboratively be they human or "robots" (server side gadget objects)
12. The api lets anybody create open server side gadget objects that can be embeded in web pages in a firefox manner. These gadget objects can be robots that automate certain functions for example find links in text. Or allow you to publish the wave into a blog etc. Or search on objects be they data or people and group those objects any way you want. Or live interactive maps. Or even games be they collaborative such as suduko or competitive such as chess. However a couple of very cool robots stand out
One example given was a context sensitive spellchecker that correctly flags when I type that "its bean a long time since i had been soup" that I have spelt bean/been wrong. it can do this in line automatically.
Another example that built on the spellchecker to provide inline translation, for example writing I'm playing D&D with people in France, Germany and the Netherlands, were all typing and reading in our respective languages no matter what language they were originally typed in.
The control is via the client browser, the capability is added server side on the website/wave server.
13. Equally applications that mediate between waves and applications (such as twitter) can be added. So for example replying to a twitter wave extension posts that reply in twitter in reply to the original post. it all so updates the wave with tweets alerting (and obviously you to changes. Another example is bug/issue/version tracking.
14. Any "extension" can be added simply by clicking on it.
i'm going to sort this out and shorten this in a bit
Warning this is an 80 minutes intro from the google IO conference
1. Wave is an open source comms protocol and API library built on our collective knowledge of wiki's, BBS, SMS, IM, blogging, e-mail, content management, source control, etc. The google team will also be open sourcing the lions share of the code they have developed.
2. The wave is a based on a tree structure, that allows replication of any part of the tree or a complete tree. The tree is a set of objects e.g. data objects (whatever their source) and the wave itself can be embedded along with its functionality. Thus wave/tree can be embedded (by drag'n'drop) in other wave/trees. There are all the usual management tools such as folders themselves built on/in wave.
3. There are server side apps associated with the web site/host and browser side apps that run on HTML 5 or extensions written in gears. It doesn't matter which wave server you belong to, you can have access to waves anywhere. If you have been added into a particular branch of a tree, the wave propagates to your server. Equally if you don't have access to other parts of the wave/tree you won't know, nor will they propagate to your server, staying only on their host.
4. the integration of e-mail and IM with whiteboard and thread management is great
5. the replay conversation from start is both obvious and I want it now!
6. Copying data objects to and from waves is seamless (albeit requires gears). Data objects such as characters, pictures, sound, code, meta etc. Also copying waves into other formats such as blogs is also seamless yet retains all the functionality of the wave.
7. obviously it works seamless across any device with a browser
8. Being a whiteboard type app obviously data objects can be edited on and modified by anybody in the wave (and changes are recorded so that new people can follow who did what when and why). The wave is edit locked on a per data object basis, so for example N people can be interactively editing a wave simultaneously.
9. As a wave is a set of objects, the recording/playback tool can be used on individual objects or groups of objects.
10. Data objects can be searched upon.
11. Form handling is built in, allowing forms to be handled collaboratively be they human or "robots" (server side gadget objects)
12. The api lets anybody create open server side gadget objects that can be embeded in web pages in a firefox manner. These gadget objects can be robots that automate certain functions for example find links in text. Or allow you to publish the wave into a blog etc. Or search on objects be they data or people and group those objects any way you want. Or live interactive maps. Or even games be they collaborative such as suduko or competitive such as chess. However a couple of very cool robots stand out
One example given was a context sensitive spellchecker that correctly flags when I type that "its bean a long time since i had been soup" that I have spelt bean/been wrong. it can do this in line automatically.
Another example that built on the spellchecker to provide inline translation, for example writing I'm playing D&D with people in France, Germany and the Netherlands, were all typing and reading in our respective languages no matter what language they were originally typed in.
The control is via the client browser, the capability is added server side on the website/wave server.
13. Equally applications that mediate between waves and applications (such as twitter) can be added. So for example replying to a twitter wave extension posts that reply in twitter in reply to the original post. it all so updates the wave with tweets alerting (and obviously you to changes. Another example is bug/issue/version tracking.
14. Any "extension" can be added simply by clicking on it.
i'm going to sort this out and shorten this in a bit
