keiron      2002/06/14 00:53:34

  Modified:    docs/xml-docs/fop status.xml
               docs/design intro.xml status.xml
  more status info, design status
  Revision  Changes    Path
  1.2       +1 -0      xml-fop/docs/xml-docs/fop/status.xml
  Index: status.xml
  RCS file: /home/cvs/xml-fop/docs/xml-docs/fop/status.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- status.xml        12 Jun 2002 14:14:32 -0000      1.1
  +++ status.xml        14 Jun 2002 07:53:34 -0000      1.2
  @@ -35,6 +35,7 @@
   ... and plenty of other areas. See the <jump href="todo.html">todo</jump>
   list for more details.
  +See ths <jump href="design/status.html">Status</jump> for more information.
   Development for 1.0DR1 is addressing the design issues for layout and
  1.4       +0 -5      xml-fop/docs/design/intro.xml
  Index: intro.xml
  RCS file: /home/cvs/xml-fop/docs/design/intro.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- intro.xml 17 Dec 2001 10:17:25 -0000      1.3
  +++ intro.xml 14 Jun 2002 07:53:34 -0000      1.4
  @@ -14,11 +14,6 @@
   <s1 title="Introduction">
  -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.
   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
  1.2       +46 -1     xml-fop/docs/design/status.xml
  Index: status.xml
  RCS file: /home/cvs/xml-fop/docs/design/status.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- status.xml        14 Dec 2001 07:32:28 -0000      1.1
  +++ status.xml        14 Jun 2002 07:53:34 -0000      1.2
  @@ -1,6 +1,6 @@
   <?xml version="1.0" standalone="no"?>
  -<!-- Overview -->
  +<!-- Status of Design/Rewrite -->
  @@ -19,6 +19,51 @@
   it possible to handle keeps/breaks and spacing better.
  +A number of issues have been dealt with in the redesigned code.
  +  </p>
  +  </s1>
  +<s1 title="Features TODO">
  +<li>avalon integration - logging, configuration, component management, caching, uri 
  +<li>improved interfaces
  +  <li>no threading/static problems</li>
  +  <li>simpler to use</li>
  +<li>better commandline handling</li>
  +  </p>
  +  </s1>
  +<s1 title="Done/Started Features">
  +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.
  +<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>

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to