Keiron Liddle wrote:
>
....
>
> Then after that I will see about handling the element child constraints (I
> haven't worked out how this should be done yet, any ideas) and doing a
> similar thing (to be impl.) with the rest of the elements that we don't
> have yet.
>
For things like tables, I had been thinking of handling child type
checking in the addChild method. That way we can give messages early in
the game and also do special things like handling different children in
special ways. An example is when table-cell FO are directly under a
table-body (or header or footer) rather than in a table-row. In that
case, I think it would be better to create a "fake" row to hold them.
That kind of work is logically done during FO tree building.
However that's rather a piecemeal approach. Perhaps it would be good to
describe (schema? DTD?) the possible child types and have the base class
implementation do that kind of checking.
Just my .02 euros!
Karen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
