Thanks! So what are the recommended better ways to implement the functionality that "output=js" used to support?
-Dave -----Original Message----- From: Michael Hermanto [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 25, 2008 4:55 PM To: [email protected] Subject: Re: What happened to "output=js"? > When inserting a gadget in a container not hosted on the same domain as > Shindig, it's convenient to be able to dynamically generate the JS to > create the gadget iframe. > > > > I noticed that the non-sandbox gmodules.com supports an "output=js" > request parameter that does just that, but Shindig does not support such > a parameter. > > > > What's the history of the "output=js" parameter, why doesn't Shindig > support it, and what's the recommended alternative? > You're correct to say that "output=js" is not supported by Shindig. It is used by www.gmodules.com to render open-syndication gadgets (or gadgets for your webpage, here <http://www.google.com/ig/directory?synd=open>). I understood that there are better ways to support "output=js", so it probably should not continue in Shindig.
