According to Google Wave API Tech Lead Douwe Osinga, Google Wave is scheduled to open up to the public on September 30th. This is grewat news for those like me whome are patiently waiting for access to the platform and all that it has to offer. Osinga has outlined specific areas of improvement and new features. Listed below:
Extensions
Design good flow for adding extensions, which includes:
Enabling users to easily discover extension installers
Browsing experience for insert gadgets and robots from a gallery
Enabling user management of their installed extensions (& easily de-install)
Stretch goal: Expand the extension system with more hooks and actions.
The goal, in the short term, is to make it easier for a givenextension to hook into conversations without being actively added towave. For example, right now you can insert a YouTube gadget from alink to a YouTube video. We’ll open it up to let an extension triggeron a regular expression over any link, so you can build all types of“previewers.” This mechanism will not just trigger for linkannotations, but for any annotation.
Robots
- New Robots wire protocol (v0.2)Shortly we will publish the proposed next version of the robots wireprotocol. We’d love to get your feedback prior to implementing it.
– Java and Python API parityGetting the two APIs to have feature parity
– Robot Gateway / OpenSocial RPC AccessRobots only react to events right now. By allowing the robots toauthenticate themselves through the OpenSocial RPC protocol, robotscan create and retrieve waves without being triggered by the wavesystem first, which will allow for more “active” robots.
– Better multiple wave accessRight now it is hard to create robots that keep multiple waves insync. We’ll add support to updates waves “blindly” (i.e. withoutknowing for sure what their current context is) in a less dangerousway by allowing to update annotated ranges in another wave and further more make it possible to bring waves outside of the current context into context.
– Sunset the existing robots cron mechanismAfter we open the Robot Gateway, the basic wave cron system will nolonger be needed since robots could use Google App Engine’s nativecron system or the Google App Engine Task Queue API.
– Gateway supportImprove the current tweety type of access to support outsideaddresses of the form address+ro…@appspot.com. These addresses will come with their own profiles and will make it possible to bettersupport actions on behalf of external entities.
Gadgets
- Full OpenSocial gadget supportWhile we already support the underlying gadget XML and relatedfeatures, we will add full support for the OpenSocial JavaScriptlibrary (i.e. feature requires=”opensocial-0.9″)This includes a mapping of the OpenSocial concepts onto the waveconcepts and supporting the actual OpenSocial APIs as well asgadgets.io.makeRequest.
– DiffOnOpen/Playback state mode for gadgetsGagdets currently automatically support playback, but sometimes youwant to be able to do something explicitly (e.g. in a chess game showthe previous place of a piece). The same goes for diff-on-open. Currently gadgets only show the current state – with diff-on-open support they will be able to show the user what has changed since last time.
– Google Web Toolkit (GWT) gadgetsFor complex gadgets, GWT is a rather nice way to develop. We’llprovide a library to build gadgets inside of GWT and a small framework to run the same code outside of wave to make debugging with an actual debugger possible.
Embed
- Expanded UI configuration:Switches to display toolbar, participant list, bottom tools.- Methods to switch the wave in and out of edit mode- Stretch goal: Read-only anonymous access so people don’t have to be logged into Google Wave to see embedded waves.
Future Thoughts
Following September 30th, we have several things in mind, but it’ll be important to see what gets built in the meantime and hear yourfeedback on the APIs as things evolve.
Some ideas we’re currently thinking about for later in the year:- Expand the number of hooks extensions can plug into (via regularexpressions)
- Enable robots that aren’t required to use Google App Engine
- Provide an API for robots to access attachments, search and contact
- Explore tools for improving the robot development/debug experience
- Expand the embedding API to cover more use cases
[+/-] Show Full Post...
[+/-]Hide Full Post...