In turn I apologize for the delay in my response.
Thank you for the answers. I am working towards "the splitting",
following your precious advice.
I will fax my ICLA by next tuesday.
I will be offline for the week-end but will continue working on my
laptop. I have to start sending you my code some time soon!
Thank you,
Patrick Paul
Jeremias Maerki wrote:
Sorry for the delay. Too much going on right now.
On 19.07.2006 01:37:57 Patrick Paul wrote:
Just to make sure I understand things correctly, the element list
construction needs to be seperated from the line breaking algorithm ONLY
when using it for auto table layout ?
I'd state it differently: Element list contruction needs to be separated
from the line breaking algorithm in order so the auto table layout can
access the element lists before the line breaking can occur. ATM, yes,
it's only used for auto table layout.
I am asking this because the
LineLayoutManager is not used exclusively by the TableLayoutManager, right ?
Yes.
If this is correct, how do you recommend I do this split ? Should I
create a new "LineLayoutManager" ? Or should I actually change the
LineLayoutManger and reflect the change anywhere it is necessary in the
code ?
No, don't create a new LineLayoutManager. The existing one needs to be
adjusted. getNextKnuthElements() in the context of the LineLayoutManager
means returning a block-level element list which cannot be provided at
the point where you need the inline-level element lists. So you may need
to come up with a mechanism that you can call on the block-level LMs
inside the table-cell so they descend down to the LineLayoutManagers and
issue the construction of the inline element lists. Ideally, the
LineLayoutManagers won't have to recreate the element lists when the
real getNextKnuthElements() call happens but they will automatically
create those element lists when they are not available, yet (i.e. in
cases outside a table).
HTH
BTW, Patrick, when I checked the ICLA status of you and Vincent I saw
that you still don't have an ICLA on file with the ASF. Please sign and send
(i.e. fax) one to the ASF secretary:
http://www.apache.org/licenses/#clas
Thanks.
Patrick Paul
Jeremias Maerki wrote:
Here are my notes on AutoTableLayout I collected last year in case you
haven't seen them, yet. One of the more important parts will be to split
up the element list construction and the line breaking in
LineLayoutManager, because you can't do the line breaking as long as you
don't know the available IPD.
http://wiki.apache.org/xmlgraphics-fop/AutoTableLayout
HTH
On 18.07.2006 21:30:39 Patrick Paul wrote:
Great this is exactly what I needed, just didn't know where to look
(just as I received your message I had coded my own little routine).
Now I need a little pointer on how best to fly over table rows without
"touching" them. I have some idea but I would prefer to check with the
experts.
Thank you,
Patrick
Andreas L Delmelle wrote:
On Jul 18, 2006, at 20:46, Patrick Paul wrote:
Hi Patrick,
I've been "playing" a little with the TableLayoutManager code.
If someone would be kind enough to point me in the right direction
on how to determine the full length of each element list, it would
help a great deal.
Depends on what you mean by 'length': if you mean content-length,
have a look at layoutmgr.ElementListUtils.calcContentLength().
If you mean number of elements --but you don't, do you? ;)
Cheers,
Andreas
Jeremias Maerki
Jeremias Maerki
