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/30 20:54:42 UTC
cvs commit: xml-fop/src/documentation/content/xdocs/design startup.xml areas.xml book.xml extending.xml layout.xml parsing.xml renderers.xml status.xml
vmote 2003/04/30 11:54:42
Modified: src/documentation/content/xdocs/design areas.xml book.xml
extending.xml layout.xml parsing.xml renderers.xml
Added: src/documentation/content/xdocs/design startup.xml
Removed: src/documentation/content/xdocs/design status.xml
Log:
Move contents of design/status.xml (not currently published anywhere) to the various subsystem doc in a "status" section.
Add startup.xml document as a stub to contain config, control, and env status content.
Remove design/status.xml.
Revision Changes Path
1.13 +16 -0 xml-fop/src/documentation/content/xdocs/design/areas.xml
Index: areas.xml
===================================================================
RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/design/areas.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- areas.xml 30 Apr 2003 05:21:35 -0000 1.12
+++ areas.xml 30 Apr 2003 18:54:41 -0000 1.13
@@ -154,5 +154,21 @@
<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>
1.20 +1 -0 xml-fop/src/documentation/content/xdocs/design/book.xml
Index: book.xml
===================================================================
RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/design/book.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- book.xml 23 Apr 2003 23:41:30 -0000 1.19
+++ book.xml 30 Apr 2003 18:54:41 -0000 1.20
@@ -11,6 +11,7 @@
<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"/>
1.8 +21 -1 xml-fop/src/documentation/content/xdocs/design/extending.xml
Index: extending.xml
===================================================================
RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/design/extending.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- extending.xml 29 Apr 2003 16:33:45 -0000 1.7
+++ extending.xml 30 Apr 2003 18:54:41 -0000 1.8
@@ -98,7 +98,27 @@
>>]]></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>
1.11 +18 -0 xml-fop/src/documentation/content/xdocs/design/layout.xml
Index: layout.xml
===================================================================
RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/design/layout.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- layout.xml 29 Apr 2003 16:12:34 -0000 1.10
+++ layout.xml 30 Apr 2003 18:54:41 -0000 1.11
@@ -280,5 +280,23 @@
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>
1.7 +17 -0 xml-fop/src/documentation/content/xdocs/design/parsing.xml
Index: parsing.xml
===================================================================
RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/design/parsing.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- parsing.xml 25 Apr 2003 16:40:52 -0000 1.6
+++ parsing.xml 30 Apr 2003 18:54:41 -0000 1.7
@@ -38,5 +38,22 @@
<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>
1.11 +17 -0 xml-fop/src/documentation/content/xdocs/design/renderers.xml
Index: renderers.xml
===================================================================
RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/design/renderers.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- renderers.xml 30 Apr 2003 05:21:35 -0000 1.10
+++ renderers.xml 30 Apr 2003 18:54:41 -0000 1.11
@@ -191,5 +191,22 @@
<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>
1.1 xml-fop/src/documentation/content/xdocs/design/startup.xml
Index: startup.xml
===================================================================
<?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>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-cvs-help@xml.apache.org