diff options
| author | Keiron Liddle <keiron@apache.org> | 2001-12-17 10:17:25 +0000 |
|---|---|---|
| committer | Keiron Liddle <keiron@apache.org> | 2001-12-17 10:17:25 +0000 |
| commit | 2117e3c29113281c400889d61a2bd6926039a6c3 (patch) | |
| tree | 30f3b05cb2883a1fb53ec8e091af1ad7d2502d20 /docs/design/intro.xml | |
| parent | 3d1be63b36324200ff7cb8d8bccf5db4596cdff5 (diff) | |
| download | xmlgraphics-fop-2117e3c29113281c400889d61a2bd6926039a6c3.tar.gz xmlgraphics-fop-2117e3c29113281c400889d61a2bd6926039a6c3.zip | |
information shuffling
git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@194608 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'docs/design/intro.xml')
| -rw-r--r-- | docs/design/intro.xml | 26 |
1 files changed, 25 insertions, 1 deletions
diff --git a/docs/design/intro.xml b/docs/design/intro.xml index b1aa5db67..f05c42f13 100644 --- a/docs/design/intro.xml +++ b/docs/design/intro.xml @@ -14,6 +14,11 @@ <body> <s1 title="Introduction"> <p> +<note><p> +The information here is still in the early stage, some information +may be wrong or misleading. In general there is not a broad enough +input and it is lacking in depth of information. +</p></note> The information here describes the design and architecture details for FOP. Currently this is part of a redesign process for some of the core parts of FOP. @@ -22,9 +27,28 @@ FOP. The redesign is mainly focusing on some particular process involved with the layout process when converting the FO tree into the Area Tree. </p> +<s2 title="Aims"> <p> - +The main aim for FOP is to comply with the spec and to be able to +process files of any size. + </p> + <p> +In achieving this aim we need to understand the problem and break it +into small problems that can be solved. + </p> + <p> +<ul> +<li>use SAX as input</li> +<li>process FO elements ASAP</li> +<li>dispose of unused memory, keep memory minimal</li> +<li>layout handles floats, footnotes and keeps in a simple straight forward way</li> +<li>id references are kept simple</li> +<li>pages are rendered ASAP, can be cached until resolved</li> +<li>renderers are totally responsible for their output format</li> +<li>output is sent to a stream</li> +</ul> </p> +</s2> </s1> </body> |