Uploaded image for project: 'Wookie'
  1. Wookie
  2. WOOKIE-429

Add support for embedded experiences similar to OpenSocial


    • Type: New Feature
    • Status: Reviewable
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.0.0
    • Fix Version/s: 2.0.0
    • Component/s: None
    • Labels:


      OpenSocial has a concept of an "embedded experience", which is basically being able to declare in an activity stream or some other context that a widget should be used to interact with an item of content. The widget is launched with a context parameter, the value of which can be accessed from within the widget's JavaScript.

      (In the IMS LTI spec there is also the idea of a "resourceLink" which is typically the identity of a resource that the widget interacts with, such as a video, image or document. This is very similar to EE)

      In Wookie, we tend to handle these scenarios already, using a method of the connector setting a preference at the same time it requests a widget; however, as preferences are widget-specific there isn't a general method used to access this information.

      One option is that we could create a "magic" read-only preference to support these scenarios; so for example "context" would be a preference that could only be set from the container via the REST API. (We could make these appear in the Widget object separately from preferences e.g. widget.context rather than widget.preferences.context.)

      If that feels like too much of a hack, another option is to create a new SPI for "Context" or "IndividualContext" (as opposed to SharedContext, which is for collaborative widgets) and corresponding AJAX support.




            • Assignee:
              scottbw Scott Wilson
            • Votes:
              0 Vote for this issue
              1 Start watching this issue


              • Created: