YouTube - Google Wave Developer Preview at Google I/O 2009

Comments

• Public Comments

  • Al Stevens

    6 months ago

    
    
    

    This is a long video: 1 hour and 20 minutes. I took some notes while watching. They're pretty high level, but may help you skip to the parts of the video you are most interested in.
    
    Notes:
    
    Google unveils Wave, an HTML 5 App, running in a browser. Presented as an early developer preview.
    
    Main presenters are Lars and Jens Rasmussen, the two brothers who did Google Maps and Stephanie Hannan, PM. Wave was developed in Sydney, Australia.
    
    3 part presentation: Demo, API's and Protocol. (Also called the 3 P's Product, Platform, Protocol)
    
    What might email look like if it were invented today. Email mimics snail mail, collating related messages into related conversations or threads. Wave starts out with the definition of a conversation as a lightweight tree structure of messages and a set users participating in that conversation. A conversation object is a shared object sitting on a server somewhere. Users participating add to the conversation.
    
    A message can be drafted by a single user, and then others can be added. The added users can reply in the message itself, adding their replies exactly where they want. Other users can add to these internal threads. IM style of communication can be done in the same wave, with updates, character by character, odne in real time.
    
    Since A wave is a tree structure of messages. Any part of the tree can be restricted, so side conversions can be supported.
    
    Drag and drop from desktop to the browser is currently not supported by HTML 5, so photo dragging requires an extension.
    
    Features from a wave can also be extracted and put in a new one.
    
    There is an embed API. As an example, Bloggy embeds the wave in the blog, complete with full interactivity. Using Bloggy, you can add full group discussions on any site.
    
    A mobile version runs on iPhone and Android.
    
    Edits update in real time. This enables collaborative authoring, integrating discussion and content collaboration in one tool. Anyone who sees an original message, sees changes by other participants marked as changes. Anyone seeing the document for the first time, sees the net result. But they can use playback -- a feature that allows you to see the entire history of the wave -- to see the original plus the changes. Since we have accountability, we allow anyone on a wave to edit it.
    
    The product of a wave can be another wave. If a wave is used to collaboratively create a document, when done, the result can be exported into another wave. This is similar to a version control system -- you can see the history, or the final result.
    
    Wave is 100% built with the Google web toolkit. It's written in Java and then translated into html/javascript/css. Making it work on mobile devices adds about 5% extra engineering.
    
    You end up with lots of waves, so there are organizing tools. These include folders, titles and tags. But, also a wave can be used to organize other waves. Dropping a wave into another wave adds a wavelink -- wiki-like.
    
    Spell checker is context sensitive. "Been soup" will get corrected to "bean soup".
    
    A Robot is a server side program that participates in a wave. It has full functionality -- access to history, collaboration, wave creation. Spelly is such a robot. It sits on the server and uses collaborative editing to make changes or correct suggestions. Linky watches for links. (Bloggy, earlier publishes a wave on a blog.) Searchy, in the wave pops up a search, lets you find an image or page and insert it into the wave.
    
    Client side API. Any open social gadget can fit inside a wave. Also make available an api that lets developers make their gadget live and collaborative. API is hosted on code.google.com. Gadgets are easy to make -- they demonstrate a yes/no/maybe gadget. Sample games demonstrated include sudoku and chess, which are, of course, sharable. Then with playback, you can watch the entire game. An embedded map lets users see zoom level and other changes in real time.
    
    
    The gadget API requires developer only to store updates to the local xml.
    
    Forms are native to waves. They can be filled out collaboratively.
    
    Robots are server side. Examples include Polly the Pollster, built completely within wave, illustrates a robot that makes it really easy to collobratevely create, run and analyze a poll.
    
    Wave can also integrate with other systems. Twave uses twitter and creates a tweet stream in a wave.
    
    Wave can integrate with existing workflows. Buggy lets you highlight text, and file it in issue tracker. Comments in the wave update the bug tracking system. Additions to the bug tracker update the wave.
    
    The lion's share of the wave code will be open sourced, including the current UI and a reference implementation of the federation protocol.
    
    Federation is hard, but will make the openness actually work. Wave is open, in the same sense as email. Separate wave systems can interact. Servers cooperate using a federation system. Clients in each wave system communicate with their servers -- down to the character level. Servers communicate using the fedearion system and pass the character typing up to their clients. Protocol allows for private interactions within a wave system. The private data will never leave the servers. Federation protocol is at an early stage.
    
    A final robot demo, Rosie the translation robot, speaks 40 languages and translates in real time.
    
    Lot's of applause.
    
    In summary, Wave is a simple communications object that can be used for lots of communication and collaboration, email, blogging, photo sharting, wiki's, collaborative documents, extension api's that can be used for integration with other systems and workflows.
    
    All attendees get accounts. Key URL's are:
    
    Product: wave.google.com
    Platform: cod.google.com/apis/wave
    Protocol: www.waveprotocol.org

    This is a long video: 1 hour and 20 minutes. I took some notes while watching. They're pretty high level, but may help you skip to the parts of the video you are most interested in.<br /><br />Notes:<br /><br />Google unveils Wave, an HTML 5 App, running in a browser. Presented as an early developer preview.<br /><br />Main presenters are Lars and Jens Rasmussen, the two brothers who did Google Maps and Stephanie Hannan, PM. Wave was developed in Sydney, Australia.<br /><br />3 part presentation: Demo, API's and Protocol. (Also called the 3 P's Product, Platform, Protocol)<br /><br />What might email look like if it were invented today. Email mimics snail mail, collating related messages into related conversations or threads. Wave starts out with the definition of a conversation as a lightweight tree structure of messages and a set users participating in that conversation. A conversation object is a shared object sitting on a server somewhere. Users participating add to the conversation.<br /><br />A message can be drafted by a single user, and then others can be added. The added users can reply in the message itself, adding their replies exactly where they want. Other users can add to these internal threads. IM style of communication can be done in the same wave, with updates, character by character, odne in real time. <br /><br />Since A wave is a tree structure of messages. Any part of the tree can be restricted, so side conversions can be supported.<br /><br />Drag and drop from desktop to the browser is currently not supported by HTML 5, so photo dragging requires an extension.<br /><br />Features from a wave can also be extracted and put in a new one.<br /><br />There is an embed API. As an example, Bloggy embeds the wave in the blog, complete with full interactivity. Using Bloggy, you can add full group discussions on any site.<br /><br />A mobile version runs on iPhone and Android.<br /><br />Edits update in real time. This enables collaborative authoring, integrating discussion and content collaboration in one tool. Anyone who sees an original message, sees changes by other participants marked as changes. Anyone seeing the document for the first time, sees the net result. But they can use playback -- a feature that allows you to see the entire history of the wave -- to see the original plus the changes. Since we have accountability, we allow anyone on a wave to edit it. <br /><br />The product of a wave can be another wave. If a wave is used to collaboratively create a document, when done, the result can be exported into another wave. This is similar to a version control system -- you can see the history, or the final result.<br /><br />Wave is 100% built with the Google web toolkit. It's written in Java and then translated into html/javascript/css. Making it work on mobile devices adds about 5% extra engineering.<br /><br />You end up with lots of waves, so there are organizing tools. These include folders, titles and tags. But, also a wave can be used to organize other waves. Dropping a wave into another wave adds a wavelink -- wiki-like.<br /><br />Spell checker is context sensitive. "Been soup" will get corrected to "bean soup".<br /><br />A Robot is a server side program that participates in a wave. It has full functionality -- access to history, collaboration, wave creation. Spelly is such a robot. It sits on the server and uses collaborative editing to make changes or correct suggestions. Linky watches for links. (Bloggy, earlier publishes a wave on a blog.) Searchy, in the wave pops up a search, lets you find an image or page and insert it into the wave.<br /><br />Client side API. Any open social gadget can fit inside a wave. Also make available an api that lets developers make their gadget live and collaborative. API is hosted on <a href="http://code.google.com" rel="nofollow" target="_blank">code.google.com</a>. Gadgets are easy to make -- they demonstrate a yes/no/maybe gadget. Sample games demonstrated include sudoku and chess, which are, of course, sharable. Then with playback, you can watch the entire game. An embedded map lets users see zoom level and other changes in real time.<br /><br /><br />The gadget API requires developer only to store updates to the local xml.<br /><br />Forms are native to waves. They can be filled out collaboratively.<br /><br />Robots are server side. Examples include Polly the Pollster, built completely within wave, illustrates a robot that makes it really easy to collobratevely create, run and analyze a poll.<br /><br />Wave can also integrate with other systems. Twave uses twitter and creates a tweet stream in a wave.<br /><br />Wave can integrate with existing workflows. Buggy lets you highlight text, and file it in issue tracker. Comments in the wave update the bug tracking system. Additions to the bug tracker update the wave.<br /><br />The lion's share of the wave code will be open sourced, including the current UI and a reference implementation of the federation protocol.<br /><br />Federation is hard, but will make the openness actually work. Wave is open, in the same sense as email. Separate wave systems can interact. Servers cooperate using a federation system. Clients in each wave system communicate with their servers -- down to the character level. Servers communicate using the fedearion system and pass the character typing up to their clients. Protocol allows for private interactions within a wave system. The private data will never leave the servers. Federation protocol is at an early stage.<br /><br />A final robot demo, Rosie the translation robot, speaks 40 languages and translates in real time.<br /><br />Lot's of applause.<br /><br />In summary, Wave is a simple communications object that can be used for lots of communication and collaboration, email, blogging, photo sharting, wiki's, collaborative documents, extension api's that can be used for integration with other systems and workflows.<br /><br />All attendees get accounts. Key URL's are:<br /><br />Product: <a href="http://wave.google.com" rel="nofollow" target="_blank">wave.google.com</a><br />Platform: <a href="http://cod.google.com/apis/wave" rel="nofollow" target="_blank">cod.google.com/apis/wave</a><br />Protocol: <a href="http://www.waveprotocol.org" rel="nofollow" target="_blank">www.waveprotocol.org</a>

    • Some HTML is allowed.
    • Reply
    • Cancel
    • Submit
    Commented in: Google Wave

    • shal

      6 months ago

      
      
      

      Great review Al! Thank you!

      Great review Al! Thank you!

      • Some HTML is allowed.
      • Reply
      • Cancel
      • Submit
      Commented in: Google Wave
  Add a Comment

Here's a list of the HTML tags we allow: