Take the community feedback survey now.

phildownes@redweb.com
Nov 19, 2009
  6413
(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
Meet the newest OMVPs – summer 2025 cohort

We’re excited to welcome the latest group of Optimizely Most Valuable Professionals (OMVPs) into the program! This summer’s cohort highlights a ble...

Satata Satez | Sep 5, 2025

The Sweet Spot: Hybrid Headless Architecture

When it comes to content management architecture, the pendulum often swings between tightly coupled “headed” CMS setups and the flexibility of full...

Minesh Shah (Netcel) | Sep 4, 2025

Preview Unpublished Pages and Blocks on the Frontend (Optimizely CMS 12)

Introduction In my previous post , I explained how to customize the ContentArea rendering pipeline in Optimizely CMS 12 so editors can see...

Adnan Zameer | Sep 4, 2025 |

How to automatically remove orphaned Opti jobs from the DB

Optimizely CMS provides a simple yet powerful built-in job system that handles most standard scheduling scenarios with ease. Developers can easily...

Stanisław Szołkowski | Sep 4, 2025 |