There is no set date, but Dan from Google said that “soon”, inline gadgets will no longer be supported in the gadget API. From the announcement:
“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.”
New inline gadgets will not be included into the Google gadgets directory.
Existing inline gadgets will remain in the directory and will continue to function.
If you are developing an inline gadget, you must pretty much submit it right now, and hope that it gets enough page views to warrant inclusion in the directory before the cutoff takes place. For anyone in this scenario I would strongly suggest that you submit your gadget this week to all the places suggested in my Google gadget submit guide. If there is anyone who has put alot of work in their gadget and is worried it won’t get into the directory in time, contact me and I might be able to highlight it on this blog which normally helps a gadget get enough pageviews to help it get in.
What are inline gadgets?
Inline gadgets are Google gadgets which have the ability to change the iGoogle page which it is on. In the Google gadget documentation inline gadgets are descibed as…
“You can use the
html-inline content type to write a gadget that modifies the parent page. Such gadgets are called “inlined gadgets.By default, gadget content is wrapped in an iframe. An iframe is effectively a page running within the parent page. It has no knowledge of the parent page and no ability to interact with it. This helps protect users from malicious gadgets that might try, for example, to steal or modify cookies. However, iframes impose certain limitations. They don’t allow gadgets to interact with each other and other components on the page.
To get around these limitations you can use inlining, in which the gadget becomes part of the iGoogle page HTML. To see this in action, add an inlined gadget (such as the developer gadget) to your iGoogle page and view the HTML source. You can see the entire gadget spec in the HTML. Compare this to the iframe gadgets on the same page, which are simply referenced in the HTML source through their gadget spec URLs.
The benefit of inlining is that you can modify the iGoogle page DOM. For example, see googlelogo.xml.
They sound cool, why is Google depreciating inline gadgets?
The reason cited for this change was possible security issues.
I also think there are some basic problems with the current API that tie into Open Social and Google gadget PubSub. It is my belief that inline gadgets (or some new version of them) will be reintroduced to the gadget API at a later date, however if you are putting time into developing inline gadgets, you are kinda screwed for the moment.
The most widely known type of inline gadgets would be those which let you choose a theme for your iGoogle page.
On the Google gadgets API group, Dan answered some questions and concerns.
It is nice that they have given the news in advance, but could have announced this change much louder so I hope anyone with the ability the “spread the word” will let others know that these types of Google gadgets will soon be gone. It would suck for someone to be working on this just to find out later that their gadget won’t function and isn’t allowed in the directory.
{ 1 comment… read it below or add one }
hi..
here u download movie,songs,games..