At the OpenSocial State of the Union on May 12th, Andrew Davis and Ryan Baxter of IBM announced a sandbox environment for app developers to test their apps against the OpenSocial 2.0 specification.
“We’ve built a sample collaboration application that contains an activity stream, inbox, and an area to render arbitrary gadgets. The sandbox is based on a daily build of Shindig 3.0 which’s the reference implementation for OpenSocial 2.0. Gadget developers who’re interested in building apps for OpenSocial 2.0 containers can go to the sandbox and add any gadget they please to test it out,’ informed Baxter and Davis.
“The data in the inbox and activity stream is static and will remain that way but they plan to add functionality so developers can add their own activities and emails for a given session. This’ll be key for testing OpenSocial gadgets that use embedded experiences. There’re also several pieces of the OpenSocial specification which’ve not been implemented in the container yet. For e.g., gadget preferences, pubsub2, and some gadget to container APIs like gadget.window.setTitle,” stated the duo.
“Over the coming weeks and months we’ll work implementing the missing pieces from the specification so the sandbox is more complete. We’ve also reached out to Shindig community so a daily build of Shindig is automatically deployed to the server. This’ll allow app developers to develop gadgets against cutting edge OpenSocial proposals. At some point the app will become part of Shindig, allowing the community to continue to enhance the sandbox as the specification progresses,” added Davis and Baxter.
“We plan to continue to work on the sandbox to refine it and make it more complete. The social data in the collaboration application is not very robust, and we’d like to include a more complete set so developers can better test their apps.”
[Source: Opensocial blog]