The following topics cover best practices for developing and designing highly functional widgets with optimal performance.
In this document, the term widget
collectively describes both iWidgets and OpenSocial gadgets. An iWidget is built on the IBM iWidget specification
, and an OpenSocial gadget is built upon and conforms to the OpenSocial specification
General best practicesPrevious topic: Sample gadgets sbt
Next topic: OAuth guide for developers
As you design and code widgets, use the following general best practices as a guideline:
Creating portable widgets
Although component models for creating widgets typically support portability across container implementations, sometimes widgets lose their ability to be portable for various reasons. This topic provides tips for making sure that widgets, including both iWidgets and OpenSocial gadgets, remain portable across container implementations.
Best practices for eventing
Use the following guidelines for eventing:
Packaging for performance and multiple environments sbt
Identifying performance issues for OpenSocial gadgets
This topic identifies performance issues for gadgets.
Rendering OpenSocial gadgets inline sbt
A new Apache Shindig feature is now available that allows gadgets to render inline while keeping the impact to the Shindig core as small as possible.
Implementing namespaces sbt
Creating embedded experiences sbt
From a user's perspective, an embedded experience is a way of interacting with events, notifications, and business processes dynamically in context directly from an inbox, social home page, and other containers without having to log in to and switch to another application or service.
Problemsolving your CSS styles sbt
This topic explains some problems you might experience when using CSS style to control how your widgets display when rendered in a browser. Fortunately, many solutions are available to help solve these problems.