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/05/05 07:08:48 UTC
cvs commit: xml-fop/src/documentation/content/xdocs/design properties.xml
vmote 2003/05/04 22:08:48
Modified: src/documentation/content/xdocs/design properties.xml
Log:
Fix typos. Expand "Refinement" sections a bit. Move "Implementation Notes" to the content areas.
Revision Changes Path
1.12 +7 -9 xml-fop/src/documentation/content/xdocs/design/properties.xml
Index: properties.xml
===================================================================
RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/design/properties.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- properties.xml 1 May 2003 19:20:37 -0000 1.11
+++ properties.xml 5 May 2003 05:08:48 -0000 1.12
@@ -43,7 +43,7 @@
<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 PLB handles loops through each attribute in the list, finds an appropriate "Maker" for it, then calls the Maker to convert the attribute value into a Property object of the correct type, and stores that Property in the PropertyList.</p>
+ <p>The PLB loops through each attribute in the list, finds an appropriate "Maker" for it, then calls the Maker to convert the attribute value into a Property object of the correct type, and stores that Property in the PropertyList.</p>
</section>
<section id="datatypes">
<title>Property datatypes</title>
@@ -174,7 +174,10 @@
returned.</p>
</section>
<section id="property-spec">
- <title>XML property specification format</title>
+ <title>Implementing Standard Properties</title>
+ <p>Because the properties defined in the standard are basically static, FOP currently builds the source code for the related Property classes from an XML data file.
+All properties are specified in src/codegen/foproperties.xml.
+The related classes are created automatically during the build process by applying an XSLT stylesheet to the foproperties.xml file.</p>
<section id="generic">
<title>Generic properties</title>
<p>In the properties xml files, one can define generic property
@@ -350,16 +353,11 @@
</section>
<section id="refine">
<title>Refinement</title>
- <p>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 <strong>Refinement</strong> step is part of reading and using the properties which may happen immediately or during the layout process. FOP does not currently use a separate Refinement process, but tends to handle refining steps as the FO Tree is built.</p>
</section>
<section id="refined-fo-tree">
<title>Refined FO Tree</title>
+ <p>The Refined FO Tree is the result of the Refinement process.</p>
</section>
- <section id="implement">
- <title>Implementation Notes</title>
- </section>
- <p>All properties are specified in src/codegen/foproperties.xml.
-The related classes are created automatically during the build process.</p>
- <p>The base class for all properties is <em>fo.Property</em>, and the base class for all the property makers is the inner class <em>Property.Maker</em>.</p>
</body>
</document>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-cvs-help@xml.apache.org