On Tue, 20 Sep 2005 04:33 pm, Luca Furini wrote: > Andreas L Delmelle wrote: > > BTW: Is it a correct assessment that implementing this should turn > > out to be far simpler than fixed page-sizes? IIC, theoretically, > > the whole page-breaking algorithm can be ignored for indefinite > > page-heights. getAvailableBPD() would always return, say, > > Integer.MAX_VALUE? > > I don't think the breaking algorithm can be completely ignored, but > it's a good idea to have getAvailableBPD() return an almost infinite > value. >
Wonder if we would run into a limitation here with respect to using int and mpt: Maxint = 2147483647mpt ~ 2147483pt ~ 30000in ~ 75000cm ~ 2500 A4 pages vertically. Probably not as this would be all one page kept in memory before rendering. An out of memory exception is the more likely outcome :-). > Once the PageBreakingAlgorithm has created the single > PageBreakPosition, it would be possible to use the stored difference > in order to set the correct page height (otherwise the page would > have height = > Integer.MAX_VALUE even if it contains just a few lines). > > Regards > Luca Manuel
