Hi, A few points: 1. Labs APIs are not officially supported, but that does not mean that unofficial support will not meet (or try to meet) the same standard as the non-Labs APIs. 2. I have tried to address any issues that were reported with regards to the legacy API. 3. The legacy API has not yet been officially deprecated. 4. The legacy API will be deprecated, and while I do not yet have a final timeline on the deprecation, we are considering between 1 to 3 years of support (ie. if things break, we fix them). As further context, we are strongly leaning towards 3 years, but until it's final I'm not going to say that's how long it will be. For reference, 3 years is the length of time non-Labs APIs must be supported after announcing deprecation. 5. Migration from the legacy API to gadgets.* is, in many cases, as simple as find and replace. There is no loss of functionality when moving from _IG_* to gadgets.*, as the legacy API is currently running (through a wrapper) directly on top of gadgets.*. 6. PubSub was always an experimental feature, and only worked sporadically at best. 7. The drag and grid libraries, as far as I know, don't work with the new iGoogle renderer. However, I'm also not aware of gadgets that use them, as there are numerous other better implementations in 3rd-party JS libraries. 8. iGoogle's conduct with regards to inlined gadgets has alienated a number of iGoogle's oldest developers, I'm aware of this. However, I'm surprised that these developers do not understand the necessity of disabling inlined gadgets. I'm also surprised that the introductions of gadgets.* in production and OpenSocial in the sandbox are met with fear and not excitement regarding the new opportunities. Many have made their judgement on how iGoogle handles APIs from a single data point (inlined gadgets), despite the fact that the majority of other iGoogle technologies have remained supported for many, many years, while simultaneously being supplemented with new ones.
Dan On Aug 4, 2:02 am, String <[email protected]> wrote: > On Aug 4, 3:03 am, "Dan (Google)" <[email protected]> wrote: > > > That's incorrect. The API as it concerns inlined gadgets has not been > > changing. It has been consistently frozen (and deprecated) for nearly > > two years. > > The elephant in the room is that the Legacy API, used by (guessing) 90+ > % of the gadgets out there, is also deprecated - has been for over a > year now - and unsupported (because it's been reclassified as "Labs"). > Given the recent troubles as iGoogle cut over to the gadgets.* API, > there's understandably some concern that the Legacy API will go the > way of inlining. There are some clear parallels. > > > The suggestion to move to supported APIs (which, with the > > exception of inlined gadgets and the rarely-used drag and grid > > libraries) > > Has support been removed for drag and grid? When was that announced? > > And don't forget pubsub, support for which was apparently dropped at > some unspecified time in the past. There was no notice AFAIK, it only > came to light because there's been a recent spate of interest in inter- > gadget commuinication on this forum. > > Dan, I again don't want to make this personal, but it's just not a > good sign that Google's conduct with regard to the Gadgets APIs has > alienated many of its most dedicated developers - including, I think, > every one that you designated as a "Guru". That tells me there's a > serious issue, and I'd like to think it would say the same to you. > > String --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "iGoogle Developer Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en -~----------~----~----~----~------~----~------~--~---
