Sign up

Widgets » FAQ

Frequently asked questions

Login problems?

Lost your password?

Get a new password here

Can't login?

Make sure you have cookies enabled and try again. If you still have problems try deleting all your browser cookies (in Opera, menu: tools/delete private data) and try again. If this does not help, get a new password and try one more time. If nothing helps, you can contact us.

Can I log in using my Opera Community username and password?

Yes, you can log into widgets.opera.com using your existing My Opera account.

About Opera Widgets

What are Opera Widgets?

Opera Widgets are small web programs running outside the browser. Widgets can be both fun and useful, like games or development tools. They float on your desktop for quick and easy access to information or services.

What do I need to run Opera Widgets?

You can run Opera Widgets using the Opera 9 browser.

What kind of widgets are available?

There are many kinds of widgets. Examples include games, news feeds, weather information widgets, and web developer tools like color pickers, pixel rulers and others. See some examples of widgets

Are the widgets free?

Yes, you may use all the widgets on this site for free.

Where can I learn more about installing and using Opera Widgets?

The Opera Widgets user guide is a good place to learn about widgets, how to install them and how to use them.

Who makes Opera Widgets?

Anyone can make Opera Widgets. Widgets are made by widget creators from all over the world. Some are made by employees at Opera Software.

Can I make Opera Widgets?

Yes, it's easy! Start by reading the Widgets developer tutorial and see the section Making widgets in the FAQ.

What are the technologies behind Opera Widgets?

Opera Widgets are made using standard web technologies, such as HTML, CSS, JavaScript, SVG, AJAX.

What platforms are supported for Opera Widgets?

You can run Opera Widgets on all platforms supported by the Opera browser, including Windows, Linux and Mac.

What devices do Opera Widgets run on?

Opera Widgets run on your desktop computer and will soon also run on mobile phones. Opera Software delivers the Opera Widgets technology to users of our Opera 9 SDK for devices, including producers of set top boxes for TVs.

I get an error saying "Widget not approved for your browser version". What does this mean?

Opera Widgets run on different platforms and devices. Some widgets are optimized for certain platforms or devices or contain errors that means they wont run properly on the given platform or device. In such cases, the author of the widget may have specified this when publishing his or her widget. In other cases, Opera Software staff have discovered such problems and limited the widget accordingly.

Can I use Opera Widgets on my mobile?

Not yet, but soon.

What are mobile widgets?

Mobile widgets are widgets that run on mobile phones. They give you quick and easy access to services like like traffic information, games, notes sharing and so on. They also allow you to take that information with you offline.

Making Opera Widgets

What do I need to know to make Opera Widgets?

You need to know some HTML. If you want to make them look good, you need to know some CSS. If you want to make them interactive, you need to know some JavaScript.

Where can I read more about making Opera widgets?

See the widget section on dev.opera.com.

About the widgets.opera.com site

Who made this web site?

This web site was made by the Web Applications Team at Opera Software ASA.

What's the site for?

It's a place for sharing and finding Opera Widgets, and a place to meet other widget authors.

Publishing widgets

Widget authors can publish their widgets on our site to share them with the world.

Why should I publish my widget?

Publishing your widget on widgets.opera.com makes your widget available to thousands of users quickly and easily. Through these users you can get feedback and bug reports to make your widget even better.

What rights to the widgets do I have when publishing widgets on widgets.opera.com?

See the Terms on the Publish page.

How do I publish a widget?

Before publishing:

  1. Test your widget to find bugs. Test on different platforms, devices and Opera browser versions if you can.
  2. Check your config.xml files for errors. It needs to work for the widget to be accepted. Opening the file in a different browser will check it for well formedness.
  3. Check that your config.xml contains enough information. We will use this file to supply information about your widget.
  4. Translate the widget if you can.
  5. Compress your HTML, style, script, translations, resource files and config.xml into a zip file. Files and directories in the widget should go in the root of the zip file.
  6. Take a screenshot of the widget.

Publishing:

  1. Visit the Publish page
  2. Select your widget archive file (.zip) in the archive file dialog and publish it.
  3. Read through and verify the information from your config.xml. Feel free to add more text.
  4. Select your screenshot in the screenshot file dialog.
  5. Select the target devices for your widget. Make sure you've tested on those devices.
  6. Select a group for your widget.
  7. Select the target languages for your widget. Make sure you've supplied translations.

What are target devices?

Target devices are those devices that your widget runs on. Usually your widget will work on most devices, although in some cases it may require different styles or tweaked functionality.

What are target languages

Target languages are languages this widget has translations for.

What are target countries?

Target countries are the countries your widget applies to. If it's a news feed from a Polish speaking web site, the target country would be Poland. If it has no specific target country, select 'All'.

How can I get people to try and use my widget?

Now that you have spent a lot of time making a widget, you naturally want people to try it out. A good widget name, description, and snapshot image which tells the user what to expect when running the widget, often helps to increase the number of views.

There are primarily two ways of achieving this: Writing a good description and taking good screenshots.

Remember that people from different backgrounds, from different countries and cultures, at different ages, with different platforms, devices and browser versions will read your description before trying your widget. Not everyone understand things the way you do. Feedback from friends and familiy can often reveal issues that need clarification.

How should I write widget descriptions?

We've provided two fields you can use to communicate with your users. The short description is taken from your config.xml file and shown on all lists the widget appears on. The long description is shown on your widget's page.

Use the short description to catch the user's eye, stating what your widget does and what value users can get out of it. It may be a tagline, but it should be informative. You should avoid phrases like "Download me" or "This is a super cool widget".

The following are examples of descriptions you might write: "Stay updated on the weather in location X, Y, Z.", "Relax with this classic game of XYZ.", "Get quick access to the XYZ specification.", "Measure your web page elements with this expandable ruler.", "Read news from Slashdot".

Use the long description to tell the user what features your widget has, how it was implemented, about changes in different versions, rules for games and so on.

.

How should I make screenshots to show off my widget?

You should take screenshots that show the core functionality of your widget. This way people will instantly see the strength of the widget.

  • Show the main page, not the login page or the preferences page if your widget has them.
  • Show your widget in action. If it's a game, show the game running. If it can have data, show it with data.
  • You can crop the screenshot to just show the most important parts of the widget.

The screenshot should ideally have a size of 300x225 pixels. We will resize screenshots above that size which may lead to undesired effects.

Why did the file size or description of my widget change when I published it?

When you upload your widget file, we unpack it and test its contents before repacking it and putting it on the server. This may lead to some differences in compression and file size. Additionally, if you change the widget information in the Configuration step, this information is put back into your zip file. Finally, Opera Software reserves the right to update or correct the description fields at any time.

Can I delete one of my widgets?

No, you can't delete your own widgets.

Widget approval

All widgets need to be approved by Opera Software staff.

How are widgets approved?

We only check for errors to make sure our users get a good experience. We do not take responsibility for the content of the widgets or make any guarantees about it's functionality. See our disclaimer.

What are the requirements for getting a widget approved?

These are some of the guidelines that apply to widgets under review.

  • The widget must have a sensible name and description.
  • The widget must not have obvious bugs. I.e., test it before publishing.
  • The widget must not contain malicious or destructive code.
  • The widget must not contain or use copyrighted information you don't have the rights to.
  • The widget must not contain or point to adult or hateful content.

My widget was rejected. What do I do?

You will have received a message stating what guidelines the widget breaks or other issues encountered. Fix these issues and re-publish the widget an we'll review it again.

The Widget Issue tracking system

widgets.opera.com has an issue tracking system that widget authors and users can use to manage and report bugs.

How do I report a problem with a widget?

First of all, you should read through the issue listings for the widget in question and see if anyone has already reported the same bug. You'll find the bug listing in the "Bugs" tab on the information page for the widget.

Check if you have the latest version of the widget. The issue might have been fixed in a later version.

If you have the latest version, and can't find a similar bug:

  • Visit the information page for the widget
  • Click the link "Or file a bug report".
  • Fill in a short title, describing the essence of the problem.
  • Describe the bug in as much detail as you can.
  • Read through your information again to double check it.
  • Check the field stating that you've looked through already reported bugs.
  • Hit the submit button.

Who fixes bugs?

The author of the widget fixes bugs. This means that it may take some time so be patient. Opera Software staff do not fix bugs in user published widgets.

How should I write a bug report?

  • Describe as clearly as you can what you were doing when the bug occured. What did you click on, what data had you filled in, etc.
  • Supply any error messages you've received.
  • Specify which Opera version, platform and device you ran the widget on.

Copyright © 2001 - 2008 Opera Software. All rights reserved. About | Contact | Privacy | Disclaimer | Web analytics powered by HitsLink.HitsLink Logo