phildownes@redweb.com
Nov 19, 2009
  6706
(5 votes)

Google Wave EPiServer Gadget

Here is my contribution to the EPiServer Gadget Contest 2009.

I’ve decided to integrate Google Wave into an EPiServer gadget. An EPiServer gadget of this nature could be developed further as Waves could be set up for communication between Editors, Editors and Admins, Editor/Admin to Partners, Editor/Admin to EPiServer and Anonymous users to Editors.

Currently this proof of concept implements the Google Wave Panel API and embeds a specific Google Wave into the gadget. The API available at present is rather limiting but I’m sure Google will expand it over time.

Obviously for this you need EPiServer 6 CMS CTP 2, Microsoft ASP.MVC and Google Wave (Sandbox) Activated Account (and friends to talk to).

On first load of the Google Wave Gadget the user is presented with the Google Wave login prompt. Login into Google Wave in a new tab in the browser.

img1 

You will then need to tell the EPiServer Gadget which wave you wish to load. To do this find the Google Wave ID from the Debug link in the Google Wave Interface.

img2

I’ve opened up the following wave to public access to allow it to be loaded in through the Google Wave Embed Panel API.

img3

Now edit the setting for the EPiServer gadget and enter the wave ID (without the wavesandbox.com! bit). Click OK and your wave panel should now display with the EPiServer gadget and be fully editable.

img4

My submission is certainly not a polished gadget but more a proof of concept which definitely has the potential to be expanded on as the Google Wave API is opened up.

Enjoy.

Download Source

Nov 19, 2009

Comments

Sep 21, 2010 10:32 AM

Very nice! :)
/ André Brynildsen

Please login to comment.
Latest blogs
Optimizely CMS 13: Why Search & Navigation Now Means Graph Migration

Optimizely CMS 13 makes Graph a required part of the platform. Here is what that means in practice for teams moving from Search & Navigation, with ...

Wojciech Seweryn | Apr 8, 2026 |

Jhoose Security Module V3.0.0 – Site-Level Security Configuration for Optimizely

Jhoose Security Module updated for Optimizely CMS 13, introducing separate packages for CMS 12 and 13 with ongoing support and enhancements.

Andrew Markham | Apr 6, 2026 |

Searchable settings page

In my current project which has been actively developed for quite some time we have a big classic settings page. Unfortunately the placement and...

Per Nergård (MVP) | Apr 6, 2026

Using Azure Devops Pipelines in Optimizely SAAS (Configured) Commerce

Introduction When working with SAAS Commerce build service v2 your currently need to use a github repo with configured branches to start deployment...

Mark Hall | Apr 4, 2026 |