phildownes@redweb.com
Nov 19, 2009
visibility 6906
star star star star star
(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

error Please login to comment.
Latest blogs
Composition Over Inheritance: Why Your Content Contract Is Not a Base Class

Inside the structural conformance pattern in SaaS CMS — from server-side inheritance to pipeline governance. A contract in Optimizely SaaS CMS is...

Vipin Banka | Sep 19, 2026

Optimizely Opti ID Integration: Why the API Key Was Missing from the DXP Management Portal

While working on an Optimizely CMS 12 Opti ID integration recently, we ran into an issue that initially appeared to be related to SSO authenticatio...

Madhu | Sep 18, 2026 |

Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |

Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

Stanisław Szołkowski | Sep 17, 2026 |