Difference between revisions of "widget-examples"

From Microformats Wiki
Jump to navigation Jump to search
 
Line 3: Line 3:
 
* Uses an XML Manifest file to specify data about the "widget" (width, height, thumbnail image, title and version).
 
* Uses an XML Manifest file to specify data about the "widget" (width, height, thumbnail image, title and version).
 
* No requirements for markup around widgets.
 
* No requirements for markup around widgets.
 +
 +
=== Dashboard Example (plist) ===
 +
 +
<pre><code>&lt;?xml version=&#34;1.0&#34; encoding=&#34;UTF-8&#34;?&gt;
 +
&lt;!DOCTYPE plist PUBLIC &#34;-//Apple Computer//DTD PLIST 1.0//EN&#34; &#34;http://www.apple.com/DTDs/PropertyList-1.0.dtd&#34;&gt;
 +
&lt;plist version=&#34;1.0&#34;&gt;
 +
&lt;dict&gt;
 +
        &lt;key&gt;AllowNetworkAccess&lt;/key&gt;
 +
        &lt;true/&gt;
 +
        &lt;key&gt;CFBundleDisplayName&lt;/key&gt;
 +
        &lt;string&gt;AIM Fighter&lt;/string&gt;
 +
        &lt;key&gt;CFBundleIdentifier&lt;/key&gt;
 +
        &lt;string&gt;com.aimfight.widget&lt;/string&gt;
 +
        &lt;key&gt;CFBundleName&lt;/key&gt;
 +
        &lt;string&gt;AOL Fighter&lt;/string&gt;
 +
        &lt;key&gt;CFBundleShortVersionString&lt;/key&gt;
 +
        &lt;string&gt;2.0&lt;/string&gt;
 +
        &lt;key&gt;CFBundleVersion&lt;/key&gt;
 +
        &lt;string&gt;2.0&lt;/string&gt;
 +
        &lt;key&gt;CloseBoxInsetX&lt;/key&gt;
 +
        &lt;integer&gt;5&lt;/integer&gt;
 +
        &lt;key&gt;CloseBoxInsetY&lt;/key&gt;
 +
        &lt;integer&gt;5&lt;/integer&gt;
 +
        &lt;key&gt;MainHTML&lt;/key&gt;
 +
        &lt;string&gt;fight.html&lt;/string&gt;
 +
&lt;/dict&gt;
 +
&lt;/plist&gt;</code></pre>
  
 
== AOL's Channel Content Modules - [[http://sports.aol.com|AOL Sports example]] ==
 
== AOL's Channel Content Modules - [[http://sports.aol.com|AOL Sports example]] ==

Revision as of 15:56, 27 September 2005

Apple's Dashboard

  • Uses an XML Manifest file to specify data about the "widget" (width, height, thumbnail image, title and version).
  • No requirements for markup around widgets.

Dashboard Example (plist)

<code><?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
        <key>AllowNetworkAccess</key>
        <true/>
        <key>CFBundleDisplayName</key>
        <string>AIM Fighter</string>
        <key>CFBundleIdentifier</key>
        <string>com.aimfight.widget</string>
        <key>CFBundleName</key>
        <string>AOL Fighter</string>
        <key>CFBundleShortVersionString</key>
        <string>2.0</string>
        <key>CFBundleVersion</key>
        <string>2.0</string>
        <key>CloseBoxInsetX</key>
        <integer>5</integer>
        <key>CloseBoxInsetY</key>
        <integer>5</integer>
        <key>MainHTML</key>
        <string>fight.html</string>
</dict>
</plist></code>

AOL's Channel Content Modules - [Sports example]

  • Each module (widget) has a markup envelope and some required elements that make it a module and allow for consistent styles across products.

Konfabulator

  • (need someone else to fill this in, have never built one or taken them apart)

WSRP

  • SOAP envelopes to transport modules, but there is no specific formatting required for the actual content of the "portlet" (module or widget).