Gadgets and Dashboards 2.0
Gadgets and Dashboards 1.0
At heart, Atlassian gadgets are Google gadgets. Atlassian gadgets use the new Google
gadgets.* API defined by the OpenSocial specification. In addition, you will probably want to use some of the Atlassian extensions to the gadget specification. You will also want to package your gadget as an Atlassian plugin, along with plugin modules that allow your gadget to interact with the Atlassian applications such as JIRA and Confluence.
A gadget is essentially an XML file containing the gadget specification. You will use recognised XML elements to define the following:
As the gadget developer, you create the static XML file and make it available on a server. The dashboard or other container will pull the XML file from the server or plugin where it resides, and render it. The container may, for example, display the gadget inside an iframe on a dashboard. Or the container may display the gadget on a web page via a wiki macro.
Here is an overview of how gadgets, containers, plugins and applications interact with each other:
If you have never written a gadget before, you can start by writing a simple Google gadget:
Now move on to write an Atlassian Gadget.