On 2001.11.22 11:58 Jeremias Maerki wrote: > Hello Keiron > > Aaahh, sounds good to me. Just to be sure: For layout problems such as > overflows the FO "overflow" property tells the user agent if an > error condition has to be signaled. But what about things such as images > that couldn't be loaded. I can imagine that this might not always be a > condition to throw an Exception, especially maybe for FO editors using > FOP for preview or during development, when you don't want FOP to stop > as soon as problem occurs. In this case the user agent would probably be > configured to halt or continue when a problem occurs. And the user agent > would be the central point of problem handling instead my idea of a > ProblemListener. Right?
Yes, that sounds like the general idea. If we try to minimise and centralise the way that people can configure/debug/use/customise/embed etc. then it should make things easier. There is certainly more thought and design that will need to go into getting it right. > And by the way: I'm really happy to see MessageHandler go! One more step > towards a multithreading-friendly FOP. This is great! Still more to go but each step helps. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
