No one has been able to write an inlined gadget for over a year. Please explain to me how the API has been modified.
On Aug 4, 1:21 pm, Matt Foster <[email protected]> wrote: > > With that said, I can tell you that -all- inlined gadgets will be removed > ... > > That's incorrect. The API as it concerns inlined gadgets has not been > > changing. > > Rick James?? > > http://groups.google.com/group/Google-Gadgets-API/browse_thread/threa... > > Quote from the linked thread... > "The plan is to continue supporting legacy gadgets, but I don't have > the specific timeline available. I'm working on this as we speak and > will hopefully have a complete timeline available within a month or > two. Part of not announcing gadgets.* is that I didn't want everyone > to panic about the legacy API until the plan was finalized. So, don't > panic. :) " > > I'd say we're pretty panicked at this point... > > How's that time line coming? > Step One, botch everyones legacy gadget. > Step Two, ??? > Step Three, Profit!! > > On Aug 4, 5: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 -~----------~----~----~----~------~----~------~--~---
