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/07 06:58:53 UTC
cvs commit: xml-fop/src/documentation/content/xdocs/dev implement.xml
vmote 2003/04/06 21:58:52
Modified: src/documentation/content/xdocs/dev implement.xml
Log:
Fix table rows.
Revision Changes Path
1.2 +4 -2 xml-fop/src/documentation/content/xdocs/dev/implement.xml
Index: implement.xml
===================================================================
RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/dev/implement.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- implement.xml 7 Apr 2003 04:43:41 -0000 1.1
+++ implement.xml 7 Apr 2003 04:58:52 -0000 1.2
@@ -31,15 +31,17 @@
</tr>
<tr>
<td colspan="2">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.</td>
+ </tr>
+ <tr>
<td><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>.</td>
<td>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.</td>
</tr>
<tr>
- <td></td>
+ <td>.</td>
<td><em>fo.pagination.PageSequence.addFlow()</em> programatically adds a Flow object to the page sequence.</td>
</tr>
<tr>
- <td></td>
+ <td>.</td>
<td>fo.pagination.PageSequence.makePage() creates a BodyArea and passes it to <em>fo.Flow.layout</em></td>
</tr>
<tr>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-cvs-help@xml.apache.org