<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://dev.netvibes.com/doc/lib/exe/css.php?s=feed" type="text/css"?>
<rss version="2.0">
    <channel>
        <title>doc uwa:howto</title>
        <description></description>
        <link>http://dev.netvibes.com/doc/</link>
        <lastBuildDate>Fri, 30 Oct 2009 15:50:33 +0100</lastBuildDate>
        <generator>FeedCreator 1.7.2-ppt DokuWiki</generator>
        <image>
            <url>http://dev.netvibes.com/doc/lib/images/favicon.ico</url>
            <title>doc</title>
            <link>http://dev.netvibes.com/doc/</link>
        </image>
        <item>
            <title>How to assign a JavaScript behavior to a tag?</title>
            <link>http://dev.netvibes.com/doc/uwa/howto/assign_javascript_behaviors?rev=1225384617</link>
            <description>It is tempting to use event handlers in the “old” way - that is, by putting the code directly on the tag's handler, like so:


&lt;textarea &lt;BEGIN GeSHi&gt;onfocus=&quot;pieceOfCode(this);&quot;&lt;END  GeSHi&gt; &gt;
  Default text
&lt;/textarea&gt;


It is no longer possible to do so in the UWA environment: the pieceOfCode method above would be set globally, like document.pieceOfCode(), which is not allowed in UWA (the document and window objects are not recommended for portability reasons).</description>
        <category>uwa:howto</category>
            <pubDate>Thu, 30 Oct 2008 17:36:57 +0100</pubDate>
        </item>
        <item>
            <title>How to use the internal audio player?</title>
            <link>http://dev.netvibes.com/doc/uwa/howto/audio_player?rev=1225387979</link>
            <description>How to use the internal audio player?


By default, when Netvibes' internal RSS Reader displays an RSS feed with audio enclosures, it adds a Play button to those audio entries. Clicking that button opens the Netvibes Audio Player at the top of the Netvibes page. There, users can listen to the audio file (or podcast) while it loads, pause it, or click forward in the file player.</description>
        <category>uwa:howto</category>
            <pubDate>Thu, 30 Oct 2008 18:32:59 +0100</pubDate>
        </item>
        <item>
            <title>How to handle passwords securely?</title>
            <link>http://dev.netvibes.com/doc/uwa/howto/authentication?rev=1245765136</link>
            <description>Many of the most interesting widgets will need some form of authentication, which requires the passing of passwords. Because passwords must not be handled in a clear text way, as it is done for other preferences, we set up specific tools for handling them.</description>
        <category>uwa:howto</category>
            <pubDate>Tue, 23 Jun 2009 15:52:16 +0100</pubDate>
        </item>
        <item>
            <title>How to widgetize a RSS feed?</title>
            <link>http://dev.netvibes.com/doc/uwa/howto/build_a_rss_reader?rev=1225381224</link>
            <description>a.k.a, “How to turn a RSS feed into a UWA widget” or “How to build a RSS reader widget”.



One of the primary use of a widget is to provide users with an easy access to your data. Many websites rely on RSS in order to provide their data. If this is your case, it is in your best interest to provide your own widgetization of your RSS feed. This is how you do it.</description>
        <category>uwa:howto</category>
            <pubDate>Thu, 30 Oct 2008 16:40:24 +0100</pubDate>
        </item>
        <item>
            <title>How to display a Flash app within a widget?</title>
            <link>http://dev.netvibes.com/doc/uwa/howto/display_flash?rev=1225384450</link>
            <description>Flash apps have the same constraints as regular images: while displaying them is self-evident (just add the usual object/embed code), you have to cater for the files which width is bigger than that of the widget. See ”How to display an image within a widget?”</description>
        <category>uwa:howto</category>
            <pubDate>Thu, 30 Oct 2008 17:34:10 +0100</pubDate>
        </item>
        <item>
            <title>How to display an image within a widget?</title>
            <link>http://dev.netvibes.com/doc/uwa/howto/display_image?rev=1225384157</link>
            <description>Displaying an image within a widget is not that big a deal: just add the usual HTML tag (&lt;img src=”” alt=”” /&gt;), fill it with an absolute URL to the image to display, and you're done. You may style it with CSS through classes, works like any normal image.</description>
        <category>uwa:howto</category>
            <pubDate>Thu, 30 Oct 2008 17:29:17 +0100</pubDate>
        </item>
        <item>
            <title>How to turn a MiniAPI module into a UWA widget?</title>
            <link>http://dev.netvibes.com/doc/uwa/howto/from_module_to_widget?rev=1225365354</link>
            <description>First, thank you for having built modules for our previous API. The new API may have a steep learning curve, but we believe the advantages are truly worth it.

The major change to notice is that widgets are now based upon static files (nothing dynamic, like PHP or ASP.NET), and that all your data should be fetched and sent through Ajax calls. Therefore, your default BODY markup should be little more than &lt;p&gt;Loading...&lt;/p&gt; or a basic XHTML skeleton, and all your data should be built into your mar…</description>
        <category>uwa:howto</category>
            <pubDate>Thu, 30 Oct 2008 12:15:54 +0100</pubDate>
        </item>
        <item>
            <title>Translating the widget into the user's language</title>
            <link>http://dev.netvibes.com/doc/uwa/howto/localize_widget?rev=1225387484</link>
            <description>Netvibes is a website used by millions of people from several countries, and many of our users do not regularly use English, yet would probably benefit from your widget - provided its content is not specific to a region. 

Therefore, it would certainly benefit from being multilingual. This is called internationalization (or i18n, the fact of making the widget's string translatable) and localization (l10n, the fact of translating the internationalized, or i18n'd, strings).</description>
        <category>uwa:howto</category>
            <pubDate>Thu, 30 Oct 2008 18:24:44 +0100</pubDate>
        </item>
        <item>
            <title>How to open a new browser window?</title>
            <link>http://dev.netvibes.com/doc/uwa/howto/open_popup?rev=1225386181</link>
            <description>Your widget might need to open a new browser window (or a popup window) for specific purposes. This would usually be done using the window.open() method, but since UWA disables access to the window object, its open() method is unavailable.

UWA therefore integrates a special method, called widget.openURL(). It only takes one parameter: the target URL.</description>
        <category>uwa:howto</category>
            <pubDate>Thu, 30 Oct 2008 18:03:01 +0100</pubDate>
        </item>
        <item>
            <title>How to target a single element without getElementById?</title>
            <link>http://dev.netvibes.com/doc/uwa/howto/replace_getelementbyid?rev=1225385998</link>
            <description>The UWA environment disables the document and window object for security and portability reasons, but retains some of their methods, properties and events in its widget object (see ” JavaScript Framework”).

The getElementById() method from the document object, while very useful for everyday uses, has not been kept in widget because there can be multiple instances of a given widget on a single page, and thus potentially multiple elements with the same id.</description>
        <category>uwa:howto</category>
            <pubDate>Thu, 30 Oct 2008 17:59:58 +0100</pubDate>
        </item>
        <item>
            <title>Submitting a UWA widget to a 3rd-party platform</title>
            <link>http://dev.netvibes.com/doc/uwa/howto/submit_3rd_party?rev=1225390438</link>
            <description>Submitting a UWA widget to a 3rd-party platform




UWA widget are compatible with many existing platforms thanks to its compilators, and it is therefore possible to submit comiled UWA widget to other format-specific directories.

Submitting to iGoogle's gadgets directory

Requirements


iGoogle's directory requires a specific set of meta to be defined within the widget. UWA's compilers is taking care of converting existing meta into the proper format, but it cannot create meta that do not exist…</description>
        <category>uwa:howto</category>
            <pubDate>Thu, 30 Oct 2008 19:13:58 +0100</pubDate>
        </item>
        <item>
            <title>How to test a UWA widget?</title>
            <link>http://dev.netvibes.com/doc/uwa/howto/test_widget?rev=1225365145</link>
            <description>Before submitting your UWA widget to the Netvibes Ecosystem, you should make sure it works as expected. Here's how you can test your widget.

Local/standalone test


UWA widgets can be tested locally or on a server, thanks to two emulation files. Placed in the header of your widget, they will emulate the UWA environment, including the Netvibes UI, without having to be installed in Netvibes - this is called the standalone mode.</description>
        <category>uwa:howto</category>
            <pubDate>Thu, 30 Oct 2008 12:12:25 +0100</pubDate>
        </item>
        <item>
            <title>Using events in UWA</title>
            <link>http://dev.netvibes.com/doc/uwa/howto/using_uwa_events?rev=1225390351</link>
            <description>The widget object provides a handful of events to handle the interactivity of your widget: you can easily build useful methods to respond to specific events from the widget itself, or the user activity. those events are listed on the ”JavaScript Framework” section. The purpose of this page is not to list all available events, but to give examples of their use.</description>
        <category>uwa:howto</category>
            <pubDate>Thu, 30 Oct 2008 19:12:31 +0100</pubDate>
        </item>
        <item>
            <title>UWA IFrame method</title>
            <link>http://dev.netvibes.com/doc/uwa/howto/uwa_iframe?rev=1254153322</link>
            <description>You can easily display UWA widgets within your own environment, thanks to our IFrame method.
This document will show you how to build the correct URL to display a given widget within an IFrame on your platform. Relying on an IFrame has the advantage of both being simple and secure.
There can be any number of IFrames on one page, as long as each IFrame has a unique ID (related to the widget's chosen ID).</description>
        <category>uwa:howto</category>
            <pubDate>Mon, 28 Sep 2009 17:55:22 +0100</pubDate>
        </item>
        <item>
            <title>What makes a valid UWA widget?</title>
            <link>http://dev.netvibes.com/doc/uwa/howto/valid_widget?rev=1225364130</link>
            <description>In order for your widget to work properly within the UWA environment, it has to follow the following rules.

	*  It MUST be well-formed XML
	*  It MUST be UTF-8 encoded
	*  It MUST feature the Netvibes namespace
	*  It MUST place the JavaScript and CSS code in the HEAD section of the HTML file</description>
        <category>uwa:howto</category>
            <pubDate>Thu, 30 Oct 2008 11:55:30 +0100</pubDate>
        </item>
        <item>
            <title>How to use a widget on my site/blog?</title>
            <link>http://dev.netvibes.com/doc/uwa/howto/widget_export?rev=1225464590</link>
            <description>Ecosystem

UWA-iframeExposition server



BlogWidget is the name of the method to use when using a UWA widget outside conventional environments (Netvibes, iGoogle, Apple Dashboard...). In short, the UWA BlogWidget environment provides you with a JavaScript code that lets you use a UWA widget on any page, wether it's a blog post or sidebar, or a regular static website.</description>
        <category>uwa:howto</category>
            <pubDate>Fri, 31 Oct 2008 15:49:50 +0100</pubDate>
        </item>
        <item>
            <title>How to skin a widget?</title>
            <link>http://dev.netvibes.com/doc/uwa/howto/widget_templates?rev=1225381723</link>
            <description>In order to get the right look-and-feel for your widget, we built the UWA templates and controls. We advise you to base most of your code on those: this will ensure your widget always fits in the whole environment style.</description>
        <category>uwa:howto</category>
            <pubDate>Thu, 30 Oct 2008 16:48:43 +0100</pubDate>
        </item>
    </channel>
</rss>
