Skip to main content
Jump to: navigation, search

Orion/Documentation/Developer Guide/Core client services

< Orion‎ | Documentation‎ | Developer Guide
Revision as of 15:04, 28 February 2012 by Susan (Talk | contribs) (orion.core.favorite)

Overview of core client services

Orion provides a number of basic infrastructure services that can be used by client scripts for performing various tasks. These services have no user interface component and can be used within any page of a client application. This section of the guide outlines what services are available, along with simple examples of how to use them.


The orion.core.favorite service is used to access and store the user's bookmarks or favorites. While a user may opt to use their own browser's bookmark mechanism instead, there are some specific advantages to using Orion's favorite service instead:

  • Favorites are persisted on the server, so the user can switch to another client computer or browser and access their familiar bookmarks
  • Favorites are associated with a specific Orion application and user, so favorites from different users or applications are not all mixed into a single place.
  • Favorites are used to suggest file and folder based parameters for other actions in Orion, such as moving and copying files to a location, or finding specific files.

Here is an example usage of the favorites service:


See orion.favorites.FavoritesService in the Orion client API reference for a complete list of functions available on the favorite service.


The orion.core.file service is used to provide file system contents for the Orion workspace. For example a plug-in can use this service to include content from one server into a workspace on another server. Each file service is displayed as a root element in the Orion Navigator page.

The code snippet below demonstrates a use of this service:

 provider.registerServiceProvider("orion.core.file", service, {Name: 'Sample File System'});

The above code will contribute a top level node to the Navigator named "Sample File System". The parameter "service" in the API above must provide the functions specified by the Orion file client API. Refer to orion.fileClient.FileClient in the client API reference for further details. For more information on client-server interaction, see Orion File Server API. For an complete file system example, see the sample file plugin in the Orion Git repository.


The marker service is used to store problems found by a builder or syntax validator. A client can register with this service for notification when markers are changed. Here is an example of a component that is registering for notification of marker changes:

     function(problems) {
       //do something with the new problems

Each marker is a simple JSON object with the following properties:

A string stating the description of the problem or marker
The line number of the marker
The column position of the marker


The preferences service manages a hierarchical set of preference nodes. Nodes are identified by a path string, where segments are delimited by the slash character ('/'). Each node is a JSON object with string keys and values that are String, Boolean, or Number.

Here is an example of retrieving a preference storing the list of recently used projects:

 prefService.getPreferences("/window/recent").then(function(prefs) {
   var projects =  prefs.get("projects");
   if (typeof projects === "string") {
     projects = JSON.parse(projects);
   if (projects && projects.length && projects.length > 0) {
     //do something with the projects

And here is an example of adding a new project to the list, and storing the result back in the preference service:

 prefService.getPreferences("/window/recent").then(function(prefs) {
   var projects = prefs.get("projects");
   if (typeof projects === "string") {
     projects = JSON.parse(projects);
   projects.push({name: "My Proj", location: ""});
   prefs.put("projects", projects);


The text link service scans text for segments that could be interpreted as hyperlinks, and inserts appropriate anchor elements representing each link. For example the service could scan for email addresses in a piece of text and convert them to mailto: links.

Here is an example of using the text link service:

var divWithLinks = linkService.addLinks(someText);, body, "first");

The text link service makes use of link scanners contributed by plugins to perform the analysis and replacement of text with links. If no link scanners are available, the text link service simply returns a DOM element containing the entire input text.


The content type service tells Orion about a new kind of file. The content types contributed to this service don't have any direct effect on the Orion UI, but they can be referred to by other services that need to associate themselves with a particular kind of file. For an example, see orion.navigate.openWith.

The Orion client UI defines a bunch of content types by default: see webEditingPlugin.html in the client UI code.

Service attributes

An Array containing one or more content types to register. Each element of the array defines a new content type, and must have this shape:
String The unique identifier of the content type. This is a simple hierarchical name and should start with a category like "text" or "image".
String The user-readable name of the content type.
String[] Optional. Array of file extensions characterizing this content type. (Extensions are given without the leading "." character).
String[] Optional. Array of filenames characterizing this content type. Use this when a type does not have a characteristic file extension, but rather a filename. (For example, "Makefile", "README", "passwd").
String Optional. If this content type is a subtype of another, this gives the parent content type's ID.

Service methods

None. This service is purely declarative.


This example code contributes contributes a new content type for Perl files. A Perl file extends from "text.plain" and has the extension .pl.

 provider.registerServiceProvider("orion.file.contenttype", {}, {
   contentTypes: [{  id: "text.perl",
                     name: "Perl",
                     extension: ["pl"],
                     "extends": "text.plain"
                  }] });

The example code below contributes a new content type for Ant build files. An Ant build file is a special kind of XML file that always has the name "build.xml".

 provider.registerServiceProvider("orion.file.contenttype", {}, {
   contentTypes: [{  id: "text.ant",
                     name: "Ant build file",
                     filename: ["build.xml"],
                     "extends": "text.xml"
                  }] });

Back to the top