Glen Mazza wrote:
> [...]
> I think if we do this, it will allow for more simplifications and
> insights into the layout coding, and make it easier to understand. I
> don't think we can afford the duplication as-is--my experience so far
> with FOP is that simplifying engenders more simplifications, while lard
> ends up begetting more lard.
It seems a good plan; maybe it would be better to wait a little time, so
that the code is more or less stabilized.
As we are talking about code simplifications: at the moment there are
classes for the sequences of elements (KnuthSequence, extended by
Paragraph and BlockSequence) and for the breaking algorithms
(BreakingAlgorithm, PageBreakingAlgorithm, LineBreakingAlgorithm).
The sequences and the algorithms are tightly coupled, and they share (or
duplicate) many parameters: what about having a class with both the
sequence of elements and its specific breaking method?
Regards
Luca
