Features that are new in StyleVision Version 2010 Release 3 are listed below.
|•||Value Formatting (Formatting Numeric Datatypes): The earlier Input Formatting mechanism has been extended to enable—only in the Enterprise Edition—the formatting of Inline XBRL values when they are output in an (X)HTML report. The older Input Formatting feature remains unchanged but has been renamed to Value Formatting.|
|•||Inline XBRL: The SPS design can generate Inline XBRL elements in the (X)HTML output. These Inline XBRL elements can subsequently be extracted by an external processor that generates valid XBRL documents from (X)HTML documents.|
|•||Global templates can now be created for any node or type in the schema. In earlier versions of StyleVision, global templates could only be created for global elements and global types. They can now be created on any node or type, and even for any item returned by an XPath expression. |
|•||Integration in Microsoft Visual Studio 2010. This extends support to the latest version of Visual Studio, which is in addition to support for versions 2005 and 2008. Support for Visual Studio 2003 has been discontinued.|
Features that are new in StyleVision Version 2010 Release 2 are listed below.
|•||Enterprise and Professional editions are each available as separate 64-bit and 32-bit applications.|
|•||Parameters for Design Fragments allow design fragments to be used with different parameter values for each usage instance. A different parameter value can be assigned to a design fragment at each location where the design fragment is used in the SPS.|
|•||First and last page headers and footers can be specified separately. This is in addition to different headers and footer for odd-numbered and even-numbered pages and for different document sections.|
Features that are new in StyleVision Version 2010 Release 1 are listed below. Some of these new features have required a modification in the way older features are handled. In such cases, the existing feature continues to behave as before, but uses one or more of the newer mechanisms. The way a new feature affects existing features is noted in the list below.
|•||Layout Containers: A Layout Container is a block in which Design Elements can be laid out and absolutely positioned within the block.|
|•||Blueprints: Within a Layout Container an image of a form can be used as an underlay blueprint for the design. With the help of a blueprint, an existing design can be reproduced accurately.|
|•||Document Sections: Documents can be divided into sections, with each section having its own properties, such as page layout properties. This enables different parts of a document to be presented differently. Older features affected: Previous designs had no sections. These designs will now be created as documents with one section, the Initial Document Section. Page properties and page layout properties, which were previously specified for the document as a whole, are now specified for the Initial Document Section. The cover page for print output of previous versions will be created in the new version as a template within the Initial Document Section. |
|•||User-Defined Templates: A template can be generated for a sequence of items by an XPath expression you specify. These items may be atomic values or nodes. An XPath expression enables the selection of nodes to be more specific, allowing conditions and filters to be used for the selection. Furthermore, templates can be built for atomic values, thus enabling structures to be built that are independent of the schema structure. Older features affected: Variable Iterators, which were used to create a template for a variable, now create a variable on a node template and then a User-Defined template for that variable. |
|•||User-Defined Elements: This feature is intended to enable presentation language elements (such as HTML, XSLT, and XSL-FO) to be freely inserted at any location in the design.|
|•||User-Defined XML Text Blocks: XML Text blocks can be freely inserted at any location in the design, and these blocks will be created at that location in the generated XSLT stylesheet.|
|•||XSLT Templates: XSLT files can be imported into the generated stylesheets. If a node in the XML instance document is matched to a template in the imported XSLT file and no other template takes precedence over the imported template, then the imported template will be used. Additionally, named templates in the imported XSLT file can be called from within the design.|
|•||Variables: A variable can now be declared on a template and take a value that is specified with an XPath expression. Previously, the value of a variable was limited to the selection of the node on which it was created. Variables in the 2010 version allow any XPath expression to be specified as the value of the variable. Older features affected: Variables and Variable Iterators. Variables from older versions are now created on the relevant template and are given a value that selects the same template. Variable Iterators are replaced with a combination of a Variable and a User-Defined Template; see User-Defined Templates below.|
|•||Inserting Design Elements: Design Elements (paragraphs, lists, images, etc) can be inserted first, and an XML node from the schema tree assigned to the Design Element afterwards. This is in addition to the existing mechanism by which a schema nodes is dragged into the design and a Design Element created for it.|
|•||Disable output escaping: A setting that defines whether text output will be escaped or not. A character is said to be escaped when it is written as a character entity (such as & or A). This feature is useful when outputting text that contains program code.|
|•||Pixel Resolution: Pixel length units in the SPS are converted to absolute units for print output according to a factor that the SPS designer specifies.|
|•||XHTML output: When XHTML is specified as the HTML output preference in the document's properties (File | Properties), an XHTML document is generated for the HTML output.|
© 2019 Altova GmbH