Uploaded image for project: 'Shindig'
  1. Shindig
  2. SHINDIG-1402

Rendering Open Social gadgets inline (without an IFrame)

    Details

    • Type: New Feature
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.0.0
    • Fix Version/s: 2.5.3
    • Component/s: Java, Javascript , PHP, Website
    • Labels:
      None
    • Environment:
      Should be applicable to any platform Shindig will run

      Description

      Kudos to the team who have come up with such an excellent container and the success we have in many of the open social networking platforms. OpenSocial gadgets IFrame model seems to work great on the web that will let you sandbox all the interactions with the back-end. This is especially very cool to isolate when you don't have control on each of the gadget sources.

      Background:
      Moving to the enterprise space brings in extra challenges. One such request we are seeing is rendering open social gadgets inline. This seems an important feature for many situations where gadgets are trusted and scalability is a concern. Isolating gadgets with each gadget loading its own resources may not be required. I am sure there may be some tricks to workaround. But from clean programming model perspective, we would like to propose this feature.

      Here are some of the concerns expressed for which we were attempting to prototype rendering gadgets inline:

      • Load common JavaScript libraries globally
      • Load Gadget features globally
      • Address some of the memory leak issues with iframes
      • Reduce the download size of the page
      • Reduce number of requests to server
      • Avoid iframe reloading when the gadgets are moved on the page

      Feature Request:
      Support Inline container in addition to IFrame container. There could be an API to render gadgets inline vs iframe. There are more observations in terms of namespace conflicts, duplicate JavaScript, and CSS loading, duplicate feature loading etc. We have a working patch on 2.0.0, but before we go too far with the implementation, I wanted get the thoughts from the community and see what you think about adding this feature to Shindig.

      Thanks in advance for the feedback.

        Attachments

        1. inline.patch
          103 kB
          Michael Beaver
        2. inline-initial-port.patch
          522 kB
          Michael Beaver
        3. inline_feature_patch_20101103.patch
          24 kB
          Kai Feng Zhang
        4. inlineFeature.txt
          52 kB
          Andy Smith
        5. patch_20100921.patch
          231 kB
          Kris Vishwanathan
        6. inline_20100824.patch
          491 kB
          Kris Vishwanathan

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              v2kris Kris Vishwanathan
            • Votes:
              5 Vote for this issue
              Watchers:
              16 Start watching this issue

              Dates

              • Created:
                Updated:

                Time Tracking

                Estimated:
                Original Estimate - 672h
                672h
                Remaining:
                Remaining Estimate - 672h
                672h
                Logged:
                Time Spent - Not Specified
                Not Specified