Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Not all gadgets need the full weight of the current gadget spec.  This proposal creates a simplified format that may be used.

== Example ==
<pre style="font-size:12pt;">
<?xml version='1.0' encoding='utf-8'?>
<Module title="Simple Gadget">
  <Data>
      <os:ViewerRequest key='vwr' />
  </Data>
  <Templates>
    <Template tag="my:foo">
    <div>
    <img src="$

Unknown macro: {My.person.thumbnailUrl}

" /> <br/>
    (Picture of $

Unknown macro: {My.person.displayName}

)
    </div>
    </Template>  
  </Templates>

  <Content type='osml' >
  <h1>Hello, $

Unknown macro: {vwr.displayName}

</h1>
  <my:foo person="$

Unknown macro: {vwr}

" />
 </Content>
</Module>
</pre>

== ModulePrefs as optional ==

The ModulePrefs section may be optional in a gadget.  The Module node may contain a @title attribute for the gadget.  When ModulePrefs is not specified the container may infer what features are required.

== Data section ==

A new Data element may be used to specify data pipeline tags. This is a direct child of the Module element. All data pipeline tags are globally registered.  Data may be scoped to a view(s) by specifying the view name(s) in a @scope attribute of the data pipeline tag.

== Templates section ==

A new Templates element may be used to specify data pipeline tags. This is a direct child of the Module element. All custom tag templates are globally registered.  Templates may be scoped to a view(s) by specifying the view name(s) in a @scope attribute of the Template tag.  This utilizes the syntax defined for template libraries. http://opensocial-resources.googlecode.com/svn/spec/1.0/OpenSocial-Templating.xml#rfc.section.15

  • No labels