You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-commits@xmlgraphics.apache.org by vm...@apache.org on 2003/04/01 19:26:51 UTC
cvs commit: xml-fop/src/documentation/content/xdocs/design architecture.xml
vmote 2003/04/01 09:26:51
Modified: src/documentation/content/xdocs/design architecture.xml
Log:
add comments that cover the maintenance branch
Revision Changes Path
1.6 +2 -3 xml-fop/src/documentation/content/xdocs/design/architecture.xml
Index: architecture.xml
===================================================================
RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/design/architecture.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- architecture.xml 24 Mar 2003 22:22:40 -0000 1.5
+++ architecture.xml 1 Apr 2003 17:26:50 -0000 1.6
@@ -10,7 +10,7 @@
</authors>
</header>
<body>
- <p>The purpose of this document is to tie together the FOP design (interface) with some of the key points where control is passed within FOP (implementation), so that developers can quickly find the section of code that is relevant to their needs. The process described is for a "typical" command-line document. All class names are in org.apache.fop unless otherwise designated.</p>
+ <p>The purpose of this document is to tie together the FOP design (interface) with some of the key points where control is passed within FOP (implementation), so that developers can quickly find the section of code that is relevant to their needs. The process described is for a "typical" command-line document. All classes are in org.apache.fop unless otherwise designated.</p>
<section>
<title>Overview</title>
<p>The input FO document is sent to the FO tree builder via SAX events. Fragments of an FO Tree are built from this process. As each page-sequence element is completed, it is passed to a layout processor, which in turn converts it into an Area Tree. The Area Tree is then given to the Renderer, which converts it into a stream of data containing the output document. The sections below will provide additional details.</p>
@@ -27,8 +27,7 @@
<title>Formatting Object Tree</title>
<ul>
<li>The SAX events that the parser creates are handled by <em>fo.FOTreeBuilder</em>, which uses <code>startElement()</code>, <code>endElement()</code>, and <code>characters()</code> methods to build the FO Tree.</li>
- <li><em>fo.FOTreeBuilder.endElement()</em> runs the end() method for each node as it is created. The <em>fo.pagination.PageSequence</em> class overrides this end() method to run <em>apps.LayoutHandler.endPageSequence()</em>.</li>
- <li><em>apps.LayoutHandler.endPageSequence()</em> in turn runs <em>fo.pagination.PageSequence.format()</em>, which drives the layout process.</li>
+ <li>In the trunk, <em>fo.FOTreeBuilder.endElement()</em> runs the end() method for each node as it is created. The <em>fo.pagination.PageSequence</em> class overrides this end() method to run <em>apps.LayoutHandler.endPageSequence()</em>, which in turn runs <em>fo.pagination.PageSequence.format()</em>. In the maintenance branch, the end of a PageSequence element causes the PageSequence object to be passed to <em>apps.StreamRenderer.render</em>, which in turn runs fo.pagination.PageSequence.format. In both cases, the layout process is then driven from <em>fo.pagination.PageSequence.format</em>.</li>
</ul>
</section>
<section>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-cvs-help@xml.apache.org