[Google-Gadgets-API] Re: gadgets.util only in sandbox? - Dan (Google Employee) - com.googlegroups.google-gadgets-api

5 messages in com.googlegroups.google-gadgets-api[Google-Gadgets-API] Re: gadgets.util...

From	Sent On	Attachments
Tobi555	30 May 2008 10:52
Dan (Google Employee)	30 May 2008 11:49
Tobi555	30 May 2008 12:11
leonel abarca	30 May 2008 12:17
Dan (Google Employee)	02 Jun 2008 17:32

Subject:	[Google-Gadgets-API] Re: gadgets.util only in sandbox?
From:	Dan (Google Employee) (api....@google.com)
Date:	05/30/2008 11:49:39 AM
List:	com.googlegroups.google-gadgets-api

Hi,

To use gadgets.* and opensocial.* calls in your gadgets, you'll either need to use them within the sandbox or wait until they are available in the production version of iGoogle (which should happen this summer).

Documentation on the legacy API is available here: http://code.google.com/apis/gadgets/docs/legacy/dev_guide.html

Best, Dan

On May 30, 10:53 am, Tobi555 <goo...@samedia.eu> wrote:

Hi, I'm trying to write an app for iGoogle. Quite confusing. It is recommended to use the openSocial API which I did and which works fine in the sandbox. I managed to upload it with the gadget editor as well. But sending its generated url to anybody does not work, because outside the sandbox you will get an error saying "gadgets.util has no properties". After two hours I finally found this sentence in the Gadget API Reference: "This API is not yet supported by the production instance of iGoogle, though it is available in the iGoogle sandbox. If you'd like to write a gadget for iGoogle, see the gadgets API Reference."

OK, I went there but the Javascript API link on that page links back to the above. Catch 22.... On the net I found people using _IG_FetchXmlContent but this apparently is not documented anymore. All related links don't work anymore that is. Is _IG_FetchXmlContent deprecated?

Is there anything I didn't understand?

I mean, gadgets SHOULD work using the link generated by the gadget editor upon pressing PUBLISH or SAVE, right?

Or do I simply have to wait until the new opensocial API is available for the public?