1.1 | An XSLT transformation, controlled by a stylesheet, converts an XML source of a page into HTML which is then displayed by the browser | 11 |
1.2 | A variation of Figure 1.1: Instead of HTML, a combination of presentation-oriented XML and a CSS style sheet renders the page in a browser | 12 |
1.3 | XML offline: XSLT transformation is done in the authoring environment, while the web server and web client both deal with HTML pages | 20 |
1.4 | XML on the server: XSLT transformation is done on the web server; a client receives an HTML page | 22 |
1.5 | XML in the browser: XSLT transformation is done in a web client | 25 |
1.6 | A simple dynamic web page: Note that while some of the atomic dynamic values are drawn from the database, others may be calculated by the page's embedded script | 30 |
1.7 | A more complex dynamic web page: The program code is removed from the template, and the template is constructed from separate fragments . | 31 |
1.8 | Incorporating XML/XSLT into a dynamic web site: "Compile, then transform" | 33 |
1.9 | Another way to combine XML/XSLT with a dynamic engine: "Transform, then compile." Composite dynamic values are best avoided in this scenario | 37 |
2.1 | The page documents and the master document are fed to the transformation stylesheet that produces HTML pages | 50 |
5.1 | The Batik-rasterized version of Example 5.14. The image is magnified to demonstrate anti-aliasing; the actual size is approximately 400 by 60 pixels | 244 |
5.2 | Drop shadow added to Figure 5.1 by Imagemagick | 245 |
5.3 | The result of transforming the page document from Example 3.1 with the stylesheet from Example 5.21, using Example 3.2 as master document and Example 5.19 as shared library | 266 |
6.1 | XEmacs: Editing an XSLT stylesheet with generic XML editing commands | 289 |
6.2 | <oXygen/> XML editor: Project view, document source, and an XPath expression | 291 |
6.3 | <oXygen/> XML editor: The tree view of an XML document and an XPath expression. The information in the panes at right (the current element's content model, lists of all defined elements and entities) comes from the DTD, which in this case was generated automatically by the program from a sample document | 294 |
6.4 | Pollo XML editor: Tree-like view with " frames " representing elements. Lists of allowed element types in the panes at right implement guided editing based on a DTD or an XSDL schema. An XPath expression highlights the first match and lets you scroll the list of all matches | 296 |
6.5 | Morphon: Editable CSS-controlled presentation of an XML document. Icon tags let you see what element you are editing, but they can be turned off for a pure word-processor-like interface | 298 |
6.6 | X-Smiles: Editing a subset of master document with an XForms interface from Example 6.1 | 306 |
6.7 | A "legend" XML document using most of the element types defined for the page documents, rendered by Mozilla with the CSS style sheet from Example 6.2 | 316 |
6.8 | XPath Explorer focuses on one thingevaluating XPath expressions on a documentbut does that really well | 334 |
6.9 | An XSLT-process session in XEmacs; from top to bottom: source, stylesheet (both with breakpoints highlighted), messages, debugging console, and output; the sidebar (right) lists breakpoints, execution context, and variables at the current breakpoint | 343 |
6.10 | catchXSL!, an XSLT profiler, displays execution timings for each instruction in a stylesheet | 345 |