cvs commit: xml-fop/src/documentation/content/xdocs/dev implement.xml book.xml

2003-04-06 Thread vmote
vmote   2003/04/06 21:43:41

  Modified:src/documentation/content/xdocs/design book.xml
   src/documentation/content/xdocs/dev book.xml
  Added:   src/documentation/content/xdocs/dev implement.xml
  Removed: src/documentation/content/xdocs/design architecture.xml
  Log:
  Move design/architecture.xml to dev/implement.xml.
  
  Revision  ChangesPath
  1.7   +0 -3  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.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- book.xml  24 Mar 2003 21:37:20 -  1.6
  +++ book.xml  7 Apr 2003 04:43:41 -   1.7
  @@ -14,9 +14,6 @@
 menu-item label=Index href=index.html/
 menu-item label=Understanding href=understanding/index.html/
   /menu
  -menu label=Overview
  -  menu-item label=Architecture Implementation href=architecture.html/
  -/menu
   menu label=Sections
 menu-item label=FO Tree href=fotree.html/
 menu-item label=Properties href=properties.html/
  
  
  
  1.14  +1 -0  xml-fop/src/documentation/content/xdocs/dev/book.xml
  
  Index: book.xml
  ===
  RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/dev/book.xml,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- book.xml  7 Apr 2003 04:22:59 -   1.13
  +++ book.xml  7 Apr 2003 04:43:41 -   1.14
  @@ -11,6 +11,7 @@
 menu-item label=Introduction href=index.html/
 menu-item label=FAQs href=faq.html/
 menu-item label=Examples href=examples.html/
  +  menu-item label=Walk-Thru href=implement.html/
   /menu
   menu label=Using
 menu-item label=Extensions href=extensions.html/
  
  
  
  1.1  xml-fop/src/documentation/content/xdocs/dev/implement.xml
  
  Index: implement.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
  titleImplementation Overview/title
  subtitleFollowing a Document Through FOP/subtitle
  authors
person name=Arved Sandstrom email=/
  /authors
/header
body
  pThe purpose of this document is to tie together the FOP design (interface) 
with some of the key points where control is passed within FOP (implementation), so 
that developers can quickly find the section of code that is relevant to their needs. 
The process described is for a typical command-line document. All classes are in 
org.apache.fop unless otherwise designated./p
  section
titleOverview/title
pThe input FO document is sent to the FO tree builder via SAX events. 
Fragments of an FO Tree are built from this process. As each page-sequence element is 
completed, it is passed to a layout processor, which in turn converts it into an Area 
Tree. The Area Tree is then given to the Renderer, which converts it into a stream of 
data containing the output document. The sections below will provide additional 
details. Where needed differences between the trunk and maintenance branches are shown 
in tabular format./p
  /section
  section
titleStartup/title
ul
  liThe job starts in emapps.Fop.main()/em./li
  liControl is passed to emapps.CommandLineStarter.run()/em./li
  liControl is passed to emapps.Driver.render()/em. This class fires up 
a SAX parser, the events from which indirectly control the remaining processing, 
including building the FO Tree, building the Area Tree, rendering, output and 
logging./li
/ul
  /section
  section
titleFormatting Object Tree/title
table
  tr
thTrunk/ththMaintenance/th
  /tr
  tr
td colspan=2The SAX events that the parser creates are handled by 
emfo.FOTreeBuilder/em, which uses codestartElement()/code, 
codeendElement()/code, and codecharacters()/code methods to build the FO 
Tree./td
tdemfo.FOTreeBuilder.endElement()/em runs the end() method for each 
node as it is created. The emfo.pagination.PageSequence/em class overrides this 
end() method to run emapps.LayoutHandler.endPageSequence()/em, which in turn runs 
emfo.pagination.PageSequence.format()/em./td
tdthe end of a PageSequence element causes the PageSequence object to be 
passed to emapps.StreamRenderer.render/em, which in turn runs 
fo.pagination.PageSequence.format./td
  /tr
  tr
td/td
tdemfo.pagination.PageSequence.addFlow()/em programatically adds a 
Flow object 

cvs commit: xml-fop/src/documentation/content/xdocs/dev implement.xml

2003-04-06 Thread vmote
vmote   2003/04/06 21:58:52

  Modified:src/documentation/content/xdocs/dev implement.xml
  Log:
  Fix table rows.
  
  Revision  ChangesPath
  1.2   +4 -2  xml-fop/src/documentation/content/xdocs/dev/implement.xml
  
  Index: implement.xml
  ===
  RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/dev/implement.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- implement.xml 7 Apr 2003 04:43:41 -   1.1
  +++ implement.xml 7 Apr 2003 04:58:52 -   1.2
  @@ -31,15 +31,17 @@
   /tr
   tr
 td colspan=2The SAX events that the parser creates are handled by 
emfo.FOTreeBuilder/em, which uses codestartElement()/code, 
codeendElement()/code, and codecharacters()/code methods to build the FO 
Tree./td
  +/tr
  +tr
 tdemfo.FOTreeBuilder.endElement()/em runs the end() method for each 
node as it is created. The emfo.pagination.PageSequence/em class overrides this 
end() method to run emapps.LayoutHandler.endPageSequence()/em, which in turn runs 
emfo.pagination.PageSequence.format()/em./td
 tdthe end of a PageSequence element causes the PageSequence object to 
be passed to emapps.StreamRenderer.render/em, which in turn runs 
fo.pagination.PageSequence.format./td
   /tr
   tr
  -  td/td
  +  td./td
 tdemfo.pagination.PageSequence.addFlow()/em programatically adds a 
Flow object to the page sequence./td
   /tr
   tr
  -  td/td
  +  td./td
 tdfo.pagination.PageSequence.makePage() creates a BodyArea and passes 
it to emfo.Flow.layout/em/td
   /tr
   tr
  
  
  

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