On Tue, Jan 29, 2008 at 5:39 PM, Reinoud Elhorst <[EMAIL PROTECTED]> wrote:
> Hi all, > > In the process of trying to make Hyves an OpenSocial container, I tried my > hand tonight at making the Hello World OpenSocial Gadget example work in > our > site, through Shindig. I ran into some small issues, which I rather > "hacked" > my way around. Now I understand that Shindig is work in progress, and > don't > blame anyone for this not being s finished product. Au contraire, I was > pleasantly surprised by how far I've come in just one night: thumbs up for > the readability and documentation of most of the code, and obviously the > lavish explanations I've been able to enjoy on this list! > > I hope someone can give some feedback on the following issues: > - I included the js and css files from the /javascript/container > directory > into the parent page. When copying the code from the sample files, there > are > some options I'm missing in the gadgets.js file. It seems to me that the > result of gadgets.container.createGadget, should have methods to set the > "nocache=1" and the security token (or just generally, everything behind > the > #). Am I thinking in the right direction here, or is this being handled in > some other way? You can see what I had to do in the sample container for this: http://svn.apache.org/repos/asf/incubator/shindig/trunk/javascript/samplecontainer/samplecontainer.html In line 71 - 93 I basically make my own overriding gadget class and change the getIframeUrl method to do what I want it to do. This doesn't involve any gross hacking, but we could make this a little cleaner though by giving a more obvious hook. > > > - The opensocial part consists of a lot of general javascript, and some > container-specific javascript. How does shindig know where to get this > container specific javascript? Would this done in a call to the result of > gadgets.container.createGadget as well? Right now what you need to do is drop in some code to the shindig features directory. More specifically, shindig currently does not response to the opensocial requires tags that it should, like "opensocial-0.7". You would need to create this directory in your copy of shindig, create a features.xmlfile which included your javascript class which extends the opensocial container.js file, and then shindig would know what to do. (I can go into more detail here if you haven't already done this) This will hopefully get easier in shindig over time as it supports more and more of opensocial. The first goal is to get a real opensocial container running which gets data from the server (vs the mock data in the sample container). I'm not sure if we can immediately add a js api for setting the opensocial container class (in the same way you set up the gadget js code) but we can probably work on it. I hope that helps! Nice work on getting your server up. - Cassie > > - For the ifpc to work correctly, the ifpc_relay.html file has to be > present > on the same domain as the parent page is on (so, basically, your SNS > domain). Is there any documentation yet on what the security implications > of > this are? > > > > Presently, I'm at the point where pretty much everything works except for > the API calls back to the site; I wanted to make sure I was going in the > right direction with regard to the exchange of the security token. > > Thanks, > > Reinoud Elhorst > Hyves Senior Developer >
