diff options
| author | William Victor Mote <vmote@apache.org> | 2003-04-22 04:59:56 +0000 |
|---|---|---|
| committer | William Victor Mote <vmote@apache.org> | 2003-04-22 04:59:56 +0000 |
| commit | 92ba5cac5a2184595d0bd331df21294f1b751032 (patch) | |
| tree | e06685690ffc2fdea04a1f61c56ae07b6dbf870b | |
| parent | 66b2081c6f309d940e7dd212fc0570d5aabfe0ba (diff) | |
| download | xmlgraphics-fop-92ba5cac5a2184595d0bd331df21294f1b751032.tar.gz xmlgraphics-fop-92ba5cac5a2184595d0bd331df21294f1b751032.zip | |
Pretty-print & white-space changes only.
git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@196313 13f79535-47bb-0310-9956-ffa450edef68
| -rw-r--r-- | src/documentation/content/xdocs/design/fotree.xml | 259 |
1 files changed, 97 insertions, 162 deletions
diff --git a/src/documentation/content/xdocs/design/fotree.xml b/src/documentation/content/xdocs/design/fotree.xml index f277a406f..b4c94bc89 100644 --- a/src/documentation/content/xdocs/design/fotree.xml +++ b/src/documentation/content/xdocs/design/fotree.xml @@ -1,108 +1,71 @@ <?xml version="1.0" standalone="no"?> <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd"> - <document> - <header> - <title>FO Tree</title> - <subtitle>Design of FO Tree Structure</subtitle> - <authors> - <person name="Keiron Liddle" email="keiron@aftexsw.com"/> - </authors> - </header> - - <body> -<section> - <title>Introduction</title> -<p> -The FO Tree is an internal representation of the input XSL-FO document. + <header> + <title>FO Tree</title> + <subtitle>Design of FO Tree Structure</subtitle> + <authors> + <person name="Keiron Liddle" email="keiron@aftexsw.com"/> + </authors> + </header> + <body> + <section> + <title>Introduction</title> + <p>The FO Tree is an internal representation of the input XSL-FO document. The tree is created by building the elements and attributes from the SAX events. The process of building the FO Tree corresponds to the <strong>Objectify</strong> step from the spec. -The <strong>Refinement</strong> step is part of reading and using the properties which may happen immediately or during the layout process. - - </p> - <p> -The FO Tree is used as an intermediatory structure which is converted +The <strong>Refinement</strong> step is part of reading and using the properties which may happen immediately or during the layout process.</p> + <p>The FO Tree is used as an intermediatory structure which is converted into the area tree. The complete FO tree should not be held in memory -since FOP should be able to handle FO documents of any size. - </p> - <p> - The FO Tree is simply a heirarchy of java objects that - represent the fo elements from xml. The traversal is done by - the layout or structure process only in the flow elements. - </p> - -<section> - <title>FONode</title> -<p>The base class for all objects in the tree is FONode. The base class for +since FOP should be able to handle FO documents of any size.</p> + <p>The FO Tree is simply a heirarchy of java objects that represent the fo elements from xml. +The traversal is done by the layout or structure process only in the flow elements.</p> + <section> + <title>FONode</title> + <p>The base class for all objects in the tree is FONode. The base class for all FO Objects is FObj.</p> - -<p> -The class inheritance described above only describes the nature of the + <p>The class inheritance described above only describes the nature of the content. Every FO in FOP also has a parent, and a Vector of children. The parent attribute (in the Java sense), in particular, is used to enforce -constraints required by the FO hierarchy. -</p> - -<p> -FONode, among other things, ensures that FO's have a parent and that they -may have children. -</p> -<p>Each xml element is represented by a java object. For pagination the +constraints required by the FO hierarchy.</p> + <p>FONode, among other things, ensures that FO's have a parent and that they +may have children.</p> + <p>Each xml element is represented by a java object. For pagination the classes are in <code>org.apache.fop.fo.pagination.*</code>, for elements in the flow they are in <code>org.apache.fop.fo.flow.*</code> and some others are in <code>org.apache.fop.fo.*.</code></p> - -</section> - -<section> - <title>Making FO's</title> -<p>There is a class for each element in the FO set. An object is created for + </section> + <section> + <title>Making FO's</title> + <p>There is a class for each element in the FO set. An object is created for each element in the FO Tree. This object holds the properties for the FO Object.</p> -<p>Some validity checking is done during these steps. The user can be warned of the error and processing can continue if possible. -</p> - <p> - When the object is created it is setup. It is given its - element name, the FOUserAgent - for resolving properties - etc. - the logger and the attributes. The methods - <code>handleAttributes()</code> and - <code>setuserAgent()</code>, common to <code>FONode</code>, - are used in this process. The object will then be given any - text data or child elements. Then the <code>end()</code> - method is called. The end method is used by a number of - elements to indicate that it can do certain processing since - all the children have been added. - </p> - -<p> -An FO maker is read from a hashmap lookup using the namespace and + <p>Some validity checking is done during these steps. The user can be warned of the error and processing can continue if possible.</p> + <p>When the object is created it is setup. +It is given its element name, the FOUserAgent - for resolving properties etc. - the logger and the attributes. +The methods <code>handleAttributes()</code> and <code>setuserAgent()</code>, common to <code>FONode</code>, are used in this process. +The object will then be given any text data or child elements. +Then the <code>end()</code> method is called. +The end method is used by a number of elements to indicate that it can do certain processing since all the children have been added.</p> + <p>An FO maker is read from a hashmap lookup using the namespace and element name. This maker is then used to create a new class that represents an FO element. This is then added to the FO tree as a child -of the current parent. -</p> -</section> - -<section> - <title>Properties</title> - -<p>The XML attributes on each element are passed to the object. The objects -that represent FO objects then convert the attributes into properties. -</p> - -<p>Since properties can be inherited the PropertyList class handles resolving +of the current parent.</p> + </section> + <section> + <title>Properties</title> + <p>The XML attributes on each element are passed to the object. The objects +that represent FO objects then convert the attributes into properties.</p> + <p>Since properties can be inherited the PropertyList class handles resolving properties for a particular element. All properties are specified in an XML file. Classes are created -automatically during the build process. -</p> - -<p>In some cases the element may be moved to have a different parent, for +automatically during the build process.</p> + <p>In some cases the element may be moved to have a different parent, for example markers, or the inheritance could be different, for example initial property set.</p> -</section> - -<p> -Properties (recall that FO's have properties, areas have traits, and XML + </section> + <p>Properties (recall that FO's have properties, areas have traits, and XML nodes have attributes) are also a concern of <em>FOTreeBuilder</em>. It accomplishes this by using a <em>PropertyListBuilder</em>. There is a separate <em>PropertyListBuilder</em> for each namespace encountered @@ -112,101 +75,73 @@ contain element-specific property maker hashes; these are based on the <em>local name</em> of the flow object, ie. <em>table-row</em>, not <em>fo:table-row</em>. If an element-specific property mapping exists, it is preferred to the generic mapping.</p> -<p>The base class for all + <p>The base class for all properties is <em>Property</em>, and all the property makers extend <em>Property.Maker</em>. A more complete discussion of the property -architecture may be found in <jump href="properties.html">Properties</jump>. -</p> -</section> - -<section> - <title>Foreign XML</title> -<p> -FOP supports the handlingof foreign XML. +architecture may be found in <jump href="properties.html">Properties</jump>.</p> + </section> + <section> + <title>Foreign XML</title> + <p>FOP supports the handlingof foreign XML. The XML is converted internally into a DOM, this is then available to the FO tree to convert the DOM into another format which can be rendered. In the case of SVG the DOM needs to be created with Batik, so an element mapping is used to read all elements in the SVG namespace and pass them -into the Batik DOM. -</p> -</section> - -<section> - <title>Extensions</title> -<p> -It is possible to add extensions to FOP so that you can extend the ability of +into the Batik DOM.</p> + </section> + <section> + <title>Extensions</title> + <p>It is possible to add extensions to FOP so that you can extend the ability of FOP with respect to render output, document specific information or extended -layout functionality. -</p> -</section> - -<section> - <title>Foreign XML</title> - -<p>The base class for foreign XML is XMLObj. This class handles creating a +layout functionality.</p> + </section> + <section> + <title>Foreign XML</title> + <p>The base class for foreign XML is XMLObj. This class handles creating a DOM Element and the setting of attributes. It also can create a DOM Document if it is a top level element, class XMLElement. This class must be extended for the namespace of the XML elements. For unknown namespaces the class is UnknowXMLObj.</p> - -<p>If some special processing is needed then the top level element can extend + <p>If some special processing is needed then the top level element can extend the XMLObj. For example the SVGElement makes the special DOM required for -batik and gets the size of the svg. -</p> - -<p>Foreign XML will usually be in an fo:instream-foreign-object, the XML will +batik and gets the size of the svg.</p> + <p>Foreign XML will usually be in an fo:instream-foreign-object, the XML will be passed to the render as a DOM where the render will be able to handle -it. Other XML from an unknwon namespace will be ignored. -</p> - -<p>By using element mappings it is possible to read other XML and either</p> -<ul><li>set information on the area tree</li> -<li>create pseudo FO Objects that create areas in the area tree</li> -<li>create FO Objects</li></ul> -</section> - -<section> - <title>Unknown Elements</title> -<p>If an element is in a known namespace but the element is unknown then an +it. Other XML from an unknwon namespace will be ignored.</p> + <p>By using element mappings it is possible to read other XML and either</p> + <ul> + <li>set information on the area tree</li> + <li>create pseudo FO Objects that create areas in the area tree</li> + <li>create FO Objects</li> + </ul> + </section> + <section> + <title>Unknown Elements</title> + <p>If an element is in a known namespace but the element is unknown then an Unknown object is created. This is mainly to provide information to the user. This could happen if the fo document contains an element from a different version or the element is misspelt.</p> -</section> - -<section> - <title>Page Masters</title> - <p> - The first elements in a document are the elements for the - page master setup. This is usually only a small number and - will be used throughout the document to create new pages. - These elements are kept as a factory to create the page and - appropriate regions whenever a new page is requested by the - layout. The objects in the FO Tree that represent these - elements are themselves the factory. The root element keeps - these objects as a factory for the page sequences. - </p> -</section> - -<section> - <title>Flow</title> -<p>The elements that are in the flow of the document are a set of elements + </section> + <section> + <title>Page Masters</title> + <p>The first elements in a document are the elements for the page master setup. +This is usually only a small number and will be used throughout the document to create new pages. +These elements are kept as a factory to create the page and appropriate regions whenever a new page is requested by the layout. +The objects in the FO Tree that represent these elements are themselves the factory. +The root element keeps these objects as a factory for the page sequences.</p> + </section> + <section> + <title>Flow</title> + <p>The elements that are in the flow of the document are a set of elements that is needed for the layout process. Each element is important in the creation of areas.</p> -</section> - -<section> - <title>Other Elements</title> - - <p> - The remaining FO Objects are things like page-sequence, - title and color-profile. These are handled by their parent - element; i.e. the root looks after the declarations and the - declarations maintains a list of colour profiles. The - page-sequences are direct descendents of root. - </p> - </section> - - </body> + </section> + <section> + <title>Other Elements</title> + <p>The remaining FO Objects are things like page-sequence, title and color-profile. +These are handled by their parent element; i.e. the root looks after the declarations and the declarations maintains a list of colour profiles. +The page-sequences are direct descendents of root.</p> + </section> + </body> </document> - |