<body>
<section>
<title>Area Tree</title>
-<section>
- <title>Area Tree</title>
<p>The Area Tree is an internal representation of the result document. This
is a set of java classes that can put together a set of objects that
represent the pages and their contents.</p>
of page sequences.</p>
</section>
- </section>
-
</body>
</document>
</header>
<body>
-<section>
- <title>FO Tree</title>
<p>
The FO Tree is a representation of the XSL:FO document. This
represents the <strong>Objectify</strong> step from the
</p>
</section>
-</section>
-
</body>
</document>
<title>Layout Managers</title>
</header>
<body>
-<section>
- <title>Layout Managers</title>
-
<p>The role of the layout managers is to build the Area Tree by using the
information from the FO Tree. The layout managers decide where information
is placed in the area tree.</p>
the flow.</p>
<p>A layout manager handles the adding and removing of footnotes/floats, this in turn effects the available space in the main reference area.</p>
-</section>
</section>
</body>
</header>
<body>
-<section>
- <title>Property Handling</title>
<p>During XML Parsing, the FO tree is constructed. For each FO object (some
subclass of FObj), the tree builder then passes the list of all
attributes specified on the FO element to the handleAttrs method. This
returned.</p>
</section>
-</section>
</body>
</document>
<section>
<title>Renderers</title>
-<section>
- <title>Renderers</title>
-
<p>A renderer is used to convert the Area Tree into the output document.
The renderer is given the tree one page at a time. All pages are supplied
in the order they appear in the document. In order to save memory it is
If two renderers have the same font metrics then it is possible to render
the Area Tree in each renderer. This can be handled by the AreaTree
Handler.</p>
-</section>
-
</section>
</body>