On Jul 20, 2007, at 01:17, Manuel Mall wrote:
Nothing. I just don't like those being bound to the text either...
Why duplicate the font-, alignment- and other info on the FOText
descendant? Either there is no need to store them at the higher level
at all, or they are always available from the parent so there is no
compelling reason to bind them to the FOText as well.
The main reason is that our object hierarchy does not easily allow to
retrieve that without messy tests instanceof tests and typecasts. If
you want to re-architect the object hierarchy within the fo tree just
to avoid the need to bind against FOText, please by my guest.
Well, it has been on my mind to do so, actually, albeit not just to
avoid this binding.
No priority so far. It's working. Never mind if the design is
suboptimal --at least, nobody else seems to mind. :-)
<snip />
My point exactly.
Good, so why all the fuss about this particular relatively small
commit
then?
Hmm, Fuss? :-/ I wasn't making any fuss... Was I?
Cheers
Andreas
