cvs commit: xml-fop checkstyle.cfg

2003-06-30 Thread vmote
vmote 2003/06/30 09:04:11 Modified:.checkstyle.cfg Log: Sort properties in same order as documentation for easier reference. Add some comments. There are no intended changes to the substance. Revision ChangesPath 1.2 +31 -5 xml-fop/checkstyle.cfg

cvs commit: xml-fop/src/documentation/content/xdocs download.xml servlets.xml

2003-06-30 Thread vmote
vmote 2003/06/30 09:13:16 Modified:.checkstyle.cfg src/documentation/resources/stylesheets compliance2html.xsl src/documentation/content/xdocs download.xml servlets.xml Log: Fix bad RCS keyword (should be $RCSfile$). Revision Changes

cvs commit: xml-fop/src/documentation/resources/stylesheets compliance2html.xsl

2003-06-30 Thread vmote
vmote 2003/06/30 09:23:17 Modified:src/documentation/resources/stylesheets compliance2html.xsl Log: Fix bad RCS keyword (should be $RCSfile$). Revision ChangesPath 1.9 +2 -2 xml-fop/src/documentation/resources/stylesheets/compliance2html.xsl Index:

cvs commit: xml-fop/src/java/org/apache/fop/rtf/rtflib/tools ImageConstants.java ImageUtil.java

2003-06-30 Thread vmote
vmote 2003/06/30 10:45:33 Modified:src/java/org/apache/fop/rtf/rtflib/rtfdoc IRtfPageNumberCitationContainer.java IRtfPageNumberContainer.java IRtfParagraphContainer.java

cvs commit: xml-fop checkstyle.cfg

2003-06-30 Thread vmote
vmote 2003/06/30 11:16:36 Modified:.checkstyle.cfg Log: Explicitly enter naming convention values used as defaults by checkstyle, so that they can be more easily seen and managed, and so that any future changes in defaults will not affect our standards. No changes to the

cvs commit: xml-fop checkstyle.cfg

2003-06-30 Thread vmote
vmote 2003/06/30 12:21:17 Modified:.checkstyle.cfg Log: Explicitly enter remaining convention values used as defaults by checkstyle, so that they can be more easily seen and managed, and so that any future changes in defaults will not affect our standards. No changes to

finalize style wiki?

2003-06-30 Thread Victor Mote
I have added all of the checkstyle default values into our checkstyle.cfg file (making sure that before after results are identical), so that it is easier to see what our de facto standards are. This may also prevent problems later if checkstyle changes their defaults. And Peter, it may be of

cvs commit: xml-fop/src/java/org/apache/fop/rtf/rtflib/rtfdoc RtfBookmark.java RtfHyperLink.java

2003-06-30 Thread vmote
vmote 2003/06/30 13:42:20 Modified:src/java/org/apache/fop/rtf/rtflib/rtfdoc RtfBookmark.java RtfHyperLink.java Log: Refactor constants to conform to style guidelines. Revision ChangesPath 1.6 +7 -6

Re: finalize style wiki?

2003-06-30 Thread J.Pietschmann
Victor Mote wrote: Is it agreeable to everyone to move the resolved Style wiki issues to an html page under our dev tab? +1 (This is in keeping with my philosophy that wiki are temporary whiteboard areas that should usually have a limited life Same here. J.Pietschmann

Re: Problem getting CVS changes onto FOP-CVS list.

2003-06-30 Thread J.Pietschmann
Glen Mazza wrote: BTW you seem to have set your indentation to 2 ... In the code? I can't find an example where that happened (IIRC my changed lines were all starting first column anyway)--please let me know of one. I can't find it. There was a large block in the diff where indentation changed,

cvs commit: xml-fop/src/java/org/apache/fop/fo FOTreeBuilder.java

2003-06-30 Thread pietsch
pietsch 2003/06/30 14:04:06 Modified:src/java/org/apache/fop/rtf/rtflib/rtfdoc RtfPage.java src/java/org/apache/fop/rtf/renderer RTFHandler.java src/java/org/apache/fop/datatypes FixedLength.java src/java/org/apache/fop/svg PDFTranscoder.java

[VOTE] Move ElementMapping initialization from Driver to FOTreeBuilder

2003-06-30 Thread Glen Mazza
Team, As mentioned earlier, I would like to pull out FOTreeBuilder's ElementMapping initialization from Apps.Driver, and instead encapsulate it within FOTreeBuilder directly. [Note: Alt-design no longer uses ElementMappings--but this change does not preclude switching to alt-design's method:

cvs commit: xml-fop/src/java/org/apache/fop/rtf/rtflib/tools ImageConstants.java ImageUtil.java

2003-06-30 Thread vmote
vmote 2003/06/30 15:01:03 Modified:src/java/org/apache/fop/rtf/rtflib/exceptions RtfException.java RtfStructureException.java src/java/org/apache/fop/rtf/rtflib/interfaces ITableColumnsInfo.java

RE: [VOTE] Move ElementMapping initialization from Driver to FOTreeBuilder

2003-06-30 Thread Victor Mote
Glen Mazza wrote: But, this is a two-vote procedure because something else has to be done first: 1.) Discontinue the dynamic discovery and run-time adding capability of ElementMappings. The code currently allows you to add user-created ElementMappings to the FOTreeBuilder at run-time

cvs commit: xml-fop/src/java/org/apache/fop/rtf/rtflib/rtfdoc BorderAttributesConverter.java IBorderAttributes.java

2003-06-30 Thread vmote
vmote 2003/06/30 17:24:38 Modified:src/java/org/apache/fop/rtf/rtflib/rtfdoc BorderAttributesConverter.java Removed: src/java/org/apache/fop/rtf/rtflib/rtfdoc IBorderAttributes.java Log: Add javadoc comments. Remove unused

RE: [VOTE] Move ElementMapping initialization from Driver to FOTreeBuilder

2003-06-30 Thread Glen Mazza
Thanks for voting. --- Victor Mote [EMAIL PROTECTED] wrote: What about instream-foreign objects that get passed through? SVG is the only one I know of, and it is hard-wired in already, but I'm not sure that this capability should be lightly tossed. Agreed. But do dynamically added