Re: Q: Line-layout -> separating element-list creation / line-breaking

2006-08-23 Thread Patrick Paul
Andreas L Delmelle wrote: Hi all, Hello everyone ;-) I've been doing some thinking myself about the separation between element-list creation and actual line-breaking, and went wandering through the related sources. Just checking here if my initial estimates are correct. At first glan

Re: Q: Line-layout -> separating element-list creation / line-breaking

2006-08-23 Thread Andreas L Delmelle
On Aug 23, 2006, at 17:44, Patrick Paul wrote: Why not keep getNextKnuthElements() wich does the line breaking depending on a boolean switch ? Then depending on wether the element list already exists, the (modified) collectKnuthElements() method is called. FTM, such a boolean switch w

Re: Q: Line-layout -> separating element-list creation / line-breaking

2006-08-23 Thread Patrick Paul
Andreas L Delmelle wrote: On Aug 23, 2006, at 17:44, Patrick Paul wrote: Why not keep getNextKnuthElements() wich does the line breaking depending on a boolean switch ? Then depending on wether the element list already exists, the (modified) collectKnuthElements() method is called.

Re: Q: Line-layout -> separating element-list creation / line-breaking

2006-08-23 Thread Andreas L Delmelle
On Aug 23, 2006, at 20:16, Patrick Paul wrote: You are right. Thanks for the suggestion. I would even say that "determine" is misleading since the min and max content widths are calculated when getNextKnuthElements is called. So it maybe it would be better to name it getMinMaxContentWidth

Re: Q: Line-layout -> separating element-list creation / line-breaking

2006-08-23 Thread Simon Pepping
On Tue, Aug 22, 2006 at 11:35:12PM +0200, Andreas L Delmelle wrote: > > Hi all, > > > I've been doing some thinking myself about the separation between > element-list creation and actual line-breaking, and went wandering > through the related sources. Just checking here if my initial > est

Re: Q: Line-layout -> separating element-list creation / line-breaking

2006-08-23 Thread Patrick Paul
Andreas L Delmelle wrote: On Aug 23, 2006, at 20:16, Patrick Paul wrote: You are right. Thanks for the suggestion. I would even say that "determine" is misleading since the min and max content widths are calculated when getNextKnuthElements is called. So it maybe it would be better to n

Re: Q: Line-layout -> separating element-list creation / line-breaking

2006-08-23 Thread Patrick Paul
Simon Pepping wrote: On Tue, Aug 22, 2006 at 11:35:12PM +0200, Andreas L Delmelle wrote: Hi all, I've been doing some thinking myself about the separation between element-list creation and actual line-breaking, and went wandering through the related sources. Just checking here if my in

Re: Q: Line-layout -> separating element-list creation / line-breaking

2006-08-23 Thread Andreas L Delmelle
On Aug 23, 2006, at 21:16, Patrick Paul wrote: Simon Pepping wrote: On Tue, Aug 22, 2006 at 11:35:12PM +0200, Andreas L Delmelle wrote: I've been doing some thinking myself about the separation between element-list creation and actual line-breaking, and went wandering through the relat

Re: Q: Line-layout -> separating element-list creation / line-breaking

2006-08-23 Thread Patrick Paul
Andreas L Delmelle wrote: On Aug 23, 2006, at 21:16, Patrick Paul wrote: Simon Pepping wrote: On Tue, Aug 22, 2006 at 11:35:12PM +0200, Andreas L Delmelle wrote: I've been doing some thinking myself about the separation between element-list creation and actual line-breaking, and went

Re: Q: Line-layout -> separating element-list creation / line-breaking

2006-08-23 Thread Andreas L Delmelle
On Aug 24, 2006, at 02:39, Patrick Paul wrote: Andreas L Delmelle wrote: A more correct approach --a matter of taste?-- would be for the TableContentLM to 'collect' the accumulated list of its descendant LMs, perform the min/max-width calculation, update the LayoutContext, and send it