--- "Andreas L. Delmelle" <[EMAIL PROTECTED]> wrote:Except for ... (see above)? Hmm... Why would we even *need* *two* *different* LMs? Don't get me wrong: I'm *not* encouraging you to merge the two classes completely ;-P
Still can't put my finger on it, but something seems not quite OK with having two separate LM classes that 'do the same thing, regardless of the input coming from an fo:flow or an fo:static-content'
No, no, no...
BodyRegionLM will handle fo:flow and fo:static-content equivalently.
SideRegionLM will handle fo:flow and fo:static-content equivalently.
BodyRegionLM and SideRegionLM would handle these objects very differently.
Forgive my naivet�, but why not just have something like:
LayoutManager(), and inside that determine whether it's body, side or flow, or whatever?
I'm thinking something along the lines of:
LayoutManager('region-body',...)
LayoutManager('region-start',...)
LayoutManager('region-end',...)or something. That way, it's all in one (since it can apparently be repurposed anyway, with fo:flow being stuck into fo:static-content, and vice versa).
Just a thought...
Web Maestro Clay -- <[EMAIL PROTECTED]> - <http://homepage.mac.com/webmaestro/> My religion is simple. My religion is kindness. - HH The 14th Dalai Lama of Tibet
