Xopus Specifications

Learn more about what Xopus needs and what you need for Xopus. Also read up on what Xopus supports.

Client/System Requirements

Supported Operating Systems

Windows 2000, Windows XP, Windows Vista and Windows 7
Mac OS X 10.4 Tiger and up
Linux (we test with Ubuntu)

Supported Browsers

Internet Explorer 6.0, 7.0, 8.0 and 9.0
Firefox 3.6 and the latest version of Firefox

Additional Software

Use in Internet Explorer requires MSXML 6.0 libraries or MSXML 4.0 libraries

MSXML 4.0 libraries will be automatically installed on first use if not already present. The user must have the right to install applications.

In some environments users are not allowed to install applications. In those cases a manual installer is available that can be used to install the MSXML4 libaries if a user is allowed to download and start an application.

We advise to use the MSXML 6.0 libraries, which can be downloaded, but are also automatically installed with Office 2007, Windows Vista and 7, and Visual Studio 2003.

Minimal Hardware

Pentium III class processor at 1 GHz
512 MB memory
approx. 2 MB free harddisk space
800x600 monitor resolution

Recommended Hardware

Pentium IV class processor at 2 GHz
1 GB memory
approx. 2 MB free harddisk space

A good processor is more important than memory. Xopus needs quite a lot of processor time to calculate what is and isn't possible for the XML through the Schema.

Keep in mind that the following things can cause Xopus to slow down

  • The amount of HTML that is outputted by the XSL
    The more HTML there is, the more needs to be redrawn every time Xopus redraws. This can become slow.
  • Schema, and then specifically not-strict schema. The more strict it is, the less possibilities there are for Xopus to calculate.
  • CSS. Complex CSS styles will slow down the HTML.

To test if you can run Xopus on your computer, try the demos, and see how Xopus handles itself on your computer.

Server Requirements

Any webserver is sufficient.

There are out-of-the-box integrations available for many server side systems and protocols. Contact us for more information.

Specifications

Table Editor

The Xopus table editor can edit any table following the HTML table model.

Several roles can be defined:

  • Row container (<table> / <tbody>)
  • Cell container (<tr>)
  • Cell (<td>)
  • Header (<th>)
  • Row span (rowspan="")
  • Column span (colspan="")

The names of these elements and attributes can be changed to any localname and namespace url.

Operations

The table editor allows the user to perform the following operations. Operations are only available if they result in a valid XML document.

  • Insert table
  • Insert column
  • Insert row
  • Insert cell
  • Move table up/down
  • Move column left/right
  • Move row up/down
  • Move cell left/right
  • Delete table
  • Delete column
  • Delete row
  • Delete cell
  • Merge cells up/down/left/right
  • Split cells up/down/left/right
  • Change cell to header
  • Change header to cell
  • Change all cells in a row to headers
  • Change all headers in a row to cells

XML Operations

Xopus allows the user to perform several structural operations on the XML. Operations are only available if they result in valid XML.

  • Create and insert new element
    If the element has mandatory children, these will be inserted. If there is a choice between two or more mandatory children, a dialog is shown. The API can be used to specify a default element in this case. If the new element has a required attribute the Attribute Dialog is shown and the user can give a valid value.
  • Create and insert new attribute
    The attributes dialog is shown to allow the user to specify the value of the new attribute.
  • Delete element
  • Delete attribute
  • Move element up/down
  • 'Indent'/'outdent'
    Changes the nesting for list like structures.

W3C XSLT Support

Supported Elements

  • apply-imports
  • apply-templates
  • attribute attribute-set
  • call-template
  • choose
  • comment
  • copy
  • copy-of
  • decimal-format
  • element
  • fallback
  • for-each
  • if
  • import
  • include
  • key
  • namespace-alias
  • number
  • otherwise
  • param
  • processing-instruction
  • stylesheet
  • template
  • transform
  • variable
  • when
  • with-param

Partially Supported Elements

message
Termination can be controlled, but the message will not be displayed.
sort
The data-type attribute, if present, must be either text or number; QName values are not supported.
text
The disable-output-escaping attribute is not supported.
value-of
The disable-output-escaping attribute is not supported.

Unsupported Elements

output
This element is ignored in Xopus.
preserve-space
Whitespace is always preserved by Xopus.
strip-space
This element is ignored in Xopus.

W3C XML Schema Support

Supported Elements

  • annotation
  • appinfo
  • attribute
  • attributeGroup
  • choice
  • complexContent
  • complexType
  • element
  • documentation
  • enumeration
  • extension
  • factionDigits
  • field
  • group
  • import
  • include
  • key
  • keyref
  • length
  • list
  • maxExclusive
  • maxInclusive
  • maxLength
  • minExclusive
  • minInclusive
  • minLength
  • pattern
  • redefine
  • restriction
  • schema
  • selector
  • sequence
  • simpleContent
  • simpleType
  • totalDigits
  • union
  • unique

Partially Supported Elements

all
The use of all-elements should be avoided as it can have a negative impact on performance. This only applies to all constructions with more than approximately eight child elements.
any
Any-elements only give the choice between elements for which Xopus has loaded a schema.

Unsupported Elements

  • anyAttribute
  • notation
  • whiteSpace

W3C XML Base support

Xopus recognizes xml:base attributes whereever it needs to resolve URIs. This includes XML Schema documents, XSLT documents, XInclude references and Xopus configuration files.

There currently are no comments on this page.

Your comment will be added to the forum.

HTML will be shown as HTML code. Linebreaks and links starting with http:// are automatically resolved.