Elements

The <advanced/> contains the advanced options for the configuration.

The contains the advanced options for the configuration.

The allowPersonalisation element specifies if the user can show or hide buttons or button groups in the toolbar using the context menu.

The allowPersonalisation element specifies if the user can show or hide buttons or button groups in the toolbar using the context menu.

The attribute element is used to specify the role of a certain attribute in the current xml format.

The <config/> contains the global configuration.

<config version="1.0" xmlns="http://www.xopus.com/xmlns/config"/> is the root of an Xopus Local Configuration. It specifies the uri of the xml document to be loaded, its xml schema and what xsl files should be used to render the views.

The debugMode element specifies whether Xopus runs in user debug mode. In that mode more thorough checks are performed which allows Xopus to show more detailed error messages. This does have a performance penalty. 

The defaultLanguage attribute is used to declare the language to be used by the spellChecker when no language has been declared through the xml:lang attribute on the document itself.

The html div element becomes an Xopus Canvas when it has an xopus="true" attribute.

The element element is used to specify the role of a certain element in the current xml format.

If hideStatusbar is set Xopus will not show the statusbar.

Xopus allows users to surf to other pages in its content frame. If such a new page does not contain an Xopus Canvas, Xopus will go to standby mode. This element controls if Xopus should hide itsself in that case or if it should just disable its toolbar and statusbar.

If ignoreUnsavedChanges is set Xopus will exit without a warning even if the user has unsaved changes.

The <import/> element can import settings from an external Xopus Local Configuration file. The root element of that file is a config element.

The <javascript/> element points to a javascript file that is executed when Xopus activates an Xopus Canvas. The script is executed after the configuration is loaded but before any associated files are loaded. The script has access to the Xopus API.

A lookup element can be used to specify an external source of values for an attribute. The source can be any html document. The document will be opened by Xopus when a value for the attribute can be specified. The html document can return its value using script.

The lookupConfig element contains lookup element. Each lookup element specifies an attribute and a url. The url points to an html page that can generate a list of value from which the user can pick one.

The maxInsertSize element specifies the size of table insert dialog.

The <miscellaneous/> element contains miscellaneous settings.

A param element can be used to pass information to the xsl stylesheet.

The pipeline element defines the xml pipeline. It specifies the xml document to load and the xml schema to use for validation.

Xopus can also resolve xincludes. An xinclude points to an xml fragment at a certain uri. Resolving it will replace the xinclude element with the xml fragment it refers to.

The roleMapping element contains all attribute and element elements for which a role is specified.

The spellChecker element contains spellchecker API related settings. Xopus has a spellchecker built in. It offers the user interface for a spellchecker.

The spellCheckerServer element specifies the url of the spellcheck server used by Xopus. Due to browser security restrictions must the server application run on the same server and port as the webserver from which Xopus was started.

The subCanvasMode element specifies whether Xopus should make the entire document contentEditable or just the parts that are indicated as contentEditable.

The subCanvasMode element specifies whether Xopus should make the entire document contentEditable or just the parts that are indicated as contentEditable.

The tableEditor element contains specific settings for the table editor.

The toolbar element contains specific settings for the Xopus toolbar.

The toolbar element contains specific settings for the Xopus toolbar.

A transform action transforms the incoming xml using a specified xsl stylesheet.

When validateOnLoad is set Xopus will validate the whole document when it is loaded. By default Xopus will assume that the loaded document is schema valid.

The validateSimpleTypes settings can be used to prevent Xopus from validating simple schema types. Each value will be treated as though it was defined as generic string type.

Contains schema validation specific settings.

A view consists of one or more actions to be performed consecutively on the xml. The user can choose the preferred view from the Xopus menu.

The <xml> element is an xml island within html. The contents of the <xml> element must be well formed xml. So empty elements must be closed: <empty/> and &, < and > must be escaped: &, < and >.