Skip to main content
Jump to: navigation, search

Orion/Documentation/Developer Guide/Plugging into the shell

< Orion‎ | Documentation‎ | Developer Guide
Revision as of 13:18, 14 June 2013 by Grant (Talk | contribs) (fix code example)

Overview of contributing services to the Shell

The Shell page provides a view through which users can interact with Orion via a command-line interface. The page provides some basic commands for navigating Orion's workspace, and defines a service that allows plug-ins to contribute additional commands.

The service is used to contribute commands to the Shell page. When the service is executed, an object containing the user-supplied argument values is passed to the service's callback method. The command then optionally returns a response (a return value) to be displayed in the Shell.

Service methods

Implementations of may define the following function:

Takes the user-supplied command-line arguments (if any) as an argument, and optionally returns a response string in plain text (no HTML is allowed).

The only context where a contributed command would not define a service method is to assist with the contribution of sub-commands. For example, to contribute commands "tar create" and "tar extract", a parent command "tar" without a service method must first be contributed.

Service attributes

Implementations of define the following attributes:

The name that is typed at the command line to invoke the command
(Recommended) A brief description of the command
(Optional) A longer description of the command
(Optional) An array of the parameters that the command accepts

The Shell page currently uses GCLI as its underlying shell widget, and consequently has adopted its syntax for parameter specification. For details on this syntax begin reading at the "## Default argument values" header in the GCLI Writing Commands doc. The basic parameter object attributes are:

The parameter's identifier
One of { string | boolean | number | array | selection | a custom}
(Recommended) A brief description of the parameter
(Optional) The value assumed by the parameter if the user does not supply a value for it, makes the parameter optional

The service is used to contribute parameter types to the Shell page. These enable contributed commands to have custom parameters with dynamically-computed completion suggestions. The service is executed when the Shell page needs either completion suggestion values to display, or the string representation for a given value.

Service methods

Implementations of define the following functions:

parse(arg, typeSpec, context)
Takes the currently-typed user string and returns an object with completion suggestions. The arguments to this function are:
An object with properties {prefix: string, suffix: string, text: string}, contains the user's currently-typed string for an instance of this parameter
This parameter's typeSpec as defined by the command that is using it
An object with additional information; currently its only property is {lastParseTimestamp: number}, which can aid in determining when the completion suggestions being returned should be recomputed

The return value for this service must be either an orion.Deferred (if computation of the result object has to be done asynchronously), or an object with the following properties:

One of the following numbers:
0: (MATCH) the currently-typed string matches a valid value (ie.- the typing of this parameter value can now be considered complete)
1: (PARTIAL) the currently-typed string partially matches a valid value (ie.- the typing of a valid value in progress)
2: (ERROR) the currently-typed string does not match a subset of the initial characters of any valid values
(Optional) An error message to display in the Shell page
An array of {name: string, value: object} objects that are valid completions for the currently-typed string (name is the string to display in the suggestions list)
If the currently-typed string is a match for a valid value then set this property to that {name: string, value: object} value, otherwise set its value to undefined
stringify(object, typeSpec)
(Optional) Returns an object's string representation that is appropriate for display in the Shell page's output area. An example case where this string may not be the same as the "name" that was specified for it by the parse service is if a typed relative path should be resolved to an absolute path. If this service is not implemented then the object's "name" that was specified for it by the parse service implementation is used as its display string. The arguments to this function are:
The object to stringify
This parameter's typeSpec as defined by the command that is using it

Service attributes

Implementations of define the following attribute:

The name of the parameter type (used in the plug-in definition of contributed commands)


The following sample plug-in contributes a "lab" type and "printLab" command to the Shell:

<script src="/orion/plugin.js"></script>
<script src="/orion/Deferred.js"></script>

 /* first, contribute a custom type that will be used by the contributed command */

 var CompletionStatus = {
   MATCH: 0,
   PARTIAL: 1,
   ERROR: 2
 var labTypeProperties = { 
   name: "lab"
 var labTypeImpl = {
   parse: function(arg, typeSpec, context) {
      * Compute all potential prediction objects here, can be done asynchronously
      * if needed (eg.- if need to wait on an XHR).
     var ottawaValue = {name: 'Ottawa', address: 'Kanata, actually', climate: 'colder'};
     var rtpValue = {name: 'RTP', address: 'Raleigh', climate: 'warmer'};
     var potentialPredictions = [
         name: 'Ottawa', /* the string to be typed */
         value: ottawaValue /* the corresponding object */
         name: 'RTP', /* the string to be typed */
         value: rtpValue /* the corresponding object */

     var value; /* undefined until a valid value is fully typed */
     var status; /* one of the CompletionStatus values above */
     var predictions = []; /* an [] of {name: typedString, value: object} */

     for (var i = 0; i < potentialPredictions.length; i++) {
       if (potentialPredictions[i].name.indexOf(arg.text) === 0) {
         if (potentialPredictions[i].name === arg.text) {
           value = potentialPredictions[i].value;

     status = CompletionStatus.ERROR;
     if (predictions.length > 0) {
       status = value ? CompletionStatus.MATCH : CompletionStatus.PARTIAL;
     var result = {
       value: value,
       message: (status === CompletionStatus.ERROR ? ("'" + arg.text + "' is not valid") : undefined),
       status: status,
       predictions: predictions

      * If all of the above can be computed synchronously then just return result directly.
      * If the above cannot be done synchronously (eg.- waiting on an XHR) then return
      * a promise as demonstrated below and resolve it when the result becomes ready.
     var promise = new orion.Deferred();
       function() {
         promise.resolve(result); /* result has become ready some time later */
     return promise;

 /* contribute a command that uses the custom type */

 var printLabProperties = { 
   name: "printLab",
   description: "Print a lab location",
   parameters: [{
     name: "lab",
     type: {name: "lab", showClimateToo: true},
     description: "The name of the lab to print info for"
   returnType: "string"
  var printLabImpl = {
   callback: function(args) {
     var result = "Lab name: " + + "\nLocation: " + args.lab.address;
     if (args.lab.climate) {
       result += "\nClimate: " + args.lab.climate;
     return result;

 var provider = new orion.PluginProvider();
 provider.registerServiceProvider("", labTypeImpl, labTypeProperties);
 provider.registerServiceProvider("", printLabImpl, printLabProperties);

When this plug-in is installed the user can use the "printLab" command in the Shell. The first image below shows a user is in the process of entering a printLab command, and is shown a list of valid argument values.


In the following image the printLab command has executed and its result is shown in the output area.


Back to the top