- From: Marcos Caceres <marcosc@opera.com>
- Date: Mon, 8 Jun 2009 20:34:11 +0200
- To: Scott Wilson <scott.bradley.wilson@gmail.com>
- Cc: public-webapps WG <public-webapps@w3.org>
2009/5/31 Scott Wilson <scott.bradley.wilson@gmail.com>: > Hi everyone, > > Something that may be of interest if you've been following the announcement of Google Wave[1]. > > Back in January we discussed our W3C Widgets implementation (Wookie[2]), and our extensions to cover shared states and collaboration[3], a demo of which we brought to the Paris F2F. > > Well, Google Wave has a very similar API to our own for adding collaborative Gadgets to waves[4], so we've implemented the draft API and mapped it onto our existing functionality. We then tested this by taking the Google Sample Wave Gadgets[5], and converting them to W3C Widgets (removing Gadget markup, and adding config.xml). We've then successfully deployed these using Wookie in a web application (see screenshot[6]). > > These work pretty much as demonstrated by Google, but using our existing Wookie codebase, which uses Comet to achieve synchronous updates between Widget instances. > > (You can see how the API calls work in the test harness widget on the left of the screenshot). > > This raises the question as to whether and how we want to progress the collaboration/shared state Widget extensions? > I've not looked at this enough to comment, but can you describe what you have in mind in a bit more detail. Nice work on integrating the Wave stuff so quickly, btw. -- Marcos Caceres http://datadriven.com.au
Received on Monday, 8 June 2009 18:34:49 UTC