Re: (Peter) read-only BitSet usage

Glen Mazza wrote: Peter, I just asked Finn a similar question in Bugzilla, I also need to ask you to make sure I'm understanding the BitSets correctly. In Alt-Design's FOPropertySets there are many read-only BitSets. (These are somewhat different from Finn's, BTW--he created a BitSet for each FO

Re: (Victor et al) Re: Performance improvements.

Victor Mote wrote: Peter B. West wrote: If we go towards integer representation, properties in the API will always be represented by integers. By looking at this particular signature, we are not locking ourselves in. We can add other signatures if the need arises, but they can be extensions of

Re: (Victor et al) Re: Performance improvements.

Victor Mote wrote: Peter B. West wrote: Glen Mazza wrote: --- "Peter B. West" <[EMAIL PROTECTED]> wrote: See above. In alt.design, all compounds are shorthands, and all shorthands are presumed to have been resolved into their components during FO Tree building. BTW, does Alt-Design already

RE: (Victor et al) Re: Performance improvements.

Peter B. West wrote: > If we go towards integer representation, properties in the API will > always be represented by integers. By looking at this particular > signature, we are not locking ourselves in. We can add other signatures > if the need arises, but they can be extensions of the basic ca

Re: (Victor et al) Re: Performance improvements.

Victor Mote wrote: Peter B. West wrote: Victor Mote wrote: Yes, yes, yes. Since we are trying to eliminate the need for unnecessary object creation, why create a MinOptMax object? Why not just return the three resolved values in separate methods. Anything that uses the information will have to s

DO NOT REPLY [Bug 25512] - [PATCH] Test all breakposs for suppressible content

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

DO NOT REPLY [Bug 25512] - [PATCH] Test all breakposs for suppressible content

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

DO NOT REPLY [Bug 16626] - Hyphenation causing java.io.IOException error

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

cvs commit: xml-fop/src/java/org/apache/fop/layoutmgr LineLayoutManager.java

gmazza 2003/12/15 14:39:01 Modified:src/java/org/apache/fop/layoutmgr LineLayoutManager.java Log: Hyphenation/Quotation problem fixed ("quoted strings" not breaking properly.) Patch #25512 by Simon Pepping (spepping at leverkruid dot nl). Revision ChangesPath 1.7

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

Finn Bock wrote: 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. Finn, I've been trying to find an Eclipse-clean way to solve

(Peter) read-only BitSet usage

Peter, I just asked Finn a similar question in Bugzilla, I also need to ask you to make sure I'm understanding the BitSets correctly. In Alt-Design's FOPropertySets there are many read-only BitSets. (These are somewhat different from Finn's, BTW--he created a BitSet for each FO to indicate those

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 . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE: FOs and Areas

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. I don't claim

RE: (Victor et al) Re: Performance improvements.

--- Victor Mote <[EMAIL PROTECTED]> wrote: > The previous posting seems to indicate that the > properties have been > decomposed, the chronologically latter posting seems > to indicate that the > shorthand retains its shorthand character. I think Peter and I were talking about inner-to-FO propert

RE: (Victor et al) Re: Performance improvements.

Peter B. West wrote: > Glen Mazza wrote: > > --- "Peter B. West" <[EMAIL PROTECTED]> wrote: > > > >>See above. In alt.design, all compounds are > >>shorthands, and all > >>shorthands are presumed to have been resolved into > >>their components > >>during FO Tree building. > >> > > > > > > BTW, do

RE: (Victor et al) Re: Performance improvements.

Peter B. West wrote: > Victor Mote wrote: > > Yes, yes, yes. Since we are trying to eliminate the need for unnecessary > > object creation, why create a MinOptMax object? Why not just return the > > three resolved values in separate methods. Anything that uses the > > information will have to sepa

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

[Jeremias Maerki] I've removed the embedded Ant in HEAD. I rewrote build.bat and build.sh to call a separately installed Ant. Instructions will be given on the command-line if Ant cannot be found. Now that ant.jar has been removed, the project is slightly less friendly to eclipse since ant.jar is

Re: FOs and Areas

--- "Peter B. West" <[EMAIL PROTECTED]> 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 f

FOs and Areas

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. As I recall, in the original original ve

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 . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu