Conventions | NetBeansв„ў IDE Field Guide: Developing Desktop, Web, Enterprise, and Mobile Applications (2nd Edition)

To help you get the most from the text and keep track of what's happening, we've used a number of conventions throughout the book.

Worked examples-which you can download and try out for yourself- generally appear in a box like this:

A Specimen Example

Source

This section gives the XML source data, the input to the transformation. If the file name is given as example.xml , you will find that file in the archive that you can download from the Wrox Web site at http://www.wrox.com/ , generally in a subdirectory holding all the examples for one chapter.

  <source data="xml"/>

Stylesheet

This section describes the XSLT stylesheet used to achieve the transformation. Again, there will usually be a filename such as style.xsl so you can find the stylesheet in the Wrox download archive.

  <xsl:stylesheet...

Output

This section shows the output when you apply this stylesheet to this source data, either as an XML or HTML listing, or as a screenshot.

  <html...</html>

There are some further typographical conventions:

Important

Elements like this one hold important, not-to-be forgotten information that is directly relevant to the surrounding text.

Tips, hints, tricks, and asides to the current discussion are offset and placed in italic like this .

As for styles in the text:

We highlight important words when we introduce them.
We show keyboard strokes like this: Ctrl+A.
We show code within the text as follows . Element names are written as <html> or <xsl:stylesheet> . Function names are written as concat() or current-date () . Other names (for example of attributes or types) are written simply as version or xs:string . Fragments of code other than simple names are offset from the surrounding text by chevrons, for example «substring ($a, 1, 1) = 'X' » . Chevrons are also used around individual characters or string values: as a general rule, if a string is enclosed in quotation marks, then the quotes are part of the code example, whereas if it is enclosed in chevrons, the chevrons are there only to separate the code from the surrounding text.

Blocks of code are shown as follows:

  In examples we highlight code with a gray background.