<p>The Area Tree retains the concept of page sequences (this is not in the area tree in the spec) so that this information can be passed to the renderer.
This is useful for setting the title and organising the groups of page sequences.</p>
</section>
+ <section id="status">
+ <title>Status</title>
+ <section id="status-todo">
+ <title>To Do</title>
+ </section>
+ <section id="status-wip">
+ <title>Work in Progress</title>
+ </section>
+ <section id="status-complete">
+ <title>Completed</title>
+ <ul>
+ <li>new area tree model</li>
+ <li>changed area tree xml format to match the area tree hierarchy</li>
+ </ul>
+ </section>
+ </section>
</body>
</document>
<menu-item label="Introduction" href="index.html"/>
</menu>
<menu label="Core Process">
+ <menu-item label="Startup" href="startup.html"/>
<menu-item label="XML Parsing" href="parsing.html"/>
<menu-item label="FO Tree" href="fotree.html"/>
<menu-item label="Properties" href="properties.html"/>
>>]]></source>
</section>
-
+ <section id="status">
+ <title>Status</title>
+ <section id="status-todo">
+ <title>To Do</title>
+ </section>
+ <section id="status-wip">
+ <title>Work In Progress</title>
+ <ul>
+ <li>mathml extension</li>
+ <li>another xml -> svg extension</li>
+ <li>svg text normal text if that can be handled otherwise stroked this is done automatically</li>
+ </ul>
+ </section>
+ <section id="status-complete">
+ <title>Completed</title>
+ <ul>
+ <li>svg now in an xml handler, FOP can be used without batik</li>
+ <li>bookmark extension improved a bit - changed bookmark extension, now requires a wrapping element bookmark</li>
+ </ul>
+ </section>
+ </section>
</body>
</document>
The areas are then placed on a last page.</p>
</section>
</section>
+ <section id="status">
+ <title>Status</title>
+ <section id="status-todo">
+ <title>To Do</title>
+ </section>
+ <section id="status-wip">
+ <title>Work in Progress</title>
+ <ul>
+ <li><strong>better layout design</strong> - that can handle keeps and spacing better</li>
+ <li><strong>better area tree handling</strong> - means it can run in less memory</li>
+ <li>new area tree model</li>
+ <li>changed area tree xml format to match the area tree hierarchy</li>
+ </ul>
+ </section>
+ <section id="status-complete">
+ <title>Completed</title>
+ </section>
+ </section>
</body>
</document>
<p>See <link href="../extensions.html">User Extensions</link> for a discussion of standard extensions shipped with FOP, and their related namespaces.</p>
<p>See <link href="../dev/extensions.html">Developer Extensions</link> for a discussion of the mechanisms in place to allow developers to add their own extensions, including how to tell FOP about the foreign namespace.</p>
</section>
+ <section id="status">
+ <title>Status</title>
+ <section id="status-todo">
+ <title>To Do</title>
+ </section>
+ <section id="status-wip">
+ <title>Work In Progress</title>
+ </section>
+ <section id="status-complete">
+ <title>Completed</title>
+ <ul>
+ <li>better handling of unknown xml and xml from an unknown namespace</li>
+ <li>Changed extensions to allow for external xml</li>
+ <li>Can have a default element mapping for extensions</li>
+ </ul>
+ </section>
+ </section>
</body>
</document>
<p>The layout of the document depends mainly on the font being used.
If two renderers have the same font metrics then it is possible to use the same Area Tree to render both. This can be handled by the AreaTree Handler.</p>
</section>
+ <section id="status">
+ <title>Status</title>
+ <section id="status-todo">
+ <title>To Do</title>
+ </section>
+ <section id="status-wip">
+ <title>Work In Progress</title>
+ </section>
+ <section id="status-complete">
+ <title>Completed</title>
+ <ul>
+ <li>new renderer model</li>
+ <li>new interface for structured documents, rtf and mif</li>
+ <li>added handlers for xml in renderer</li>
+ </ul>
+ </section>
+ </section>
</body>
</document>
--- /dev/null
+<?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>FOP Design: Startup, Environment, Control</title>
+ </header>
+ <body>
+ <section id="intro">
+ <title>Introduction</title>
+ <p>Startup is the process of getting FOP bootstrapped and creating basic objects. Environment includes acquiring user options, instantiating any frameworks, setting up logging, etc. Control includes the basic logic for tieing the various subsystems together properly.</p>
+ </section>
+ <section id="status">
+ <title>Status</title>
+ <section id="status-todo">
+ <title>To Do</title>
+ <ul>
+ <li>avalon integration - logging, configuration, component management, caching, uri resolver</li>
+ <li>improved interfaces
+ <ul>
+ <li>no threading/static problems</li>
+ <li>simpler to use</li>
+ </ul>
+ </li>
+ <li>better commandline handling</li>
+ </ul>
+ </section>
+ <section id="status-wip">
+ <title>Work In Progress</title>
+ </section>
+ <section id="status-complete">
+ <title>Completed</title>
+ <ul>
+ <li><strong>better image handling</strong> - redone so it can use a cache and synchronizes properly only on the current image while loading</li>
+ </ul>
+ </section>
+ </section>
+ </body>
+</document>
+++ /dev/null
-<?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">
-
-<!-- Status of Design/Rewrite -->
-
-<document>
- <header>
- <title>Design Status</title>
- <subtitle>Current Status of FOP and Design</subtitle>
- <authors>
- <person name="Keiron Liddle" email="keiron@aftexsw.com"/>
- </authors>
- </header>
-
- <body>
-<section>
- <title>Status</title>
-<p>
-Currently some of FOP is being re-written so that the layout can be handled
-properly without the problems that have been encountered and to make
-it possible to handle keeps/breaks and spacing better.
- </p>
-<p>
-A number of issues have been dealt with in the redesigned code.
- </p>
- </section>
-<section>
- <title>Features TODO</title>
-<ul>
-<li>avalon integration - logging, configuration, component management, caching, uri resolver</li>
-<li>improved interfaces
-<ul>
- <li>no threading/static problems</li>
- <li>simpler to use</li>
-</ul>
-</li>
-<li>better commandline handling</li>
-</ul>
- </section>
-<section>
- <title>Done/Started Features</title>
-<p>
-Many of these changes will make FOP much better to use and develop.
-So if you help out with the development you can get to use these
-things sooner.
-</p>
-<ul>
-<li><strong>better layout design</strong> - that can handle keeps and
-spacing better</li>
-<li><strong>better area tree handling</strong> - means it can run in
-less memory</li>
-<li><strong>better image handling</strong> - redone so it can use a
-cache and synchronizes properly only on the current image while loading</li>
-<li>svg now in an xml handler, FOP can be used without batik</li>
-<li>bookmark extension improved a bit - changed bookmark extension,
-now requires a wrapping element bookmark</li>
-<li>new interface for structured documents, rtf and mif</li>
-<li>better handling of unknown xml and xml from an unknown namespace</li>
-<li>Changed extensions to allow for external xml</li>
-<li>Can have a default element mapping for extensions</li>
-<li>mathml extension</li>
-<li>another xml -> svg extension</li>
-<li>svg text normal text if that can be handled otherwise stroked
-this is done automatically</li>
-<li>new area tree model</li>
-<li>new renderer model</li>
-<li>added handlers for xml in renderer</li>
-<li>changed area tree xml format to match the area tree hierarchy</li>
-</ul>
-
- </section>
-
- </body>
-</document>
-
projects / xmlgraphics-fop.git / commitdiff