StyleVisionuser manual StyleVision Power Stylesheetsee under SPS Database (Enterprise and Professional editions)see under DB

Altova StyleVision 2007

Altova® StyleVision® 2007 Enterprise Edition is an application for graphically designing and editing StyleVision Power Stylesheets. A StyleVision Power Stylesheet (SPS) can be used for the following purposes:

To control a graphical WYSIWYG view of XML documents in Authentic View , which is an XML document editor available in the following Altova products: Altova XMLSpy , Altova StyleVision , Altova Authentic Desktop , and Altova Authentic Browser .

To enable the editing of databases (DBs) via Authentic View and to generate database reports in HTML , RTF, and PDF format.

To generate XSLT stylesheets based on the SPS design. (Both XSLT 1.0 and XSLT 2.0 are supported.) The XSLT stylesheets can be used outside StyleVision to transform XML documents into outputs such as HTML , XSL-FO (used to generate PDF and PostScript files), and RTF (Rich Text Format, used by word processing applications such as MS Word) .

To generate, directly from within StyleVision , HTML , RTF, XSL-FO, and PDF output from an XML document. In the case of DB-based SPS s, StyleVision can additionally generate, for each SPS , an XML Schema based on the DB and an XML instance document that adheres to this schema and contains data from the DB.

StyleVision also enables you to import an HTML document and create an XML document from it. Documentationoverview of Support options Abbreviationsused in user manual

About this Documentation

This documentation is the user manual delivered with StyleVision . It is available as the built-in Help system of StyleVision , can be viewed online at the Altova website , and can also be downloaded from there as a PDF, which you can print. The user manual is organized into the following sections:

An introduction , which explains what an SPS is and introduces the main features and concepts of StyleVision .

A description of the user interface , which provides an overview of the StyleVision GUI.

A tutorial section, which is a hands-on exercise to familiarize you with StyleVision features.

High-Level Procedures , which describes usage at a broad level: for example, schema sources, interaction with databases, and command line options.

Content Editing Procedures , which explains how static and dynamic components are created and edited in the SPS .

Presentation Procedures , which explains how SPS components are formatted and laid out.

Additional Editing Procedures , which explains how a range of additional SPS editing features are used.

Authentic View , which describes how XML documents are edited in Authentic View . The StyleVision GUI contains an Authentic View preview tab, in which you can immediately test the Authentic View output.

HTML Import , which describes how an XML Schema and XML document can be created that is based on the structure and content of an HTML document.

A reference section containing descriptions of all symbols and commands used in StyleVision .

An FAQ section that gives the causes of, and solutions to, commonly encountered problems.

Appendices containing information about the Altova XSLT Engine information and the conversion of DB datatypes to XML Schema datatypes ; technical data about StyleVision ; and license information.

How to use We suggest you read the Introduction and User Interface sections first in order to get an overview of StyleVision features and general usage. Doing the tutorial next would provide hands-on experience of creating an SPS . The Procedures sections ( High-Level Procedures , Content Editing Procedures , Presentation Procedures , and Additional Editing Procedures ) provide detailed descriptions of how to use various StyleVision features. For subsequent reference, the Reference section provides a concise description of all toolbar icon, design symbols, and menu commands, organized according to toolbar and menu. The Authentic View and HTML Import section s provide s , respectively, information about editing in Authentic View and converting HTML documents to XML and XML Schema documents. The Frequently Asked Questions section is intended to answer questions that might arise in the course of using StyleVision . Support options Should you have any question or problem related to StyleVision , the following support options are available:

Check the Help file (this documentation). The Help file contains a full text-search feature, besides being fully indexed. The Frequently Asked Questions section of this documentation contains a discussion of commonly encountered problems, organized by functionality.

Check the FAQs and Discussion Forum at the Altova Website .

Contact Altova's Support Center .

Commonly used abbreviations The following abbreviations are used frequently in this documentation:

SPS : StyleVision Power Stylesheet

DB : Database

CSS : Cascading Style Sheets

FAQ : Frequently Asked Questions

StyleVisionintroduction

Introduction

This section introduces you to Altova® StyleVision® 2007 . It consists of the following sub-sections:

What Is an SPS? , which explains the role of an SPS in an XML environment and with respect to StyleVision .

Product Features , which provides an overview of the key features of StyleVision .

Terminology , which lists terms used in the StyleVision user interface and in this documentation.

Setting up StyleVision , which describes how StyleVision is to be correctly set up.

SPSgeneral description of and Authentic View (Enterprise and Professional editions) and StyleVision and XSLT stylesheets

What Is an SPS ?

A StyleVision Power Stylesheet (or SPS) is an extended XSLT stylesheet which is used to graphically create a design for an HTML output document :

to control the display and entry of data in the Authentic View Authentic View of XML documents and databases (DBs); and

to specify the output design of an XML document transformation.

An SPS is saved with the file extension .sps . Design of the SPS An SPS is created graphically in StyleVision . It is based on a schema (DTD or XML Schema) ; if the SPS is to be used with a DB, it is based on an XML Schema generated automatically by StyleVision from the DB structure . The design of the SPS is flexible. It can contain dynamic and static content. The dynamic content is the data in one or more XML document s or DB s . The static content is content entered directly in the SPS . Dynamic content can be included in the design either as straight text or within components such as input fields, combo boxes, and tables. Additionally, dynamic content can be manipulated (using Auto-Calculations) and can be displayed if certain conditions in the source document are fulfilled. Different pieces of content can be placed at various and multiple locations in the SPS . Also, the SPS can contain various other components, such as images, hyperlinks, and JavaScript functions. Each component of the SPS can then be formatted for presentation as required. The SPS and Authentic View When a finished SPS is associated with an XML document or DB, that XML document or DB can be edited in Authentic View Authentic View . Authentic View is an ideal solution for enabling the distributed and graphical editing of an XML document or DB . Multiple users can edit an XML document or DB in the graphical user interface presented by Authentic View . In StyleVision , as you design an SPS , you can preview and test the SPS (in the Authentic View tab for that SPS ). For a detailed description of how SPS s work with Authentic View , see SPS and Authentic View . The SPS and XSLT stylesheets After you have completed designing the SPS , you can generate XSLT stylesheets based on the design you have created. StyleVision supports both XSLT 1.0 and XSLT 2.0, and from a single SPS , you can generate XSLT stylesheets for HTML, RTF, and XSL-FO output ( Enterprise edition only; in Professional and Standard Editions, only HTML output is supported ). The generated XSLT stylesheets can be used in external transformations to transform XML documents based on the same schema as the SPS from which the XSLT stylesheet was generated . For more information about procedures used with XSLT stylesheets, see the section Generated Files . The SPS and output You can also use StyleVision to directly generate output ( HTML, RTF, XSL-FO, and PDF in Enterprise Edition; HTML in Professional and Standard Editions ). The tabs for Output Views display the output for the active SPS document directly in the StyleVision GUI. The required output can also be generated to file: (i) from within the GUI via the File | Save Generated Files command; or by invoking StyleVision via the command line . These procedures are described in more detail in the High-Level Procedures section. StyleVisionproduct features Product featureslisting of Featuresof StyleVision

Product Features

The main product features of StyleVision are listed below in two groups:

General product features , which are high-level features

SPS design features , which are features related to the design of the SPS

General product features Given below is a list of the main high-level features of StyleVision .

The SPS can use multiple schemas and/or a single database (DB) source , thus enabling the use of multiple XML document sources together with a DB source.

Multiple SPS designs can be open simultaneously, with one being active at any given time. Each SPS design is shown in a separate tab.

While designing the SPS , Authentic View , output views and stylesheets can be displayed by clicking the respective tabs. This enables you to quickly preview the output and XSLT code , and test Authentic View features .

When an SPS is associated with an XML source document or source DB , the source document can be edited directly in the Authentic View of StyleVision .

DB reports can either be viewed in StyleVision or saved as an HTML , PDF, and RTF file s .

Both XSLT versions (1.0 and 2.0) are supported. XSLT 2.0 provides powerful data access and manipulation features.

In the Enterprise Edition, multiple output formats (HTML, RTF, and PDF) are generated from a single SPS design.

Conditions can be set on SPS components to process them differently for different outputs . With this level of granularity, different outputs can be flexibly structured to take in the requirements of that particular output.

Both XSLT files and output files can be generated and saved , either directly from within the GUI or by calling StyleVision from the command line .

HTML documents can be converted to XML .

SPS design features Given below is a list of the main StyleVision f eatures specific to designing the SPS .

The SPS can contain static text , which you enter in the SPS , and dynamic text , which is selected from the source document source document/s .

Dynamic content is inserted in the design by dragging-and-dropping nodes from the schema source schema sources .

Dynamic content can be inserted as text, or in the form of a data-entry device (such as an input field or combo box ). When inserted as a data-entry device such as a combo box , additional possibilities are available. For example, the value of the node can be selected (by the Authentic View user) from a list of enumerations.

The structure of the design is specified and controlled in a single main template . This structure can be modified by optional templates for individual elements — known as global templates because they can be applied globally for that element.

Named templates enable the modularization and re-use of templates in a manner similar to the way functions are used.

A common feature of XML documents is the repeating data structure. For example, an office department typically has several employees. The data for each employee would be stored in a data structure which is repeated for each employee. In the SPS , the processing for each such data structure is defined once and applied to each relevant node in turn (the employee node in our example).

Repeating data structures can also be inserted as dynamic tables . This provides looping in a structured, table format, with each loop through the data structure producing a row (or, if required, a column) of the table.

A repeating element can be sorted on one or more sort-keys you select, and the sorted element set is sent to the output (HTML , RTF, and PDF ).

The conditional templates feature enables one of a set of templates to be processed according to what conditions in the XML document or system environment are fulfilled. This enables processing that is conditional on information contained in the source document or that cannot be known to the SPS document creator at the time of creation (for example, the date of processing). The available conditions are those that can be tested using XPath 1.0 or XPath 2.0 expressions.

Auto-Calculations enable you to manipulate data from the source document/s and to display the result. This is useful, when you wish to perform calculations on numbers (for example, sum the prices in an invoice), manipulate strings (for example, change hyphens to slashes), generate content, etc. The available manipulations are those that can be effected using XPath 1.0 or XPath 2.0 expressions.

When data is edited in Authentic View , t he result of Auto-Calculations can also be passed to a node in the source document. This procedure is  referred to as updating the XML node (with the value of the Auto-Calculation).

Additional validation enables individual XML document nodes to be validated (additionally to schema validation) against an XPath expression defined for that node. In this way, Authentic View users can be alerted when the data they enter is invalid; a customized error message for the node can indicate the problem.

Images can be inserted in the design. The URI for the image can be static (entered in the SPS) , or dynamic (taken from a node in the source document), or a combination of both static and dynamic parts.

Two types of lists can be created: static and dynamic. In a static list , each list item is defined in the SPS . In a dynamic list , a node is created as a list item; the values of all instances of that node are created as the items of the list.

Static and dynamic links can be inserted in the design. The target URI can be static (entered in the SPS) , or dynamic (taken from a node in the source document), or a combination of both static and dynamic parts.

Static bookmarks can be inserted. These serve as anchors that can be linked to with a hyperlink.

Parameters can be declared globally for the entire SPS . A parameter is declared with a name and a string value, and can be used in XPath expressions in the SPS . The parameter value you declare is the default value and can be overridden by a value passed from the command line .

With the Input Formatting feature, the contents of numeric XML Schema datatype nodes can be formatted as required for Authentic View display and, in the case of some formats, optionally for output display. Input Formatting can also be used to format the result of an Auto-Calculation .

JavaScript functions can be used in the SPS to provide user-defined functionality for Authentic View and HTML output.

A number of predefined HTML formats are available via the GUI and can be applied to individual SPS components.

A large number of CSS text formatting and layout properties can be applied to individual SPS components via the Styles entry helper .

Additionally, CSS styles can be defined for HTML selectors at the global level of an SPS and in external CSS stylesheets. These style rules will be applied to Authentic View and HTML output, thus providing considerable formatting and layout flexibility.

Styles can also be assigned using XPath expressions . This enables style property values to be selected from XML documents and to set property values conditionally.

For paged output (typically RTF and PDF), a number of page layout options , such as orientation, margins, page-numbering, and headers and footers, can be specified in the SPS .

Setting up StyleVision FO processor (Enterprise edition)setting up Command line utility StyleVisionBatch

Setting up StyleVision

Altova StyleVision runs on Windows 2000 and Windows XP. After downloading StyleVision from the Altova website , double-click the executable ( .exe ) file to run the setup program. The setup program will install StyleVision at the desired location. The Altova XSLT Engines (1.0 and 2.0) are built into StyleVision and are used for all internal transformations. You, therefore, do not need to install an XSLT Engine additionally to your StyleVision installation. You will, however, need to have the following components installed:

Internet Explorer 5.5 or later, for Authentic View and HTML Preview. Internet Explorer 6.0 and later has better XML support and is recommended.

Microsoft Word 2000 or later, for RTF Preview. Microsoft Word 2003 or later is recommended.

An FO processor of your choice, for PDF Preview. For the XSLT transformation to XSL-FO, StyleVision offers an option for filtering out XSL-FO properties that are not supported by FOP 0.20.5, which is the Apache XML Project's FO processor . Using this filter ( see screenshot below ) would be useful only when the FOP processor is used. For some FO processors, additional components, such as the Java Runtime Environment, may be required.

Adobe Acrobat Reader, for PDF Preview (Acrobat Reader 6.0 or later is recommended).

Note on FO processors StyleVision can pass the XSL-FO document (generated by transforming the source document) to an FO processor of your choice. In the FO Processor input field of the Options dialog ( Tools | Options | XSL-FO ) ( screenshot below ), enter the location of the file that starts the FO processor. The FO processor you select is used to generate the PDF Preview as well as the PDF files created via the File | Save Generated Files command. The FOP processor of the Apache XML Project is available free of charge as a convenient installer package at the Components Download page on the Altova website . This package downloads, installs, and configures FOP for use within your product interface. However, you still have to select the FOP executable ( fop.bat ) in the Options dialog. Alternatively, you could download FOP from the Apache Website . Note that FOP requires a Java Runtime Environment, downloadable free of charge from Sun's Developer Network Site . After you have installed the FO processor, you should set the XSL-FO compliance level in the Options dialog ( Tools | Options | XSL-FO ). Note: Since conformance levels between any two FO processors can differ widely, and since the XSL-FO specification may be interpreted differently from processor to processor, the PDF produced by different processors from a single FO file could be different. Command line utility: StyleVisionBatch A command line utility , StyleVisionBatch .exe , is included in the installation. This utility can be used to call the file-generation functionality of StyleVision from the command line. StyleVisionBatch is located in the StyleVision application folder. Interfacesee GUI User Interfacesee GUI GUIdescription of Menu barmoving Toolbarsmoving

User Interface

The StyleVision GUI ( illustration below ) consists of the following parts:

A menu bar . Click on a menu to display the items in that menu. All menus and their items are described in the User Reference section. The menu bar also contains the Minimize, Restore, and Close Active Document buttons.

A toolbar area . The various toolbars and the command shortcuts in each toolbar are described in the User Reference section.

A tabbed Main Window , which displays one or more open SPS documents at a time. In this window, you can edit the design of the SPS , edit the content of Authentic View , and preview the XSLT stylesheets and output .

The Design Entry Helpers — the Schema Sources , Design Tree , Style Repository , Properties , and Styles windows — which can be docked within the application GUI or made to float on the screen.

A status bar , which displays application status information.

The Main Window and Design Entry Helpers are described in more detail in the sub-sections of this section. Note: The menu bar and toolbars can be moved by dragging their handles to the required location. See also: Reference section , for a listing and description of all menu commands. Reference | Toolbars , for a listing and description of all toolbars. GUIMain Window of multiple documents in document views in Document viewsin GUI Documentsopening and closing Scroll buttonsin Main Window

Main Window

The Main Window ( illustration below ) is where the SPS design, Authentic View , XSLT stylesheets, and output previews are displayed. SPS documents in the Main Window

Multiple SPS documents can be open in StyleVision , though only one can be active at any time. The names of all open documents are shown in tabs at the bottom of the Main Window, with the tab of the active document being highlighted.

To make an open document active, click its tab. Alternatively, use the options in the Windows menu.

If so many documents are open that all document tabs are not visible in the document-tab bar, then click the appropriate scroll button (at the right of the document-tab bar; see illustration above ) to scroll the tabs into view.

To close the active document, click the Close Document button in the menu bar at the top right of the application window (or select File | Close ).

Document views A document is displayed in the following views, one of which can be active at a time:

Design View , in which you design the SPS and edit JavaScript functions for use in that SPS . The view can be toggled between the design document and the JavaScript Editor by clicking the dropdown menu arrow and selecting Design or JavaScript, as required.

Authentic View , which enables you to immediately see the Authentic View of an XML document (the Working XML File ). The SPS is dynamically applied to the Working XML File , thus enabling you to try out Authentic View .

Output Views (HTML , RTF, and PDF output). These views are a preview of the actual output format and of the XSLT stylesheet used to generate that output. The view can be toggled between the output preview and the XSLT stylesheet by clicking the dropdown menu arrow and making the appropriate selection.

Each of the views listed above is available as a tab at the bottom of the Main Window in the Views Bar. To select a view, click on its tab. The tab of the selected view is highlighted. Design Viewdescription of and JavaScript Editor JavaScript Editorin Design View

Design View

The Design View ( illustration below ) is the view in which the SPS is designed. In Design View, you create the design of the output document by (i) inserting content (using the Entry Helpers, the keyboard, and the various content creation and editing features provided in the menus and toolbars); and (ii) formatting the content using the various formatting features provided in the Entry Helpers and menus. These aspects of the Design View are explained in more detail below. Design View can also be switched to a JavaScript Editor , in which you can create and edit JavaScript functions which then become available in the GUI for use in the SPS . To switch to the JavaScript Editor , click the dropdown button in the Design tab ( see illustration ) and select JavaScript from the dropdown menu. To switch back to Design View, click the dropdown button in the JavaScript tab and select Design from the dropdown menu. Authentic Viewdescription of and Working XML File Working XML Fileand Authentic View

Authentic View

In the Authentic View tab of the Main Window, you can view and edit the Working XML File in its Authentic View . This view enables you (i) to see how your Authentic XML document will look, and (ii) to test the Authentic View created by the SPS . This is particularly useful if you wish to test the dynamic features of Authentic View . For example, you could test how Authentic View behaves when you:

Add new elements and attributes

Add new paragraphs or table rows

Change values that affect conditional templates

Authentic View and the Working XML File In order for Authentic View to be displayed, a Working XML File must be assigned to the active SPS document This Working XML File must be valid according to the schema on which the SPS is based. StyleVision creates a temporary XML file that is based on the Working XML File, and it is this temporary file that is displayed in the Authentic View tab of the Main Window. Modifications that you make in Authentic View will modify the temporary XML file. The Working XML File itself will not be modified till you explicitly save the modifications (with the menu command File | Save Authentic XML Data ). If no Working XML File is assigned, you will be prompted to assign a Working XML File when you click the Authentic View tab. Authentic View limitations The Authentic View in the Main Window is similar to the full-fledged Authentic View available in XMLSpy and Authentic Desktop except in the following major respects:

Authentic View Entry Helpers are not available in the GUI. To insert or append nodes, you must right-click and use the context menus.

XML tables are not available for insertion.

Text state icons are not available.

To test these features, you should use the full-fledged Authentic View in XMLSpy or Authentic Desktop . A full description of how to use Authentic View is given in the section Editing in Authentic View . For additional information, please see the Authentic View tutorial in the XMLSpy or Authentic Desktop user manual. Output Viewsdescription of XSLT stylesheet previewin Output Views Working XML Fileand Output Views

Output Views

There are three Output View tabs, one each for HTML, RTF, and PDF outputs. Each output tab ( illustration below ) displays: (i) the XSLT stylesheet for that output; and (ii) a preview of the output produced by transforming the Working XML File with the XSLT stylesheet. In an Output View tab, the view can be switched between the XSLT stylesheet and the output preview by clicking the dropdown button in the Output View tab and selecting the XSLT option or the output preview option as required. The Output View tab ( illustration below ) displays: (i) the XSLT-for-HTML stylesheet generated from the SPS design; and (ii) a preview of the HTML output, produced by transforming the Working XML File with the generated  XSLT stylesheet. In the HTML Output View tab, the view can be switched between the XSLT-for-HTML stylesheet and the HTML output preview by clicking the dropdown button in the HTML Output View tab and selecting the XSLT option or the output preview option as required. XSLT view The XSLT view displays the XSLT stylesheet generated for that output format XSLT-for-HTML generated from the currently active SPS . The stylesheet is generated afresh each time the XSLT view is selected. A stylesheet in an Output View tab is displayed with line-numbering and expandable/collapsible elements; click the + and – icons in the left margin to expand/collapse elements. The stylesheet in XSLT view cannot be edited, but can be searched (select Edit | Find ) and text from it can be copied to the clipboard (with Edit | Copy ) . Note: The XSLT stylesheets generated from the SPS can be separately generated and saved using the File | Save Generated Files command. Output preview The Output HTML preview displays the output produced by transforming the Working XML File with the XSLT stylesheet for that output format XSLT-for-HTML . The output is generated afresh each time the Output HTML preview is clicked. Note that it is the saved version of the Working XML File that is transformed — not the temporary version that is edited with Authentic View . This means that any modifications made in Authentic View will be reflected in the Output HTML preview only after these modifications have been saved to the Working XML File ( File | Save Authentic XML Data ). If no Working XML File is assigned when the Output HTML preview is selected in the Output HTML View tab, you will be prompted to assign a Working XML File. For DB-based SPS s, there is no need to assign a Working XML File since a temporary non-editable XML file is automatically generated when the DB is loaded and this XML file is used as the Working XML File . Note: The output files generated from the SPS can be separately generated and saved using the File | Save Generated Files command. Design Entry Helpersdescription of Auto Hide Hide Design Entry Helper windowsdocking floating Auto Hidefeature of Design Entry Helpers Hidefeature of Design Entry Helpers DockingDesign Entry Helper windows FloatingDesign Entry Helper Windows Schema Sources windowsee also Design Entry Helpers Design Treesee also Design Entry Helpers Style Repositorysee also Design Entry Helpers Propertiessee also Design Entry Helpers Stylessee also Design Entry Helpers

Design Entry Helpers

The Design Entry Helpers are GUI components that help you design the SPS and provide information about individual SPS design components. They are enabled when the Design View of a document is active, and are disabled when Authentic View or Output View (HTML , RTF, or PDF View) is active. There are five Design Entry Helpers ( listed below ), each of which is described in a sub-section of this section.

Schema Sources

Design Tree

Style Repository

Styles

Properties

Docking and floating the Design Entry Helper windows Design Entry Helper windows can be docked in the StyleVision GUI or can be made to float on your screen. To dock a window, drag the window by its title bar and drop it on any one of the four inner or four outer arrowheads that appear when you start to drag. The inner arrowheads dock the dragged window relative to the window in which the inner arrowheads appear. The four outer arrowheads dock the dragged window at each of the four edges of the interface window. To make a window float, (i) double-click the title bar; or (ii) drag the title bar and drop it anywhere on the screen except on the arrowheads that appear when you start to drag. Alternatively, you can also use the following mechanisms. To float a docked window, click the Menu button at the top-right of a docked window ( see screenshot below ) and select Floating. This menu can also be accessed by right-clicking the title bar of the docked window. To dock a floating window, right-click the title bar of the floating window and select Docking from the menu that appears; the window will be docked in the position in which it was last docked. Auto-Hiding Design Entry Helper windows A docked window can be auto-hidden. When a Design Entry Helper window is auto-hidden, it is minimized to a tab at the edge of the GUI. In the screenshot below, all five Design Entry Helpers have been auto-hidden: two at the left edge of the GUI, two at the bottom edge, and one at the right edge. Placing the cursor over the tab causes that window to roll out into the GUI and over the Main Window. In the screenshot below, placing the cursor over the Styles tab causes the Styles Design entry helper to roll out into the Main Window. Moving the cursor out of the rolled-out window and from over its tab causes the window to roll back into the tab at the edge of the GUI. The Auto-Hide feature is useful if you wish to move seldom-used entry helpers out of the GUI while at the same time allowing you easy access to them should you need them. This enables you to create more screen space for the Main Window while still allowing easy access to Design Entry Helper windows. To auto-hide a window, in a docked window, click the Auto Hide button (the drawing pin icon) at the top right of the window ( screenshot below ). Alternatively, in the Menu , select Auto Hide; (to display the Menu , right-click the title bar of the window or click the Menu button in the title bar of the docked window). The window will be auto-hidden. To switch the Auto-Hide feature for a particular window off, place the cursor over the tab so that the window rolls out, and then click the Auto Hide button ( screenshot below ). Alternatively, in the Menu , deselect Auto Hide; (to display the Menu , right-click the title bar of the window or click the Menu button in the title bar of the window). Note: When the Auto-Hide feature of a Design Entry Helper window is off, the drawing pin icon of that window points downwards; when the feature is on, the drawing pin icon points left. Hiding (closing) Design Entry Helper windows When a Design Entry Helper window is hidden it is no longer visible in the GUI, in either its maximized form (docked or floating) or in its minimized form (as a tab at an edge of the GUI, which is done using the Auto-Hide feature ). To hide a window, click the Close button at the top right of a docked or floating window ( screenshot below ). Alternatively, in the Menu , select Hide; (to display the Menu , right-click the title bar of the window or click the Menu button in the title bar of the window). To make a hidden (or closed) window visible again, select the name of the Design Entry Helper in the View menu. The Design Entry Helper window is made visible in the position at which it was (docked or floating) when it was was hidden. See also: Design View , for an overview of Design View. View Menu , for additional ways of turning the display of deign entry helpers on and off. Schema Sourcesentry helper window Working XML File Template XML File (Enterprise and Professional editions) Multiple schema sources (Enterprise edition) Main schema Root elements

Schema Sources

The Schema Sources window ( screenshot below ) enables you to do the following:

Specify the schemas and/or DBs on which the SPS will be based.

Specify the schema or DB on which the SPS will be based.

Specify the Working XML File and Template XML File for each the schema source.

Select multiple root elements (document elements) for a schema.

Drag nodes from a schema tree and drop them into the design. These nodes represent the XML content that is to be included in the output.

Lists all global elements in all schema sources the schema source . A global element can be created as a global template.

Adding a schema A schema is added by clicking the dropdown arrow of the Add Schema icon in the toolbar. This pops up a menu ( screenshot below ) that enables you to add an XML Schema or DTD, or a user-defined schema. : (i) an XML Schema or DTD; (ii) a schema generated by StyleVision from a DB; or (iii) a user-defined schema. The Working XML File and Template XML File When a schema is added, it is listed under the Schema Sources item. Each schema has an entry for the Working XML File within the XML item. two important sub-items (within the XML item), in order:

The Working XML File .

The Template XML File .

To select or change the Working XML File or Template XML File , click the or button , respectively , and browse for the required file. Root elements For each schema, there is a Root elements (aka document elements ) list. This list consists of all the root elements you select for the schema (see below for how to do this). Each root element can be expanded to show its content model tree. It is from the nodes in these root element trees that the content of the main template is created. Note that the entry point of the main template is the document node of the main schema, which you can select or change at any time (see below for how to do this). To select the root elements for a schema, do the following: Click the Select button at the right of the Root elements item. This pops up the Select Root Elements dialog ( screenshot below ), in which you can select which of the global elements in the schema is/are to be the root elements. See SPS Structure | Schema Sources for an explanation of the possibilities offered by a selection of multiple root elements. Additionally, all the global elements in all added schemas the schema are listed under the All Global Elements item. For each global element, a global template can be created. Multiple schema sources Multiple schemas can be added to an SPS , and for each schema, a separate Working XML File, Template XML File, and list of root elements can be selected. To designate one schema as the main schema, right-click it and select Set as Main Schema in the context menu that pops up. Selecting the main schema One schema from among the added schemas can be designated the main schema. The importance of the main schema is that its document node is the entry point of the main template. To select the main schema, in Design View, right-click the schema and select Set As Main Schema. Toolbar and schema tree icons The following toolbar icons are shortcuts for common Schema Sources entry helper commands.

	Adds a schema from a file or a DB, or adds a user-defined schema. The option is selected from a dropdown list.
	In a user-defined schema, adds a child element to the document element or appends a sibling element to the selected element. Alternative levels are available by clicking the dropdown arrow of the icon.
	In a user-defined schema, adds an attribute to the document element or appends an attribute at the same level to the selected node. Alternative levels are available by clicking the dropdown arrow of the icon.
	Make/Remove Global Template, enabled when a global element is selected.
	Synchronize tree toggle. When toggled on (icon has border), selecting a node in the tree selects (i) the corresponding node in the design, and (ii) the corresponding node in the Design Tree if the Synchronize Tree icon in the Design Tree window is toggled on. Whe toggled off, the corresponding node in the design is not selected. Switch the toggle off if dragging a node from the tree and dropping it to the desired location in the design proves difficult.
	Remove the selected item.
	Browse for the Working XML File for that schema.
	Browse for the Template XML File for that schema.

	Adds a schema from a file or a DB, or adds a user-defined schema. The option is selected from a dropdown list.
	In a user-defined schema, adds a child element to the document element or appends a sibling element to the selected element. Alternative levels are available by clicking the dropdown arrow of the icon.
	In a user-defined schema, adds an attribute to the document element or appends an attribute at the same level to the selected node. Alternative levels are available by clicking the dropdown arrow of the icon.
	Make/Remove Global Template, enabled when a global element is selected.
	Synchronize tree toggle. When toggled on (icon has border), selecting a node in the tree selects (i) the corresponding node in the design, and (ii) the corresponding node in the Design Tree if the Synchronize Tree icon in the Design Tree window is toggled on. Whe toggled off, the corresponding node in the design is not selected. Switch the toggle off if dragging a node from the tree and dropping it to the desired location in the design proves difficult.
	Remove the selected item.
	Browse for the Working XML File for that schema.

Context menu The context menu contains the following commands:

Add schema

Set as main schema

Add element, add attribute, convert to element/attruíbute

Make/Remove Global Template

Expand and collapse commands. These enable the tree to be expanded and collapsed. Options include the entire Schema Sources tree, up to the selected level, and to expand from or collapse to the selected item.

Symbols used in schema trees Given below is a list of the symbols in schema trees. Element. Attribute. Element with child elements. Double-clicking the element or the +/- symbol to its left causes the element to expand/collapse. DB Filter applied. Applies only to top-level data table elements in the schema tree. See also: Creating the SPS Structure | Schema Sources , for more information on schema selection and root elements. Design Treeentry helper window Namespacesoverview of Parametersoverview of user-defined parameters Schema sourcesoverview of Scriptsoverview of Templatestree of Layout (Enterprise Edition)creation of cover, headers, footers Cover (Enterprise Edition)creation of Headers (Enterprise Edition)creation of Footers (Enterprise Edition)creation of

Design Tree

The Design Tree window ( screenshot below ) provides an overview of the SPS design. At the root of the Design Tree is the location of the SPS file. The next level is organized into the following categories:

Namespaces, which displays all the namespaces declared in the SPS .

Parameters, which enables the Edit Parameters dialog to be displayed. In the Edit Parameters dialog, you can declare and edit user-defined parameters for the SPS and their default values.

Schema sources , which lists the schema /s on which the SPS is is/are based, and its its/their location /s .

Scripts , which shows all the JavaScript functions that have been defined for the SPS using the JavaScript Editor of StyleVision .

Main Template , which displays a detailed structure of the main template.

Global Templates , which gives a detailed graph of all the global templates in the SPS , including the main template.

Named Templates , which shows all the named templates in the design, and their structures.

Layout , which enables you to customize HTML and print layout items such as headers and footers .

Modifying the Design Tree display The display of the Design Tree can be modified via the context menu ( screenshot below ), which pops up on right-clicking an item in the Design Tree. A description of these commands is given in the following table.

Add	Enables page layout items to be added to the Layout category.
Remove (Item)	Applies to certain categories such as Global Templates. Removes the selected item from the Design Tree.
Expand All	Expands all expandable items in all categories of the Design Tree.
Collapse All	Collapses the entire Design Tree to the top-level item, which is the location of the SPS file.
Expand from This Point	Expands all expandable items in the selected item.
Collapse to This Point	Collapses all items within the selected item, up to the selected item.
Expand/Collapse All to This Level	Expands or collapses all categories to the level of the selected item.

Global Templates The Global Templates item lists all the global templates in the SPS . These templates are displayed as trees with expandable/collapsible nodes ( see screenshot below ). Any component in any of the template trees can be removed by selecting it and clicking the Remove button in the toolbar or the Remove command in the context menu. The component is removed from the design and the tree. Named Templates The Named Templates item lists all the named templates in the SPS . These templates are displayed as trees with expandable/collapsible nodes ( see screenshot below ). Any component in any of the template trees can be removed by selecting it and clicking the Remove button in the toolbar or the Remove command in the context menu. The component is removed from the design and the tree. Layout The Layout item lists the cover page, header, and footer templates for printed media output. These can be added via the context menu, where these options are items of the Add submenu. See Designing Print Output for details of how to create these layout items. In the Design Tree entry helper, layout items can be removed by selecting it and clicking the Remove button in the toolbar or the Remove command in the context menu. The component is removed from the design and the tree. The Layout item enables you to set the title of the HTML page and hyperlink properties. These settings are made in the Properties entry helper when Layout is selected in the Design Tree entry helper. Toolbar icons The following toolbar icons are shortcuts for common Schema Sources entry helper commands.

	Adds a named template or layout item to the design. Clicking the left-hand part of the icon adds a named template. Clicking the dropdown arrow drops down a list with commands to add a named template or any of various layout items.
	Remove the selected item; icon is active when item in the Global Templates or Layout sub-trees is selected.
	Autocollapses items in the design tree.
	Synchronize tree toggle. When toggled on (icon has border), selecting a node in the tree selects (i) the corresponding node in the design, and (ii) the corresponding node in the Schema Sources tree if the Synchronize Tree icon in the Schema Sources tree is toggled on. When toggled off, the corresponding nodes in the design and Schema Sources tree are not selected.

See also: Parameters , for information about how to use parameters in an SPS . Schema Sources , for a description of the Schema Sources entry helper, where schema sources are added. Using Scripts , for information about using scripts in the SPS . Designing Print Output , for a description of how to define page properties and create page layout items. Style Repositoryentry helper window Stylesprecedence of Precedenceof styles

Style Repository

In the Style Repository window ( screenshot below ), you can assign external CSS stylesheets and define global CSS styles for the SPS . Style rules in external CSS stylesheets and globally defined CSS styles are applied to Authentic View and the HTML output document. Note that for RTF and PDF output, styles applied to certain selectors will be discarded (see Defining CSS Styles Globally for details) ; these rules are identified in the Style Repository ( see screenshot below ). The Style Repository window contains two listings, External and Global , each in the form of a tree. The External listing contains a list of external CSS stylesheets associated with the SPS . The Global listing contains a list of all the global styles associated with the SPS . The structure of the listings in the Style Repository is as follows: External - CSS-1.css  - Location of file (editable in Style Repository window)  - Media (can be defined in Style Repository window)  - Rules (non-editable; must be edited in CSS file)    - Selector-1      - Property-1      - ...      - Property-N    - ...    - Selector-N + ... + CSS-N.css Global - Selector-1  + Selector-1 Properties - ... + Selector-N Precedence of style rules If a global style rule and a style rule in an external CSS stylesheet have selectors that identify the same document component, then the global style rule has precedence over that in the external stylesheet, and will be applied. If two or more global style rules select the same document component, then the rule that is listed last from among these rules will be applied. Likewise, if two or more style rules in the external stylesheets select the same document component, then the last of these rules in the last of the containing stylesheets will be applied Managing styles in the Style Repository In the Style Repository window you can do the following, using either the icons in the toolbar and/or items in the context menu: Add:  The Add icon adds a new external stylesheet entry to the External tree or a new global style entry to the Global tree, respectively, according to whether the External or Global tree was selected. The new entry is appended to the list of already existing entries in the tree. The Add command is also available in the context menu. For more details about using external stylesheets and global styles, see Working with CSS Styles . Insert: The Insert icon inserts a new external stylesheet entry above the selected external stylesheet (in the External tree) or a new global style entry above the selected global style (in the Global tree). The Insert command is also available in the context menu. For more details about using external stylesheets and global styles, see Working with CSS Styles . Move Up/Down: The Move Up icon and Move Down icon move the selected external stylesheet or global style respectively up and down relative to the other entries in its  tree. These commands are useful for changing the priority of external stylesheets relative to each other and of global style rules relative to each other. The Move Up and Move Down commands are also available in the context menu. For more details about how to change the precedence of styles, see Working with CSS Styles . Views of global style properties: The properties of a global style can be displayed in one of three views: (i) by property group; (ii) all properties sorted alphabetically; (iii) properties with values defined, sorted alphabetically. The view can be changed for each style individually. To change the properties view of a global style, select that style and click one of the View icons in the Style Repository toolbar: Grouped ; List All ; and List Non-Empty . These commands are also available in the context menu under the View Mode item. Toggle Important: Clicking the Toggle Important icon sets the CSS value !important on or off for the selected CSS rule. Reload All: The Reload All icon reloads all the external CSS stylesheets. Reset: The Reset icon deletes the selected external stylesheet or global style. Expand/Collapse All: All expandable items in both the External and Global trees can be expanded and collapsed with one click using the Expand All and Collapse All commands in the context menu, respectively. Editing CSS styles in the Style Repository The following editing mechanisms are provided in the Style Repository:

You can replace an assigned CSS Stylesheet with another CSS stylesheet, and you can specify the media to which each external CSS stylesheet applies. How to do this is explained in the section External CSS Stylesheets .

Global styles can have their selectors and properties directly edited in the Style Repository window. How this is done is described in the section Defining CSS Styles Globally .

See also: Working with CSS Styles , for a complete description of how to work with CSS styles and how to use the Styles Entry Helper to define CSS styles locally on components. Styles Entry Helper , for a description of how to use the Styles Entry Helper. Stylesentry helper window defining and property groups CSS stylessee also Styles

Styles

The Styles window ( screenshot below ) enables CSS styles to be defined locally for SPS components selected in the Design View. The Styles window is divided into two broad parts:

The Styles For column , in which the selected component types are listed. One of these component types may be selected at a time for styling. (In the screenshot above, the 1 text component is selected.) For detailed information about the selection of component types, see Selecting SPS Components to Style .

The Property Definitions column , in which CSS properties are defined for the component type/s selected in the Styles For column. The Property Definitions column can be displayed in three views ( see below ). For the details of how to set local property definitions, see Setting CSS Property Values . The XPath icon toggles on and off the application of XPath expressions as the source of property values. With a property selected, if the XPath icon is toggled on, then an XPath expression can be entered for this property and the return value of the XPath expression is used as the value of that property. In this way, the value of a node in an XML document can be returned, at runtime, as the value of a property. When the XPath icon is toggled off, a static value can be entered as the value of the property.

Toggle Important and Reset toolbar icons Clicking the Toggle Important icon sets the CSS value !important on or off for the selected CSS rule. Clicking the Reset icon resets the value of the selected property. See also: Working with CSS Styles , for a complete description of how to work with CSS styles and how to use the Styles Entry Helper to define CSS styles locally on components Style Repository , for information about working with external CSS stylesheets and global styles . Predefined Formats , for a description of how to use predefined HTML formats in the SPS . Propertiesentry helper window defining and property groups

Properties

The Properties window ( screenshot below ) enables properties to be defined for SPS components selected in the Design View. The Properties window is divided into two broad parts:

The Properties For column , in which the selected component types are listed. One of these component types may be selected at a time and properties assigned for it. (In the screenshot above, the paragraph component is selected.) For detailed information about how components with properties are grouped, see the section Components and their Property Groups below.

The Property Definitions column , in which component properties are defined for the component type selected in the Properties For column. The Property Definitions column can be displayed in three views ( see below ). For the details of what properties are in each property group, see the section Property Groups below .

Reset toolbar icon Clicking the Reset icon resets the value of the selected property to its default. Components and their property groups The availability of property groups is context-sensitive. What property groups are available depends on what design component is selected. The table below lists SPS components and the property groups they have.

Component	Property Group
Template	Authentic
Content	Authentic; Common; Event
Text	Authentic; Common; Event
Auto-Calculation	Authentic; Common; Event
Condition Branch	Authentic
Data-Entry Device	Authentic; Common; [Data-Entry Device]; Event; HTML
Image	Authentic; Common; Event; HTML
Link	Authentic; Common; Event; HTML
Table	Authentic; Common; Event; HTML
Paragraph	Authentic; Common; Event; HTML

Component	Property Group
Content	Common; Event
Text	Common; Event
Auto-Calculation	Common; Event
Data-Entry Device	Common; [Data-Entry Device]; Event; HTML
Image	Common; Event; HTML
Link	Common; Event; HTML
Table	Common; Event; HTML
Paragraph	Common; Event; HTML

The following points about component types should be noted:

Template components are the main template, global templates, and all schema nodes in the design.

Content components are the content and rest-of-contents placeholders. These represent the text content of a node or nodes from the XML document.

A text component is a single string of static text. A single string extends between any two components other than text components, and includes whitespace, if any is present.

Data-entry devices are input field, multiline input fields, combo boxes, check boxes, radio buttons and buttons; their properties cover the data-entry device as well as the contents of the data-entry device, if any.

A table component refers to the table structure in the design. Note that it contains sub-components, which are considered components in their own right. The sub-components are: row, column, cell, header, and footer.

A paragraph component is any predefined format.

The table below contains descriptions of each property group.

Property Group	Description
Authentic	These are SPS -specific properties that are available for all component types. What properties within the group are available are component-specific. For example, when an Auto-Calculation is selected, the XPath property contains the XPath expression that determines the value of the Auto-Calculation, and the Format property enables you to define Input Formatting for the result of the Auto-Calculation. Similarly, when the contents placeholder is selected, if the datatype of the node is a numeric datatype, then the Format property is available; it is not available if the node datatype is non-numeric.
Common	The Common property group is available for all component types except the Template component type. It contains the following properties: class , dir , id , lang , and title . Values for these properties can be selected using XPath expressions.
Data-Entry Device	Specifies the value range of combo boxes, check boxes, and radio buttons. Note that this property group does not apply to input fields and buttons.
Event	Contains properties that enable JavaScript functions to be defined for the following client-side HTML events: onclick , ondblclick , onkeydown , onkeypressed , onkeyup , onmousedown , onmousemove , onmouseout , onmouseover , onmouseup .
HTML	Available for the following component types: data-entry devices ; image ; link ; table ; paragraphs . Note that there are different types of data-entry devices and paragraphs , and that tables have sub-components. These properties are HTML properties that can be set on the corresponding HTML elements ( img , table , p , div , etc). The available properties therefore vary according to the component selected. Values for these properties can be selected using XPath expressions.

Property Group	Description
Common	The Common property group is available for all component types except the Template component type. It contains the following properties: class , dir , id , lang , and title . Values for these properties can be selected using XPath expressions.
Data-Entry Device	Specifies the value range of combo boxes, check boxes, and radio buttons. Note that this property group does not apply to input fields and buttons.
Event	Contains properties that enable JavaScript functions to be defined for the following client-side HTML events: onclick , ondblclick , onkeydown , onkeypressed , onkeyup , onmousedown , onmousemove , onmouseout , onmouseover , onmouseup .
HTML	Available for the following component types: data-entry devices ; image ; link ; table ; paragraphs . Note that there are different types of data-entry devices and paragraphs , and that tables have sub-components. These properties are HTML properties that can be set on the corresponding HTML elements ( img , table , p , div , etc). The available properties therefore vary according to the component selected. Values for these properties can be selected using XPath expressions.

Setting property values Property values can be entered in one, two, or three ways, depending on the property ( see screenshot below ) :

Entered directly in the Value column. To do this, select a property, double-click in its Value column, enter the value using the keyboard, and press Enter or click anywhere in the GUI.

By selecting a value from the dropdown list of the combo box for that property. Click the down arrow of the combo box to drop down the list of property-value options.

By using the Edit button at the right-hand side of the Value column for that property. Clicking the Edit button pops up a dialog relevant to that property. For example, the entry helper for the Format property in the screenshot below pops up the Input Formatting dialog, while that for the XPath property pops up the Edit XPath Expression dialog.

For some properties, in the Common and HTML groups of properties, XPath expressions can be used to provide the values of the property. The XPath icon toggles on and off the application of XPath expressions as the source of property values. With a property selected, if the XPath icon is toggled on, then an XPath expression can be entered for this property and the return value of the XPath expression is used as the value of that property. In this way, the value of a node in an XML document can be returned, at runtime, as the value of a property. When the XPath icon is toggled off, a static value can be entered as the value of the property. Modifying or deleting a property value To modify a property value, use any of the applicable methods described in the previous paragraph, Setting Property Values . To delete a property value, select the property and click the Reset icon in the toolbar of the Properties entry helper. See also: Styles , for a description of how styles can be assigned to the selected component.