Requirements For OpenSocial Sandbox 2.0
This page should be used to gather requirements for the next version of the OpenSocial container.
- Gadget Functionality
- Core gadget functionality must be implemented
- Gadget chrome with the ability to add and close arbitrary gadgets
- Switch views both from the container and the gadget itself
- Preferences support, at least within the current session, preferably across sessions
- Support adjust height & width
- +1 would be the ability to dynamically resize the gadget so devs can test different real-estates
- Support for making remote requests via makeRequest & osapi.http
- Advanced features
- Container Services
- Actions
- Selection
- Open Views
- OpenSearch
- Embedded Experiences
- Activity stream is a must, and it must be the real activity stream from the container, so in theory if I get the activity stream via the opensocial APIs it is the same activity stream
- Email - is this necessary? Â For gadget devs you only really need to build the EE gadget once and it should work in both email and the activity stream. Â We cannot support real emails coming into the sandbox, could we possibly derive and email experience from the activity stream?
- OAuth
- I want to be able to configure my own OAuth providers for my own account and store them securely
- Hosting and Editing of my gadget XML?
- Links to resources on how to add the features supported in the container to your gadget should be easy to access from the sandbox
- Container Services
- Core gadget functionality must be implemented
- Developer Requirements
- Must be open sourced and in the OpenSocial foundations source control
- Links to resources on how to add the features supported in the container to your gadget should be easy to access from the sandbox
- The sandbox should be an upstream project and built upon Shindig or Rave
- Should have a dashboard mode as well as a "social app mode"