There are several objects available from the API, that can be used to communicate with Xopus. These objects are properties of the window that Xopus runs in.

This is the main object representing Xopus itself. In the documentation you can find what properties and methods are available. The Editor object offers some methods for configuring certain UI elements, and fires the load event for example.

An Xopus Canvas is a representation of an island. Because there can be multiple islands running in Xopus the Editor.Canvas object offers methods to find the correct island. var canvas = Editor.Canvas.​getCanvasCollection()[0]; The above example returns the first Canvas. Canvas objects offer methods to change views, as they are defined on the island, to set and get parameters from XSL's and another way to load a new XML document. This XML document will then use the Schema that is defined on the island.

The IO object is a simple object which is mainly used to implement a save function. It can however also be used to change the way that Xopus loads XML, XSL and Schema.

When you need to load or save files to and from the server, the HTTPTools object offers GET, PUT and POST functionality. It is mostly used within a save function to POST the saved XML to the server. This is shown in other documents in this example.

The Editor.Selection object offers functionality to find the cursor and selection. This implements a similar interface to DOM Ranges to manipulate text and selection.

The XML document, it's elements, attributes and comments, are all represented by Xopus Object in the API. Take a look at the documentation about objects for more information.