Back to my page

Developers

How to test a UWA widget?

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.

To use these files, the head of your widget file must feature these two lines:

<link rel="stylesheet" type="text/css" 
  href="http://www.netvibes.com/themes/uwa/style.css" />
<script type="text/javascript" 
  src="http://www.netvibes.com/js/UWA/load.js.php?env=Standalone"></script>

These lines can remain in your file once you submit your widget to Netvibes: it won't harm anythingn they are ignored by all supported environments.

These should be the only external JS and CSS files featured in the widget's code. All other JS and CSS code should be placed directly in the widget, in the script and style tags.

Online test

In order to test your widget online, Netvibes has designed a special Netvibes module.

  1. In Netvibes, add one UWA module by going to this url: http://www.netvibes.com/subscribe.php?module=UWA ;
  2. Copy/paste a widget's URL in the Edit section of the UWA module.

You could also just click on the “Add to Netvibes” or “Add to iGoogle” buttons that are automatically displayed in the standalone display of your widget.

Desktop test

Apple Dashboard users: download the Dashboard UWA widget, install it on your Dashboard, copy/paste the URL of the online UWA widget you want to test (don't use a local, offline copy), and enjoy.

Opera users: download the Opera UWA widget, install it in Opera, copy/paste the URL of the online UWA widget you want to test (don't use a local, offline copy), and enjoy.

Testing on other platforms

There is no test widget for other supported platforms, so testing for Vista, Live.com and others can only be done once the widget has been added to Ecosystem - and therefore, once it has been duly tested in all other testing platforms (standalone, Netvibes, iGoogle, Dashboard and Opera).

You only submit your widget's URL to Ecosystem, not the widget file itself. So this file needs to be publicly available on your web-server. Ecosystem will then provide users with a correct link to your widget, in order to add it to Netvibes or export it to other platforms. All platforms directly use the code from your server, not a local copy.

In short, you must:

  1. choose wisely your widget's URL - something perennial ;
  2. never delete the widget before your have deleted it from Eco first. Even so, users who have installed your widget still rely on its code, so deleting the file would make their install fail, without explanation…

Ecosystem is where users will be able to export your widget to all supported platforms. Once you have submitted your widget, you will be able to test its efficiency by exporting it yourself to all other formats one by one.

Do not be afraid to submit untested code to Ecosystem! While the widget is immediately available to all Ecosystem users, you can always choose to put if offline in order to fix the issues that where noted on platform-specific tests.

Simply update the widget's code, and put it back online in Ecosystem (no need to submit it again) in order to further test it, until you are happy with the results.

Business

Partner with us.

Developers

Build once, run everywhere.

Community

Get involved, get localized.

Press

News. Media kits. Press releases.