If it is not, your extension may be rejected. The support webpage should be relevant to your extension. We’d recommend you include news of new releases and updates, detailed usage instructions, a portfolio of your other work, and contact details in case anyone needs to contact you with queries. You should seriously consider creating a support page for your extension. Create an extension support page (optional) For more details, see the version documentation section. Note that non-zero integers cannot start with 0 - in other words, 064 is not allowed. The version number can consist of one to four dot-separated integers. It needs to be memorable, short and appropriate, so it is easy for users to find and remember. Think carefully about the name of your extension. If you have been through all these before and just need a checklist to check your details against, go straight to the Submit your extension for review section. The following sections contain many hints and tips for creating effective descriptions, screenshots, etc. Prepare your details before submissionīefore you submit your extension, you should do the following to prepare, and get all the details you need together. See our Getting started tutorial and the rest of the documentation to build your own extension. We want published Opera extensions to be of a consistently high quality, so we have created this guide for you to follow. In case there are issues, they reject the extension and send it back to the developer to work on it more and submit it again (see Figure 1). The extension moderators then test the extension and publish it in our Opera extensions catalog. This guide explains how to publish your extension, which is a multi-step process that begins when you submit your extension for review. Introduction Figure 1: Overview of the publishing process - development, submission, testing, and publishing. When the extension satisfies all criteria, it will be published.Create an extension support page (optional).This can be done with the following code: Create a button, which is then added to the toolbar. Once you've configured your extension, you can start to create the actual code. We recommend creating an icon of 64×64 pixels for this.ĭownload the hello.png icon and save it in the "icons" folder inside your development folder. This specifies the icon used in the extensions manager and the Opera extensions site. You may have noticed the icon element referenced in the config file. Save this file as config.xml in your development folder. Go ahead and create a bare bones configuration file as follows: Opera extensions use the W3C Widgets packaging and configuration format, which you may be familiar with from Opera Widgets. This is where information such as the extension name, author and icon for the extension manager is specified. Configuring an extensionįirst, you’ll create the extension configuration file, which holds the meta data describing the extension. Opera extensions are written using regular open web standards, so all you need to get started is a copy of Opera 11 and your text editor or IDE of choice. You will create a toolbar button, which when pressed will open a popup that displays a Hello World! message. This article walks you through the basic steps to create your first Opera extension. Check out our new documentation for developing extensions for Opera 15 and higher and start building your own extensions. From Opera 15 onward, Opera 11 & 12’s extension format is no longer supported, and instead, we’ve switched to Chromium’s extension model.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |