Creating an Xopus Island
The Xopus island contains references to the XML, Schema and XSL files that are used for editing. It can also contains refences to configuration files, Javascript files for API calls, and CSS for styling of the editable page.
An island looks like this:
<div xopus="true" autostart="false">
<x:config version="1.0" xmlns:x="http://www.xopus.com/xmlns/config">
<xml>
<x:pipeline xml="document.xml" xsd="schema.xsd">
<x:view name="WYSIWYG View">
<x:transform xsl="stylesheet.xsl"/>
</x:view>
</x:pipeline>
</xml>
</x:config>
</div>
It can be recognized by the xopus="true" attribute. A pipeline is used to reference the XML file, Schema file, and points to XSL files on views. Multiple views can be configured.
XML
By using a dynamic page to write the island, you can use the same island for different pages. All islands in this example are drawn by xopus-island.aspx which loads the proper XML file by using a querystring parameter.
Schema
Schema can be changed in the a similar way. This demo using a single schema, but loading a different XML file with a different schema makes no difference for Xopus. Schema's are cached by Xopus, and therefore using a dynamic island makes better use of available memory.
XSL and views
Each view requires a tranformation. Transformations need to reference XSL files. These XSL files are used to draw the XML file as HTML in the editor. The output of the XSL needs to be valid XHTML.
A special transformation (which uses an XSL that is supplied with Xopus) is available through the following configuration:
<x:view name="Xml View">
<x:treeTransform />
</x:view>
This treeTransform, or other XSL's can also be used in conjuction with other XSL files by placing it following another transformation. This allows you to view the output of your XSL as an XML view, enabling you to pinpoint problems in the output.
Other options
Javascript to be used with the API can be placed in the x:config as follows:
<x:javascript src="js/editing.js"/>
The above example includes js/editing.js on the island.
External configuration files, often used for roleMapping configurations can also be referenced:
<x:import src="config/config.xml"/>