DO NOT REPLY [Bug 25480] - [PATCH] Experimental performance improvements.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25480. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

Re: [PROPOSAL] Remove ant.jar and build.bat/sh

[me] Now that ant.jar has been removed, the project is slightly less friendly to eclipse since ant.jar is required by the files in org.apache.fop.tools.anttasks. It is easily solved locally, I just wanted to point it out. [Peter B. West] Finn, I've been trying to find an Eclipse-clean way to

DO NOT REPLY [Bug 25563] New: - [PATCH] toString() method compound property value classes in datatypes.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25563. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 25563] - [PATCH] toString() method compound property value classes in datatypes.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25563. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 25480] - [PATCH] Experimental performance improvements.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25480. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

Re: FOs and Areas

Victor Mote wrote: Peter B. West wrote: Herewith some notes on the tortured relationship between the two. As I don't know much about layout in HEAD, I am hoping that differences and (hopefully) correspondences between my ideas and the HEAD redesign can be pointed out by wiser HEADs than mine.

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

[EMAIL PROTECTED] wrote: gmazza 2003/12/14 17:07:50 Modified:.build.xml src/codegen propinc.xsl Added: src/codegen constants.xml constants.xsl foelements.xml src/java/org/apache/fop/fo Constants.java Removed: src/codegen allprops.xml

Re: [PROPOSAL] Remove ant.jar and build.bat/sh

Finn Bock wrote: [me] Now that ant.jar has been removed, the project is slightly less friendly to eclipse since ant.jar is required by the files in org.apache.fop.tools.anttasks. It is easily solved locally, I just wanted to point it out. [Peter B. West] Finn, I've been trying to find an

Re: [PROPOSAL] Remove ant.jar and build.bat/sh

Finn Bock wrote: The same way that I locally solved the Jimi and JAI dependency: copy d:\java\ant-1.5.1\lib\ant.jar lib and adding the .jar to the Java Build Path/Libraries. You don't need the copy, you can add external jars as well. J.Pietschmann

RE: FOs and Areas

-Original Message- From: Peter B. West [mailto:[EMAIL PROTECTED] snip / I realize the tone of this posting has not been entirely irenic. I'll try harder. As a kind-of headz up (seen my understanding, for the moment, is too little to add anything interesting to the discussion

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

-Original Message- From: Peter B. West [mailto:[EMAIL PROTECTED] 1.1 xml-fop/src/java/org/apache/fop/fo/Constants.java Index: Constants.java === /* $Id: Constants.java,v 1.1 2003/12/15

RE: FOs and Areas

Peter B. West wrote: It seems to me, however, that the key to 1) solving the layout dependencies of FO property expressions, and 2) reducing footprint, particularly for those long documents which are naturally expressed with very large fo:flow trees in a few page-sequences, is to have the

Re: FOs and Areas

Victor Mote wrote: I guess you are saying that a page-sequence will use too much memory (??). Again, this is a non-issue. Just use a different LayoutStrategy that is more eager. This can be an issue. In a real world file I benchmarked (rendered to 58 pages), the FO tree for the second page

What should I be doing ?

As I mentioned off-line to another list member, I have some questions about the progress of the current Fop development effort. So far: i) I have made a few measurements and reconfirmed some other peoples opinions about possible areas for improvement. ii) I have also proof-read some code

Re: What should I be doing?

More patches, please, particularly in layout and renderers--run the example files on FOP 0.20.5 and 1.0dev--catch the deltas (there's dozens) and send us patches to the 1.0 code, one-by-one. I'm currently working on converting FOP from strings to int's. Finn's work Alt-Design has given me a

Re: FOs and Areas

Victor, The statements are getting extreme. Let's just agree to differ. I'm happy to let my code and the design that underlies it do my talking. Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html