[EMAIL PROTECTED] wrote: >The other thing I've worked on is in the actual LayoutManager logic. >I've got this concept of a "BreakPosition" and have some code written at >the inline level (text, inline, line). The idea is that instead of an LM >calling generateAreas on its child LM, it repeatedly calls >"getNextBreakPosition". It then uses the returned BreakPosition >information to decide on the best break. Only then does it ask the child >LM to actually make the Areas necessary to break at the point. > Karen,
I like the idea of BreakPosition being constantly updated (see my notes on co-routines). What do you mean by "decide on the best break"? What sort of things do you see going into that decision that cannot, in essence, be decided by the child? Are you thinking about the resolution of ambiguous situations which require knowledge of partial results from a number of parallel area subtrees? Peter --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
