Hi Dan,

can you say something about the support for POST as
gadgets.io.RequestParameters.METHOD?
Currently, POST is not supported. Will this change in the forseeable
future?

In case I'm off topic, please guide me to a proper destination.

jofeux


On Aug 4, 4:03 am, "Dan (Google)" <[email protected]> wrote:
> Hi,
>
> 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 suggestion to move to supported APIs (which, with the
> exception of inlined gadgets and the rarely-used drag and grid
> libraries) encompasses APIs which have been available since inception
> of the platform. In addition to those APIs, iGoogle has added support
> for a newer version of the API (gadgets.*).
>
> My message above was not a release notification. It was an apology to
> Matt for not personally notifying him that his gadget would be
> disabled. That was not because there hasn't been fair warning that the
> API was no longer supported, but rather because Matt has provided
> valuable contribution to the community and as a gesture it would have
> been appropriate. I then explicitly spelled out that all remaining
> inlined gadgets would be disabled because my prior warnings have been
> ignored.
>
> API deprecation can be painful, and I empathize. However, it's also
> necessary to keep platforms moving forward, as is the case here.
>
> Dan
>
> On Aug 3, 12:14 pm, Matt Foster <[email protected]> wrote:
>
>
>
> > > but let this
> > > serve as additional notice to any remaining inlined gadget developers
> > > to move to supported APIs.
>
> > in other words...  bust ass to keep up with a constantly changing API
> > where release notifications come out as the 11th post in a rant
> > thread, real smooth Dan, reeeeal smoooooth...
>
> > --
>
> >http://positionabsolute.net
>
> > On Jul 20, 7:34 pm, "Dan (Google)" <[email protected]> wrote:
>
> > > Hi Matt,
>
> > > I apologize as I missed that your gadget was being removed as part of
> > > the inlined deprecation. I would have sent you a note in advance if I
> > > had known.
>
> > > With that said, I can tell you that -all- inlined gadgets will be
> > > removed, both Google-provided and 3rd-party inlined modules, and the
> > > iGoogle team is currently working to migrate several, popular, Google-
> > > provided inlined gadgets to type="html". I don't have a specific
> > > timeline on when all inlined modules will be removed, but let this
> > > serve as additional notice to any remaining inlined gadget developers
> > > to move to supported APIs.
>
> > > Thanks,
> > > Dan
>
> > > On Jul 16, 10:31 am, "Matt (Guru)" <[email protected]> wrote:
>
> > > > My iGoogle page suddenly got ugly!
> > > > My RSS gadget is now displaying "Sorry, this gadget uses the inlining
> > > > feature, which is no longer 
> > > > supported."http://www.google.com/ig/directory?url=www.javascripttoolbox.com%2Fga...
>
> > > > Did another round of gadget-killings go through? Did mine get the axe?
> > > > Hey, thanks for the warning, Google!
>
> > > > My iGoogle page is once again ugly and unusable. Add to that the fact
> > > > that I'm getting emails from users of this gadget and another. This is
> > > > environment is way too difficult to support and use (especially for
> > > > free). I quit.
>
> > > > Matt Kruse

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to