39 messages in com.googlegroups.google-gadgets-apiRe: README: Authors of Inlined (type=...
FromSent OnAttachments
Dann (Google Employee)08 Nov 2007 10:03 
Bonstio (Guru)08 Nov 2007 10:48 
Matt (Guru)08 Nov 2007 12:49 
Bonstio (Guru)08 Nov 2007 15:18 
Dann (Google Employee)09 Nov 2007 14:42 
Dann (Google Employee)09 Nov 2007 15:17 
Bonstio (Guru)10 Nov 2007 02:51 
Bonstio (Guru)15 Nov 2007 10:56 
Simon16 Nov 2007 07:58 
Matt (Guru)16 Nov 2007 08:50 
Bonstio (Guru)18 Nov 2007 04:33 
Dann (Google Employee)26 Nov 2007 14:09 
Bonstio (Guru)27 Nov 2007 12:04 
Dann (Google Employee)07 Dec 2007 17:42 
Bonstio (Guru)08 Dec 2007 02:14 
Simon09 Dec 2007 02:11 
Dann (Google Employee)10 Dec 2007 08:20 
Simon10 Dec 2007 15:46 
javalizard14 Dec 2007 06:18 
javalizard16 Dec 2007 09:44 
javalizard19 Dec 2007 10:26 
RandomName19 Dec 2007 10:31 
Steven Edwards19 Dec 2007 10:51 
TheWis19 Dec 2007 11:33 
paru...@gmail.com19 Dec 2007 11:37 
Dan (Google Employee)19 Dec 2007 12:25 
javalizard19 Dec 2007 12:29 
Alex19 Dec 2007 13:26 
bria...@google.com19 Dec 2007 13:46 
Steven Edwards19 Dec 2007 14:13 
Alex19 Dec 2007 14:16 
Alex19 Dec 2007 14:35 
Alex19 Dec 2007 15:20 
Steven Edwards19 Dec 2007 15:57 
Gregor20 Dec 2007 03:49 
Bonstio (Guru)20 Dec 2007 04:37 
Gary17 Jan 2008 16:44 
RandomName20 Jan 2008 19:50 
Gregor21 Jan 2008 10:08 
Subject:Re: README: Authors of Inlined (type="html-inline") Gadgets
From:Dann (Google Employee) (d.@google.com)
Date:11/09/2007 02:42:19 PM
List:com.googlegroups.google-gadgets-api

Hey Bonstio,

As always, thanks for the feedback. Answers to your questions below:

My question is this: on what basis will existing inline gadgets continue to be
supported? Uniquely selected by their URL or name?

We will continue supporting existing inlined gadgets based on their URL. If at some point, one of your inlined gadgets has moved and needs to be aliased to a new location, this is not a problem, and I'll be happy to satisfy this request for you. This also means that you can freely update your existing inlined gadget as you normally would without any restriction.

Hope that helps,

Dann

On Nov 8, 10:49 am, "Bonstio (Guru)" <bons@gmail.com> wrote:

Hey Dann

I can totally understand the need to do this and I must say it's not a total surprise either. Standardizing is good and I can surely see the disadvantages in terms of brittleness and security.

I would have been extremely bitter about many lost hours of development - and users - were it not for the fact that you will continue to support existing inlined gadgets so I'm very pleased that you've collectively decided to do this - nice one, thanks! And thanks for the up-front notice too :)

My question is this: on what basis will existing inline gadgets continue to be supported? Uniquely selected by their URL or name? A manual developer initiated request? Some of my gadgets live at two different URLs. I suppose I could submit an alias request to overcome this. I'd just be interested to know how you are going to work this.

CHEERS,

-Greg

On Nov 8, 6:03 pm, "Dann (Google Employee)" <d.@google.com> wrote:

Hey everyone,

Realizing that this may be a sensitive topic, I want to give everyone *advanced* notice that inlined gadgets (type="html-inline") will soon be deprecated from the Gadgets API.

This is an important announcement which I hope will reach as many developers as possible. For authors of existing inlined gadgets, you needn't worry. Your gadgets will continue working as normal. There are some subtleties around what this exactly means, and I'll try to explain them below. I don't have an ETA on when this will happen, but please expect for it to happen soon. The main goal is to give you all a heads up about this change. Feel free to post questions, and I'll do my best to answer them.

====

What does this mean? The deprecation of inlined gadgets means that new inlined gadgets can no longer be created after we turn on the switch. For inlined gadgets that already exist, they will continue to be supported and render as normal. This will just prevent any new inlined gadgets from being created. I can't announce exactly when we'll start the deprecation, but the earlier you start, the better the chances you'll make it in time.

Why? Inlined gadgets pose potential security risks to our users in addition to other complications with some API libraries, e.g. Analytics. They're more difficult to develop and cannot be syndicated via Google Gadgets For Your Webpage. This is one of the major reasons why inlined gadgets are generally less discoverable and don't get as much traffic as type="html" gadgets. Supporting inlined gadgets can be difficult because many inlined gadgets depend on specific DOM elements in the iGoogle container page. The container page can frequently change and essentially break your gadget. Just ask Bonstio and Matt ;). By deprecating inlined gadgets, it allows us to standardize the way gadgets are rendered and create a more consistent API resulting in a better developer experience.

Will inlined gadgets be closed forever? Initially, we will not be honoring requests to add additional inlined gadgets. In the future, we may consider allowing developers to submit a proposal to develop an inlined gadget and have it go through an approvals process. However, please understand that this is purely hypothetical at this point with no ETA. The current plan is that once we deprecate inlining, we will stop allowing new inlined gadgets, without exceptions.

Feedback? This announcement is intended to give advanced notice of this upcoming change. Feel free to post comments/questions, and I'll do my best to answer them.

Thanks!

Dann