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

2004-11-09 Thread Clay Leeds 
On Nov 9, 2004, at 11:58 AM, Simon Pepping wrote:
On Mon, Nov 08, 2004 at 01:43:51PM -0800, Clay Leeds wrote:
I suspect this could be a problem for the Forrest site-generation
process[1]:
  Specifying menus with book.xml
  Historically, menus in Forrest have been generated from a
  book.xml file, one per directory. This mechanism is
  still available, and if a book.xml is found, it will be
  used in preference to the menu generated by the site.xml
  file. The book.xml  files can use "site:" URIs to ease
  the maintenance burden  that led to obsolescence of
  book.xml files. In general, however, we recommend that
  users avoid book.xml files.
Is it possible for you to rename that file so it doesn't conflict? 
(I'm
hoping it is trivial for you to change that file name. Perhaps
fop-=dni-book.xml or something). If not, I'll see if I can come up 
with
some other solution, although my guess is that any workaround will
preclude it from having the same look & feel as the rest of the FOP 
web
site.
A shame; I thought book.xml was the right name for this file. Renamed
to DnI.xml.
Simon
Perhaps it is the correct name for the file. IMHO, perhaps forrest 
should pre-pend for_ in front of filenames (e.g., for_book.xml, 
for_site.xml, for_tabs.xml, etc.) like this to prevent this types of 
problems. Forrest already was having problems where they were using 
'site.xml' and outputting "site.html" and 'site.pdf' (they changed the 
latter two to "wholesite.html" and "wholesite.pdf"...).

Anyway, thanks for making the change. It means that the DnI stuff can 
be skinned (as I mentioned previously, the book.xml in there made 
forrest think that it had it's own 'book.xml' file for that directory, 
so it wouldn't use site.xml file (which defines the site navigation 
structure).

Web Maestro Clay
--
Clay Leeds - <[EMAIL PROTECTED]>
Webmaster/Developer - Medata, Inc. - 
PGP Public Key:

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

2004-11-09 Thread Simon Pepping 
On Mon, Nov 08, 2004 at 01:43:51PM -0800, Clay Leeds wrote:
> I suspect this could be a problem for the Forrest site-generation 
> process[1]:
> 
>   Specifying menus with book.xml
> 
>   Historically, menus in Forrest have been generated from a
>   book.xml file, one per directory. This mechanism is
>   still available, and if a book.xml is found, it will be
>   used in preference to the menu generated by the site.xml
>   file. The book.xml  files can use "site:" URIs to ease
>   the maintenance burden  that led to obsolescence of
>   book.xml files. In general, however, we recommend that
>   users avoid book.xml files.
> 
> Is it possible for you to rename that file so it doesn't conflict? (I'm 
> hoping it is trivial for you to change that file name. Perhaps 
> fop-=dni-book.xml or something). If not, I'll see if I can come up with 
> some other solution, although my guess is that any workaround will 
> preclude it from having the same look & feel as the rest of the FOP web 
> site.

A shame; I thought book.xml was the right name for this file. Renamed
to DnI.xml.

Simon

-- 
Simon Pepping
home page: http://www.leverkruid.nl

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

2004-11-08 Thread Clay Leeds 
On Nov 8, 2004, at 12:48 PM, Simon Pepping wrote:
Clay,
On Sun, Nov 07, 2004 at 08:48:23PM -0800, Clay Leeds wrote:
Simon,
Does the book.xml file in your DnI section serve any specific purpose
(DnI-related), or is it to follow the common coding/forrest 
convention?
I ask, because the use of book.xml is deprecated in Forrest-0.6 in
favor of the site-wide src/documentation/content/xdocs/site.xml file.
book.xml is the top-level file that calls in all the chapters. It
is indispensible, it is _the_ book, so to speak. I compared it with
the book files you have removed. I see that it has a different
purpose. The other book files seem to define menus.
Regards, Simon
I suspect this could be a problem for the Forrest site-generation 
process[1]:

  Specifying menus with book.xml
  Historically, menus in Forrest have been generated from a
  book.xml file, one per directory. This mechanism is
  still available, and if a book.xml is found, it will be
  used in preference to the menu generated by the site.xml
  file. The book.xml  files can use "site:" URIs to ease
  the maintenance burden  that led to obsolescence of
  book.xml files. In general, however, we recommend that
  users avoid book.xml files.
Is it possible for you to rename that file so it doesn't conflict? (I'm 
hoping it is trivial for you to change that file name. Perhaps 
fop-=dni-book.xml or something). If not, I'll see if I can come up with 
some other solution, although my guess is that any workaround will 
preclude it from having the same look & feel as the rest of the FOP web 
site.

[1]
http://forrest.apache.org/docs/linking.html#book-menu-selection
Web Maestro Clay
--
Clay Leeds - <[EMAIL PROTECTED]>
Webmaster/Developer - Medata, Inc. - 
PGP Public Key:

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

2004-11-08 Thread Simon Pepping 
Clay,

On Sun, Nov 07, 2004 at 08:48:23PM -0800, Clay Leeds wrote:
> Simon,
> 
> Does the book.xml file in your DnI section serve any specific purpose 
> (DnI-related), or is it to follow the common coding/forrest convention? 
> I ask, because the use of book.xml is deprecated in Forrest-0.6 in 
> favor of the site-wide src/documentation/content/xdocs/site.xml file.

book.xml is the top-level file that calls in all the chapters. It
is indispensible, it is _the_ book, so to speak. I compared it with
the book files you have removed. I see that it has a different
purpose. The other book files seem to define menus.

Regards, Simon
 
> On Nov 7, 2004, at 8:26 PM, [EMAIL PROTECTED] wrote:
> >clay2004/11/07 20:26:29
> >
> >  Removed: src/documentation/content/xdocs book.xml
> >   src/documentation/content/xdocs/design book.xml
> >   src/documentation/content/xdocs/design/alt.design 
> >book.xml
> >   
> >src/documentation/content/xdocs/design/alt.design/properties
> >book.xml
> >   src/documentation/content/xdocs/dev book.xml
> >  Log:
> >  removed all book.xml files (except DnI)
> 
> Web Maestro Clay
> -- 
> Clay Leeds - <[EMAIL PROTECTED]>
> Webmaster/Developer - Medata, Inc. - 
> PGP Public Key: 
> 

-- 
Simon Pepping
home page: http://www.leverkruid.nl

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

2004-11-07 Thread Clay Leeds 
Simon,
Does the book.xml file in your DnI section serve any specific purpose 
(DnI-related), or is it to follow the common coding/forrest convention? 
I ask, because the use of book.xml is deprecated in Forrest-0.6 in 
favor of the site-wide src/documentation/content/xdocs/site.xml file.

On Nov 7, 2004, at 8:26 PM, [EMAIL PROTECTED] wrote:
clay2004/11/07 20:26:29
  Removed: src/documentation/content/xdocs book.xml
   src/documentation/content/xdocs/design book.xml
   src/documentation/content/xdocs/design/alt.design 
book.xml
   
src/documentation/content/xdocs/design/alt.design/properties
book.xml
   src/documentation/content/xdocs/dev book.xml
  Log:
  removed all book.xml files (except DnI)
Web Maestro Clay
--
Clay Leeds - <[EMAIL PROTECTED]>
Webmaster/Developer - Medata, Inc. - 
PGP Public Key:

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

2003-05-30 Thread jeremias 
jeremias2003/05/29 14:41:33

  Modified:src/documentation/content/xdocs/dev book.xml
  Log:
  Remove link to examples
  Submitted by: Glen Mazza <[EMAIL PROTECTED]>
  
  Revision  ChangesPath
  1.26  +0 -1  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.25
  retrieving revision 1.26
  diff -u -r1.25 -r1.26
  --- book.xml  15 May 2003 16:44:52 -  1.25
  +++ book.xml  29 May 2003 21:41:33 -  1.26
  @@ -31,7 +31,6 @@
   
   
 
  -  
 
 http://cvs.apache.org/viewcvs.cgi/xml-fop"/>
   
  
  
  

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

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

2003-04-06 Thread vmote 
vmote   2003/04/06 21:22:59

  Modified:src/documentation/content/xdocs/dev book.xml
  Log:
  Move testing.xml to dev area.
  
  Revision  ChangesPath
  1.13  +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.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- book.xml  7 Apr 2003 00:55:01 -   1.12
  +++ book.xml  7 Apr 2003 04:22:59 -   1.13
  @@ -28,6 +28,7 @@
 http://nagoya.apache.org/wiki/apachewiki.cgi?FOPProjectPages"/>
 
 
  +  
 http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=Fop&short_desc=%5BPATCH%5D&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&namedcmd=Fop+all&newqueryname=fop+patch+queue&tofooter=1&order=Reuse+same+sort+as+last+time"/>
   
   
  
  
  

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

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

2002-12-23 Thread keiron 
keiron  2002/12/23 02:35:13

  Modified:src/documentation/content/xdocs/dev book.xml
  Log:
  updated new Wiki location
  
  Revision  ChangesPath
  1.8   +1 -1  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.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- book.xml  12 Dec 2002 10:59:33 -  1.7
  +++ book.xml  23 Dec 2002 10:35:13 -  1.8
  @@ -24,7 +24,7 @@
 
   
   
  -  http://codeconsult.ch/wiki/index.php/FopTasks"/>
  +  http://nagoya.apache.org/wiki/apachewiki.cgi?FOPProjectPages"/>
 
   
   
  
  
  

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

cvs commit: xml-fop/src/documentation/content/xdocs/dev book.xml configuration.xml examples.xml extensions.xml faq.xml index.xml svg.xml

2002-11-18 Thread keiron 
keiron  2002/11/18 23:57:29

  Modified:src/documentation/content/xdocs book.xml bugs.xml
compiling.xml compliance.xml configuration.xml
download.xml embedding.xml examples.xml
extensions.xml faq.xml fonts.xml gethelp.xml
implemented.xml index.xml involved.xml license.xml
limitations.xml news.xml output.xml relnotes.xml
resources.xml running.xml status.xml svg.xml
tabs.xml testing.xml
   src/documentation/content/xdocs/design architecture.xml
areas.xml book.xml breakpos.xml embedding.xml
extending.xml fotree.xml index.xml layout.xml
optimise.xml properties.xml renderers.xml
status.xml useragent.xml
   src/documentation/content/xdocs/dev book.xml
configuration.xml examples.xml extensions.xml
faq.xml index.xml svg.xml
  Log:
  The attached patch file contains:
  1. Valid URIs for all xdoc DTD declarations.
  2. Some minor changes for xdoc documents that were discovered to be invalid
  after the DTD declarations were fixed.
  3. Changed tabs.xml so that the 2nd tab on our site will now read "Redesign"
  instead of "dev" (this was discussed in a recent thread).
  Submitted By: [EMAIL PROTECTED] (Victor Mote)
  
  Revision  ChangesPath
  1.7   +3 -1  xml-fop/src/documentation/content/xdocs/book.xml
  
  Index: book.xml
  ===
  RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/book.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- book.xml  13 Nov 2002 12:21:28 -  1.6
  +++ book.xml  19 Nov 2002 07:57:27 -  1.7
  @@ -1,5 +1,7 @@
   
  -  
  +  http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-cocoon2/src/documentation/xdocs/dtd/book-cocoon-v10.dtd";>
  +
   
 
  -
  +http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd";>
   
   
 
  
  
  
  1.2   +2 -1  xml-fop/src/documentation/content/xdocs/compiling.xml
  
  Index: compiling.xml
  ===
  RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/compiling.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- compiling.xml 4 Nov 2002 16:20:51 -   1.1
  +++ compiling.xml 19 Nov 2002 07:57:27 -  1.2
  @@ -1,5 +1,6 @@
   
  -
  +http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd";>
   
   
 
  
  
  
  1.2   +2 -1  xml-fop/src/documentation/content/xdocs/compliance.xml
  
  Index: compliance.xml
  ===
  RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/compliance.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- compliance.xml13 Nov 2002 12:21:30 -  1.1
  +++ compliance.xml19 Nov 2002 07:57:27 -  1.2
  @@ -1,5 +1,6 @@
   
  -
  +http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-fop/src/documentation/resources/schema/dtd/compliance-v10.dtd?rev=1.1";>
   
   
 
  
  
  
  1.2   +2 -1  xml-fop/src/documentation/content/xdocs/configuration.xml
  
  Index: configuration.xml
  ===
  RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/configuration.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- configuration.xml 4 Nov 2002 16:20:51 -   1.1
  +++ configuration.xml 19 Nov 2002 07:57:27 -  1.2
  @@ -1,5 +1,6 @@
   
  -
  +http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd";>
   
   
   
  
  
  
  1.3   +2 -1  xml-fop/src/documentation/content/xdocs/download.xml
  
  Index: download.xml
  ===
  RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/download.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- download.xml  5 Nov 2002 11:38:03 -   1.2
  +++ download.xml  19 Nov 2002 07:57:27 -  1.3
  @@ -1,5 +1,6 @@
   
  -
  +http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd";>
   
   
   
  
  
  
  1.2   +2 -1  xml-fop/src/documentation/content/xdocs/embedding.xml
  
  Index: embedding.xml
  ===
  RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/embedding.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- embedding.xml 4 Nov 20

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

2002-11-07 Thread keiron 
keiron  2002/11/07 00:15:01

  Modified:src/documentation/content/xdocs book.xml
   src/documentation/content/xdocs/dev book.xml extensions.xml
  Added:   src/documentation/content/xdocs/design architecture.xml
areas.xml book.xml breakpos.xml embedding.xml
extending.xml fotree.xml index.xml layout.xml
optimise.xml properties.xml renderers.xml
status.xml useragent.xml
  Log:
  converted design docs to forrest
  needs updating
  
  Revision  ChangesPath
  1.5   +11 -3 xml-fop/src/documentation/content/xdocs/book.xml
  
  Index: book.xml
  ===
  RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/book.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- book.xml  4 Nov 2002 16:20:51 -   1.4
  +++ book.xml  7 Nov 2002 08:15:01 -   1.5
  @@ -13,32 +13,40 @@
 
 
 
  +  
  +
   
  +
 
 
 
  +
   
  +
 
 
 
 
 
  +
   
  +
 
 
 
 
  +
   
  +
 
 
 
  +
   
  +
 
 
 
  -
  -  
  -
 http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=Fop&short_desc=%5BPATCH%5D&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&namedcmd=Fop+all&newqueryname=fop+patch+queue&tofooter=1&order=Reuse+same+sort+as+last+time"/>
   
   
  
  
  
  1.1  xml-fop/src/documentation/content/xdocs/design/architecture.xml
  
  Index: architecture.xml
  ===
  
  
  
  
  
  Architecture
  Architecture information for FOP
  
  
  
  
  
  
  
  
FOP Mechanics
  
  
Introduction
  
  The overall process is controlled by org.apache.fop.apps.Driver.
  This class handles the FO Tree building, renderers, output and logging.
  
  
  The process in general is that the FO document is sent to the tree
  builder via SAX events. This creates an FO Tree. The FO Tree is then
  handled by the layout processor which converts the FO Tree into an area
  tree. This area tree is then given to the renderer and the renderer converts
  the area tree into a stream of data containing the output document.
  
  
  
  
Formatting Object Tree
  
  The class org.apache.fop.fo.FOTreeBuilder is responsible for
  actually constructing the FO tree. The key SAX events used are 
  startElement(),
  endElement() and characters().
  
  All formatting objects derive from abstract class
  org.apache.fop.fo.FONode. The other FO classes inherit from
  FONode as follows:
  
  
  
  
Rendering
  
  This is a separate process. The render() method in
  Driver is invoked (say,
  by CommandLine) with the laid-out AreaTree and a
  PrintWriter as arguments.
  This actually calls the render() method in a specific implementation of
  the Renderer interface, typically PDFRenderer or
  AWTRenderer.
  
  
  
  
  
  
  
  
  
  
  1.1  xml-fop/src/documentation/content/xdocs/design/areas.xml
  
  Index: areas.xml
  ===
   
  
  
  
  
  Area Tree
  Area Tree Design for FOP
  
  
  
  
  
  
  
Area Tree
  
  The code to implement the area tree will attempt to match the areas
  defined in the specification. A number of optimisations may be possible
  for similar areas and groups of areas.

 
  Since the area tree will be used during the layout by the layout managers
  it will need to store information that affects the layout. The information
  such as spacing and keeps will be held in such a way that it can be
  discarded once the layout is finalised.

  
Structure
   
  The area tree is a root element that has a list of page-viewport-areas.
  Each page viewport has a page-reference-area which holds the contents of
  the page. To handle the processing better FOP does not maintain a list
  at the root level but lets another class handle each page as it is added.


  
Page
  
  A page is made up of five area regions. These are before, start, body,
  end and after. Each region has a viewport and contain