view

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.

<x:config version="1.0" xmlns:x="http://www.xopus.com/xmlns/config">
  <x:pipeline xml="xml/doc.xml" xsd="xsd/schema.xsd">
    <x:view name="WYSIWYG View">
      <x:transform xsl="xsl/presentation.xsl" />
    </x:view>
    <x:view name="Tree View">
      <x:treeTransform/>
    </x:view>
  </x:pipeline>
</x:config>

A view must contain one or more actions. The output of the final action in a view must be valid HTML. Xopus supports any number of consecutive actions in a view. This helps to modularize your XSL Stylesheets and your XML formats. You can use you own type references that can be transformed into xincludes. Or transform multiple XML formats to a single intermediate format for which you have an stylesheet for each publication channel (website, cd-rom, etc) you wish to support.

Special names

Xopus has a few predefined names that are automatically translated when the user interface language changes.

docView

Document View

defaultView

WYSIWYG View

treeView

Tree View

xmlView

XML View

printView

Print View


view element

Namespace: http://www.xopus.com/xmlns/config

Allowed Children

transform
(Optional)
treeTransform
(Optional)
resolveXIncludes
(Optional)

Attributes

name
The name that is displayed in the Views menu.

Parent Elements

pipeline

History

version event
Xopus 4.0.3 The special view names, like docView and xmlView, are automatically translated again. (Case 194449)
Xopus 4.0.0 Bug. The special view names are not translated anymore.
Xopus 4 Change. The experimental updateMode and renderMode attributes are obsolete.
Xopus 3.2.1 Change. Added the renderMode attribute.
Xopus 3 Change. Renamed id attribute to name. The default attribute is obsolete; the first view will be the default.
Xopus 2 Introduction.