All
All
Projects
Snippets
Go
Explore
Home
About
Get Involved
IP
Legal
Interact With Us
Blog
Webinars
Discord
Twitter
YouTube
Facebook
OpenNTF GitHub
OpenNTF Connections GitHub
IBM Connections Downloads
DominoHelp (external)
Explore
Home
About
Get Involved
IP
Legal
Interact With Us
Blog
Webinars
Resources
Discord
Twitter
YouTube
Facebook
OpenNTF GitHub
OpenNTF Connections GitHub
IBM Connections Downloads
DominoHelp (external)
Resources
Discord
Twitter
YouTube
Facebook
OpenNTF GitHub
OpenNTF Connections GitHub
IBM Connections Downloads
DominoHelp (external)
Projects
Snippets
Collaboration Today
Sign In
Username
Password
Forgotten your login credentials?
Login
Register
All
All
Projects
Snippets
Go
New Release of Social Enabler for XPages in the Embedded Experience
Posted by
Niklas Heidloff
on
April 14, 2011
I've uploaded a
new release
of
Social Enabler
.
I
blogged
earlier about how to display XPages in the Embedded Experience in the IBM Social Business Toolkit. I rendered the XPages inline and passed the document UNIDs to be rendered in the Embedded Experience as URL parameters to the gadget and then forwarded them to the XPages. However this can cause issues since some containers might cache the gadget definition. So rather than URL parameters contextual data should be used as
documented
in the tutorial.
This results in the following static gadget.xml which can be used generically for all XPages. "__MODULE_ID__" is replaced by the container at runtime with a unique value so that you can run different instances of the gadgets at the same time. At the bottom of the screenshot you can see how the XPages are embedded via iFrames.
The
API
has been extended so that you can pass in the gadget URL as well as the XPage URL. The XPage will then be rendered within an
iFrame
.
Also my colleague Ryan Baxter
blogged
yesterday about some of the IBM proposals for how to extend OpenSocial in 2.0. This includes a proposal for the
Embedded Experience
.
Please enable JavaScript to view the
comments powered by Disqus.
comments powered by
Disqus