Skip to main content
Jump to: navigation, search

Difference between revisions of "Orion/Documentation/Developer Guide/Simple plugin example"

(formatting)
(Reorganize)
Line 42: Line 42:
 
<script src="plugin.js" />
 
<script src="plugin.js" />
 
</source>
 
</source>
 +
 +
=== Plugin ===
 
* Next, we'll add some code that exposes a service to Orion. Add the following, again inside the &lt;head&gt; tags:
 
* Next, we'll add some code that exposes a service to Orion. Add the following, again inside the &lt;head&gt; tags:
 
<source lang="javascript">
 
<source lang="javascript">
Line 47: Line 49:
 
     window.onload = function() {
 
     window.onload = function() {
 
         var provider = new eclipse.PluginProvider();
 
         var provider = new eclipse.PluginProvider();
        var serviceImpl = { /* TODO */ };
+
 
        var serviceProperties = { /* TODO */ };
+
        provider.registerServiceProvider("orion.edit.command", serviceImpl, serviceProperties);
+
 
         provider.connect();
 
         provider.connect();
 
     }
 
     }
 
</script>
 
</script>
 
</source>
 
</source>
* At this point, we've got an honest-to-goodness Orion plugin, albeit one that doesn't do much. Let's go over the various parts in detail:
+
At this point, we've got an honest-to-goodness Orion plugin, albeit one that does nothing. Let's go over the various parts in detail:
 
<!-- ** <tt>window.onload</tt> — -->
 
<!-- ** <tt>window.onload</tt> — -->
** <tt>var provider = new eclipse.PluginProvider()</tt> — <span style="background-color: #00ff00;">TODO</span><br>Optionally, an object giving metadata about the plugin can be provided as an argument to the constructor.
+
* <tt>var provider = new eclipse.PluginProvider()</tt> — <span style="background-color: #00ff00;">TODO</span><br>Optionally, an object giving metadata about the plugin can be provided as an argument to the constructor.
** <tt>var serviceImpl</tt> — This object gives the implementation of our service, the part that will do the actual work.<br>When someone requests our service — for example, by calling <tt>getService()</tt> on a <tt>ServiceReference</tt> object — our plugin will be loaded into an IFrame, and our service becomes available for use. The <tt>function</tt>-typed properties of the serviceImpl object define the methods of our service that people can call.
+
* <tt>provider.connect();</tt> — <span style="background-color: #00ff00;">TODO</span>
** <tt>var serviceProperties</tt> — Every service provider can supply '''properties''', which is an object that holds metadata about the service provider. Orion stores these properties when a plugin is installed <span style="background-color: #00ff00;">(?)</span>, and they can later be queried without causing the plugin to be loaded.<br>Properties are often used to filter out service providers that are irrelevant to a particular task. For example, if you're writing a service provider for content assist, you'd specify what file types your provider applies to in its properties. The content assist loader then only loads plugins that provide content assist for the particular file type being edited.  This is important because plugin load can be an expensive operation, so we want to avoid doing it if possible.<!-- If you're familiar with Eclipse desktop, you can think of service properties as analogous to the extensions declared in a plugin.xml file, since these can be queried without loading the plugin itself. -->
+
 
** <tt>provider.registerServiceProvider("orion.edit.command", serviceImpl, serviceProperties);</tt> — <span style="background-color: #00ff00;">TODO</span>
+
=== Implementing the service ===
** <tt>provider.connect();</tt> — <span style="background-color: #00ff00;">TODO</span>
+
Now we're going to create and register a service with the [[Orion/Documentation/Developer Guide/Plugging into the editor#orion.edit.command|"orion.edit.command"]] service type.
* Now we'll fill in the <tt>serviceImpl</tt> and <tt>serviceProperties</tt> objects with the actual details of the service that our plugin will provide.
+
Add the highlighted lines as shown:
<span style="background-color: #00ff00;">TODO</span>
+
 
* Before continuing, make sure that <tt>reversePlugin.html</tt> looks like this:
+
<code>
 +
    window.onload = function() {
 +
        var provider = new eclipse.PluginProvider();<br />
 +
<span style="background-color: #0f0;">        var serviceImpl = {  };
 +
        var serviceProperties = {  };
 +
        provider.registerServiceProvider("orion.edit.command", serviceImpl, serviceProperties);</span><br />
 +
        provider.connect();
 +
    }
 +
</code>
 +
 
 +
Let's go over what we have now:
 +
* <tt>var serviceImpl</tt> — This object gives the implementation of our service, the part that will do the actual work.<br />When someone requests our service — for example, by calling <tt>getService()</tt> on a <tt>ServiceReference</tt> object — our plugin will be loaded into an IFrame, and our service becomes available for use. The <tt>function</tt>-typed properties of the serviceImpl object define the methods of our service.<br />
 +
* <tt>var serviceProperties</tt> — Every service provider can supply '''properties''', which is an object that holds metadata about the service provider. <br /><!-- Orion stores these properties when a plugin is installed <span style="background-color: #00ff00;">(?)</span>, and they can later be queried without causing the plugin to be loaded.<br>Properties are often used to filter out service providers that are irrelevant to a particular task. For example, if you're writing a service provider for content assist, you'd specify what file types your provider applies to in its properties. The content assist loader then only loads plugins that provide content assist for the particular file type being edited.  This is important because plugin load can be an expensive operation, so we want to avoid doing it if possible. since these can be queried without loading the plugin itself. --> If you're familiar with Eclipse desktop, you can think of service properties as analogous to the extensions declared in a plugin.xml file <br />
 +
* <tt>provider.registerServiceProvider("orion.edit.command", serviceImpl, serviceProperties);</tt> — This call registers our serviceImpl and serviceProperties with the service type "orion.edit.command".<br />
 +
 
 +
Now we'll fill in the <tt>serviceImpl</tt> and <tt>serviceProperties</tt> objects with the actual details of the service.
 +
First, change the <tt>serviceImpl</tt> object to look like this:
 +
 
 +
<source lang="javascript">
 +
        var serviceImpl = {
 +
                run: function(text) {
 +
                    return text.split("").reverse().join("");
 +
                }
 +
            };
 +
</source>
 +
 
 +
 
 +
Make sure that your copy of <tt>reversePlugin.html</tt> looks like this:
 
<source lang="javascript">
 
<source lang="javascript">
 
<!DOCTYPE html>
 
<!DOCTYPE html>

Revision as of 09:45, 13 June 2011

Warning2.png
Article under construction
This How To is not finished yet. Some information may be incomplete.


This page explains how to write a plugin for Orion. It's intended for developers who want to extend Orion's functionality.

What's a plugin?

A plugin is an HTML file containing some JavaScript that knows how to connect to the Orion client. Plugins can be hosted on any web server and installed into Orion using their URL.

In order to be useful, a plugin should provide one or more services. When Orion needs a service contributed by a plugin, it loads the plugin inside an IFrame.

Orion currently supports a small set of extension points: service types that plugins can contribute to, in order to customize the client and add more functionality. These include things like:

  • Adding more commands to the editor toolbar
  • Adding more commands to the navigator view
  • Adding content assist for new file types
  • Adding syntax highlighting rules for new file types

What you need

Every plugin must include the following JavaScript library:

You can copy-paste its contents into a <script> tag in your plugin, or load it externally like so:

<script src="plugin.js" />

Writing the plugin

Let's make a plugin that adds a button to the toolbar of the Orion editor. When clicked, it will reverse the selected text in the editor. This is not a very useful feature, but it'll be a good introduction to the concepts involved.

Creating the plugin HTML file

  • Create a new HTML file called reversePlugin.html with the following content:
<!DOCTYPE html>
<html>
<head>
    <meta charset="UTF-8" />
    <title>Reverse Plugin</title>
</head>
<body></body>
</html>
  • What we have now isn't a plugin yet. It's just a bare-bones HTML file. The next step is to include the API we'll need to talk to Orion.
  • Grab the plugin.js file (see What you need) and put it in the same folder as reversePlugin.html. Then add this inside the <head> tags of the HTML file:
<script src="plugin.js" />

Plugin

  • Next, we'll add some code that exposes a service to Orion. Add the following, again inside the <head> tags:
<script>
    window.onload = function() {
        var provider = new eclipse.PluginProvider();
 
        provider.connect();
    }
</script>

At this point, we've got an honest-to-goodness Orion plugin, albeit one that does nothing. Let's go over the various parts in detail:

  • var provider = new eclipse.PluginProvider()TODO
    Optionally, an object giving metadata about the plugin can be provided as an argument to the constructor.
  • provider.connect();TODO

Implementing the service

Now we're going to create and register a service with the "orion.edit.command" service type. Add the highlighted lines as shown:

   window.onload = function() {
       var provider = new eclipse.PluginProvider();

var serviceImpl = { };

       var serviceProperties = {   };
       provider.registerServiceProvider("orion.edit.command", serviceImpl, serviceProperties);
provider.connect(); }

Let's go over what we have now:

  • var serviceImpl — This object gives the implementation of our service, the part that will do the actual work.
    When someone requests our service — for example, by calling getService() on a ServiceReference object — our plugin will be loaded into an IFrame, and our service becomes available for use. The function-typed properties of the serviceImpl object define the methods of our service.
  • var serviceProperties — Every service provider can supply properties, which is an object that holds metadata about the service provider.
    If you're familiar with Eclipse desktop, you can think of service properties as analogous to the extensions declared in a plugin.xml file
  • provider.registerServiceProvider("orion.edit.command", serviceImpl, serviceProperties); — This call registers our serviceImpl and serviceProperties with the service type "orion.edit.command".

Now we'll fill in the serviceImpl and serviceProperties objects with the actual details of the service. First, change the serviceImpl object to look like this:

        var serviceImpl = {
                run: function(text) {
                    return text.split("").reverse().join("");
                }
            };


Make sure that your copy of reversePlugin.html looks like this:

<!DOCTYPE html>
<html>
<head>
    <meta charset="UTF-8" />
    <title>Reverse Plugin</title>
    <script>
    window.onload = function() {
        var provider = new eclipse.PluginProvider();
        var serviceImpl = {
                run: function(text) {
                    return text.split("").reverse().join("");
                }
            };
        var serviceProperties = { name: "Reverse Text", key: ["e", true] };
        provider.registerServiceProvider("orion.edit.command", serviceImpl, serviceProperties);
        provider.connect();
    }
</script>
</head>
<body></body>
</html>

Testing the plugin

First we need to host our plugin somewhere.


Now that you've got a URL for reversePlugin, install it:


Now let's try it out.

  • In Orion, go to the navigator and create a new file called test.txt.
  • Click on test.txt to open the editor.
  • You'll see a new button on the editor toolbar:
    Image
  • Select some text, click the button, and it should be reversed.

Examples

Here are some existing plugins we've written. View their source code to see how they work:

http://orionhub.org/plugins/sampleCommandsPlugin.html
Contributes several sample actions to the Orion navigator by using the orion.navigate.command service type.
http://orionhub.org/plugins/htmlSyntaxHighlightPlugin.html
Contributes syntax highlighting support for HTML files by using the orion.edit.highlighter service type.
http://bokowski.github.com/format-js.html
Contributes a "Beautify JS" button to the editor toolbar by using the orion.edit.command service type.
http://mamacdon.github.com/m6/uglify/uglify-plugin.html
Contributes an "Uglify JS" button to the editor toolbar byusing the orion.edit.command service type.

See also

Back to the top