* The legacy API is officially deprecated as of today, September 14th.
* For three months, the legacy API will continue in its current state.
* On or around December 14th, any new gadget submissions to the
iGoogle directory must be using gadgets.*, in order to be accepted,
but existing gadgets may continue to use the legacy API.
* On the same date, the remaining inlined gadgets will be disabled.
* Finally, one year after deprecation, September 14th, 2010, gadgets
using the legacy API will cease to function on iGoogle, and the
majority of other Google-owned gadget containers (such as orkut,
Gmail, and Calendar).
In summary: all new gadgets should use the gadgets.* API. All existing
gadgets have one year to migrate to gadgets.*.
I'll be posting a migration guide and an XML conversion tool in the
next few weeks to help the transition.
I could not find any equivalent to _IG_Analytics and _IG_Drag in the
gadgets.* library. Am I correct in understanding that both the
features are deprecated/no longer supported? If so, why?
On Sep 15, 3:19 am, "Dan (Google)" <api....@google.com> wrote:
> After many faithful years of service, the legacy gadgets API is now
> officially deprecated. The complete announcement is available on the
> iGoogle Developer Blog:http://igoogledeveloper.blogspot.com/2009/09/more-things-change-more-...,
> but here are the important details:
> * The legacy API is officially deprecated as of today, September 14th.
> * For three months, the legacy API will continue in its current state.
> * On or around December 14th, any new gadget submissions to the
> iGoogle directory must be using gadgets.*, in order to be accepted,
> but existing gadgets may continue to use the legacy API.
> * On the same date, the remaining inlined gadgets will be disabled.
> * Finally, one year after deprecation, September 14th, 2010, gadgets
> using the legacy API will cease to function on iGoogle, and the
> majority of other Google-owned gadget containers (such as orkut,
> Gmail, and Calendar).
> In summary: all new gadgets should use the gadgets.* API. All existing
> gadgets have one year to migrate to gadgets.*.
> I'll be posting a migration guide and an XML conversion tool in the
> next few weeks to help the transition.
_IG_Analytics should continue to work as before, it's not part of the
core API and wasn't re-namespaced. _IG_Drag was not ported to
gadgets.* because it saw little usage, and the features it offers can
be handled by common third-party libraries (there isn't anything
special in the library required to make it work on iGoogle). If you
want a replacement for the drag features, I'd suggest something like
jQuery UI.
Thanks,
Dan
On Sep 21, 5:41 am, "J.Raghu" <r.s.javalge...@gmail.com> wrote:
> I could not find any equivalent to _IG_Analytics and _IG_Drag in the
> gadgets.* library. Am I correct in understanding that both the
> features are deprecated/no longer supported? If so, why?
> On Sep 15, 3:19 am, "Dan (Google)" <api....@google.com> wrote:
> > Hi everyone,
> > After many faithful years of service, the legacy gadgets API is now
> > officially deprecated. The complete announcement is available on the
> > iGoogle Developer Blog:http://igoogledeveloper.blogspot.com/2009/09/more-things-change-more-...,
> > but here are the important details:
> > * The legacy API is officially deprecated as of today, September 14th.
> > * For three months, the legacy API will continue in its current state.
> > * On or around December 14th, any new gadget submissions to the
> > iGoogle directory must be using gadgets.*, in order to be accepted,
> > but existing gadgets may continue to use the legacy API.
> > * On the same date, the remaining inlined gadgets will be disabled.
> > * Finally, one year after deprecation, September 14th, 2010, gadgets
> > using the legacy API will cease to function on iGoogle, and the
> > majority of other Google-owned gadget containers (such as orkut,
> > Gmail, and Calendar).
> > In summary: all new gadgets should use the gadgets.* API. All existing
> > gadgets have one year to migrate to gadgets.*.
> > I'll be posting a migration guide and an XML conversion tool in the
> > next few weeks to help the transition.
> _IG_Analytics should continue to work as before, it's not part of the
> core API and wasn't re-namespaced. _IG_Drag was not ported to
> gadgets.* because it saw little usage, and the features it offers can
> be handled by common third-party libraries (there isn't anything
> special in the library required to make it work on iGoogle). If you
> want a replacement for the drag features, I'd suggest something like
> jQuery UI.
> Thanks,
> Dan
> On Sep 21, 5:41 am, "J.Raghu" <r.s.javalge...@gmail.com> wrote:
> > I could not find any equivalent to _IG_Analytics and _IG_Drag in the
> > gadgets.* library. Am I correct in understanding that both the
> > features are deprecated/no longer supported? If so, why?
> > > After many faithful years of service, the legacy gadgets API is now
> > > officially deprecated. The complete announcement is available on the
> > > iGoogle Developer Blog:http://igoogledeveloper.blogspot.com/2009/09/more-things-change-more-...,
> > > but here are the important details:
> > > * The legacy API is officially deprecated as of today, September 14th.
> > > * For three months, the legacy API will continue in its current state.
> > > * On or around December 14th, any new gadget submissions to the
> > > iGoogle directory must be using gadgets.*, in order to be accepted,
> > > but existing gadgets may continue to use the legacy API.
> > > * On the same date, the remaining inlined gadgets will be disabled.
> > > * Finally, one year after deprecation, September 14th, 2010, gadgets
> > > using the legacy API will cease to function on iGoogle, and the
> > > majority of other Google-owned gadget containers (such as orkut,
> > > Gmail, and Calendar).
> > > In summary: all new gadgets should use the gadgets.* API. All existing
> > > gadgets have one year to migrate to gadgets.*.
> > > I'll be posting a migration guide and an XML conversion tool in the
> > > next few weeks to help the transition.
> I noticed in my gadgets that _IG_GetImageUrl is not working anymore.
> All images are dead. Is there an alternative in the new API?.
> On 21 sep, 19:37, "Dan (Google)" <api....@google.com> wrote:
> > Hi,
> > _IG_Analytics should continue to work as before, it's not part of the
> > core API and wasn't re-namespaced. _IG_Drag was not ported to
> > gadgets.* because it saw little usage, and the features it offers can
> > be handled by common third-party libraries (there isn't anything
> > special in the library required to make it work on iGoogle). If you
> > want a replacement for the drag features, I'd suggest something like
> > jQuery UI.
> > Thanks,
> > Dan
> > On Sep 21, 5:41 am, "J.Raghu" <r.s.javalge...@gmail.com> wrote:
> > > I could not find any equivalent to _IG_Analytics and _IG_Drag in the
> > > gadgets.* library. Am I correct in understanding that both the
> > > features are deprecated/no longer supported? If so, why?
> > > > After many faithful years of service, the legacy gadgets API is now
> > > > officially deprecated. The complete announcement is available on the
> > > > iGoogle Developer Blog:http://igoogledeveloper.blogspot.com/2009/09/more-things-change-more-...,
> > > > but here are the important details:
> > > > * The legacy API is officially deprecated as of today, September 14th.
> > > > * For three months, the legacy API will continue in its current state.
> > > > * On or around December 14th, any new gadget submissions to the
> > > > iGoogle directory must be using gadgets.*, in order to be accepted,
> > > > but existing gadgets may continue to use the legacy API.
> > > > * On the same date, the remaining inlined gadgets will be disabled.
> > > > * Finally, one year after deprecation, September 14th, 2010, gadgets
> > > > using the legacy API will cease to function on iGoogle, and the
> > > > majority of other Google-owned gadget containers (such as orkut,
> > > > Gmail, and Calendar).
> > > > In summary: all new gadgets should use the gadgets.* API. All existing
> > > > gadgets have one year to migrate to gadgets.*.
> > > > I'll be posting a migration guide and an XML conversion tool in the
> > > > next few weeks to help the transition.
Gadget Ads is one exception to the deprecation, and will continue to
support the legacy API after the one year period has ended. Syndicated
gadgets, however, will follow the same deprecation plan as iGoogle.
Dan
On Sep 23, 2:33 am, alos <hasanhos...@googlemail.com> wrote:
Do you have an example generated URL that isn't working, or a link to
an example gadget that is having an issue? gadgets.io.getProxyUrl
should provide the desired behavior.
Dan
On Sep 22, 11:17 pm, Zwiet <p...@cammap.nl> wrote:
> I tried gadgets.io.getProxyUrl, is not working either in iGoogle.
> Strange thing is; it does work in case I place the gadget on my
> website....
> On Sep 22, 9:57 pm, Zwiet <p...@cammap.nl> wrote:
> > Hi Dan,
> > I noticed in my gadgets that _IG_GetImageUrl is not working anymore.
> > All images are dead. Is there an alternative in the new API?.
> > On 21 sep, 19:37, "Dan (Google)" <api....@google.com> wrote:
> > > Hi,
> > > _IG_Analytics should continue to work as before, it's not part of the
> > > core API and wasn't re-namespaced. _IG_Drag was not ported to
> > > gadgets.* because it saw little usage, and the features it offers can
> > > be handled by common third-party libraries (there isn't anything
> > > special in the library required to make it work on iGoogle). If you
> > > want a replacement for the drag features, I'd suggest something like
> > > jQuery UI.
> > > > I could not find any equivalent to _IG_Analytics and _IG_Drag in the
> > > > gadgets.* library. Am I correct in understanding that both the
> > > > features are deprecated/no longer supported? If so, why?
> > > > > After many faithful years of service, the legacy gadgets API is now
> > > > > officially deprecated. The complete announcement is available on the
> > > > > iGoogle Developer Blog:http://igoogledeveloper.blogspot.com/2009/09/more-things-change-more-...,
> > > > > but here are the important details:
> > > > > * The legacy API is officially deprecated as of today, September 14th.
> > > > > * For three months, the legacy API will continue in its current state.
> > > > > * On or around December 14th, any new gadget submissions to the
> > > > > iGoogle directory must be using gadgets.*, in order to be accepted,
> > > > > but existing gadgets may continue to use the legacy API.
> > > > > * On the same date, the remaining inlined gadgets will be disabled.
> > > > > * Finally, one year after deprecation, September 14th, 2010, gadgets
> > > > > using the legacy API will cease to function on iGoogle, and the
> > > > > majority of other Google-owned gadget containers (such as orkut,
> > > > > Gmail, and Calendar).
> > > > > In summary: all new gadgets should use the gadgets.* API. All existing
> > > > > gadgets have one year to migrate to gadgets.*.
> > > > > I'll be posting a migration guide and an XML conversion tool in the
> > > > > next few weeks to help the transition.
I don't find method how to get parameters from url (for example if I
want to get width or height). The old functions is named _args(), but
now doesnt work _args()['w']
2) Does it exist equal to function: _IG_Callback(response,id)
Now I am using this solution: (if I want to call some function (named:
response) with parameter (named: id) after I get all data (from url)):
gadgets.io.makeRequest(url, _IG_Callback(response,id), params);
On Oct 2, 10:27 am, codeas <code...@gmail.com> wrote:
> I don't find method how to get parameters from url (for example if I
> want to get width or height). The old functions is named _args(), but
> now doesnt work _args()['w']
You should tokenize the window.location.search string.
For the URL http://www.news.com/?param1=foo¶m2=bar window.location.search will be the string "?param1=foo¶m2=bar"
> 2) Does it exist equal to function: _IG_Callback(response,id)
> Now I am using this solution: (if I want to call some function (named:
> response) with parameter (named: id) after I get all data (from url)):
> gadgets.io.makeRequest(url, _IG_Callback(response,id), params);
It's time to use anonymous function expressions:
gadgets.io.makeRequest(url, function() {response(id)}, params);
> After many faithful years of service, the legacy gadgets API is now
> officially deprecated. The complete announcement is available on the
> iGoogle Developer Blog:http://igoogledeveloper.blogspot.com/2009/09/more-things-change-more-...,
> but here are the important details:
> * The legacy API is officially deprecated as of today, September 14th.
> * For three months, the legacy API will continue in its current state.
> * On or around December 14th, any new gadget submissions to the
> iGoogle directory must be using gadgets.*, in order to be accepted,
> but existing gadgets may continue to use the legacy API.
> * On the same date, the remaining inlined gadgets will be disabled.
> * Finally, one year after deprecation, September 14th, 2010, gadgets
> using the legacy API will cease to function on iGoogle, and the
> majority of other Google-owned gadget containers (such as orkut,
> Gmail, and Calendar).
> In summary: all new gadgets should use the gadgets.* API. All existing
> gadgets have one year to migrate to gadgets.*.
> I'll be posting a migration guide and an XML conversion tool in the
> next few weeks to help the transition.
On Sep 14, 10:19 pm, "Dan (Google)" <api....@google.com> wrote:
> * Finally, one year after deprecation, September 14th, 2010, gadgets
> using the legacy API will cease to function on iGoogle, and the
> majority of other Google-owned gadget containers (such as orkut,
> Gmail, and Calendar).
Just occurred to me, what about mapplets? As I'm sure you know, they
use a superset of the legacy Gadgets API. Are there plans to migrate
them to gadgets.*, or will they remain as another exception? It's
important to know for those of us who develop for both platforms; I
have a number of gadget/mapplets running from a single XML file now.
> On Sep 14, 10:19 pm, "Dan (Google)" <api....@google.com> wrote:
> > * Finally, one year after deprecation, September 14th, 2010, gadgets
> > using the legacy API will cease to function on iGoogle, and the
> > majority of other Google-owned gadget containers (such as orkut,
> > Gmail, and Calendar).
> Just occurred to me, what about mapplets? As I'm sure you know, they
> use a superset of the legacy Gadgets API. Are there plans to migrate
> them to gadgets.*, or will they remain as another exception? It's
> important to know for those of us who develop for both platforms; I
> have a number of gadget/mapplets running from a single XML file now.
> After many faithful years of service, the legacy gadgets API is now
> officially deprecated. The complete announcement is available on the
> iGoogle Developer Blog:http://igoogledeveloper.blogspot.com/2009/09/more-things-change-more-...,
> but here are the important details:
> * The legacy API is officially deprecated as of today, September 14th.
> * For three months, the legacy API will continue in its current state.
> * On or around December 14th, any new gadget submissions to the
> iGoogle directory must be using gadgets.*, in order to be accepted,
> but existing gadgets may continue to use the legacy API.
> * On the same date, the remaining inlined gadgets will be disabled.
> * Finally, one year after deprecation, September 14th, 2010, gadgets
> using the legacy API will cease to function on iGoogle, and the
> majority of other Google-owned gadget containers (such as orkut,
> Gmail, and Calendar).
> In summary: all new gadgets should use the gadgets.* API. All existing
> gadgets have one year to migrate to gadgets.*.
> I'll be posting a migration guide and an XML conversion tool in the
> next few weeks to help the transition.
|
