Responses below. -----Original Message----- From: Keiron Liddle [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 21, 2002 3:08 AM To: FOP Subject: RE: Getting breaks: revisited
Hi Rhett, >> On Wed, 2002-11-20 at 16:44, Rhett Aultman wrote: > I may be green, but I did spot some of this a couple weeks ago, and it went mostly >unnoticed. While writing this email, I downloaded another CVS snapshot and the >super-simple test document from bug #8778, which is probably the simplest of all the >i-loop cases, and ran it again...it's the same thing I saw when I last brought this >up. Give me a chance, it is by no means finished and to suggest that if it doesn't do it properly now it never will is going a bit far. << I'm not suggesting that. I am, however, attempting to explore potential solutions. I'm asking you what you intend to do about it, since you have insisted that the various ideas offered are either bad or unnecessary. >> Currently it does not handle the situation where it cannot find any normal break in a page, so if the page is small it will get an infinite loop. I have never said it will handle anything you throw at it. I am talking about design anyway. The design will handle that situation. << I'm talking about design, too. This entire thread is about design. I'm citing examples because they elucidate a general, design-related issue. To be frank, saying "the design will handle this" is much like saying "the proof is left as an example for the reader." I'm attempting to explore *how* such a design would from a general position. This is a highly relevant topic. Victor, Peter, and I have all offered ideas of ways to resolve such matters, and you too seem to have more musings on it. I'd enjoy hearing them. Do you have a general solution for discarding constraints that get in the way of layout? >> Easy: there is currently no best break (ie. it is null) therefore we still need to find a break. So the best break will be after the block. It will place that on the page and finish document. If there are keeps it should probably go further until it can be sure it will find the best breaks for all things kept together. << IIRC, in my "8778 experiment", the break being offered was never null. The best break is always being offered, but the best break is at the beginning of the offending block. Either way, this resolves only the most trivial of the examples without paying attention to the greater issue, which is that such layout issues are rooted in constraints that conflict. Is your intention to wait for such cases to come in and just write special-case code for each and every one of them at the time? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
