Separate Footer and Header

[jferard]

The FooterHeader class stores both header and footer, but we need to check the type (h or f) at some places. This check could be avoided with two classes. Perhaps a design like this: keep the FooterHeader class but let it store an instance of FooterOrHeader interface that gathers the specific code of each "type".

[jferard]

Current situation:

• FooterHeader has a type (Footer/Header), a content (RegionFooterHeader/SimpleFooterHeader) and a style.
• FooterHeaderContent has a type (Footer/Header)
• FooterHeaderStyle has a type (Footer/Header)
• FooterHeaderContent may be a RegionFooterHeader (with three blocks of text) or a SimpleFooterHeader (with one block of text).
• FooterHeader has the following methods: addEmbeddedStylesToStylesElement (mode or not), appendFooterHeaderStyleXMLToAutomaticStyle, appendXMLToMasterStyle.

[jferard]

Some ideas:

• A Header or a Footer is a PageSection with a PageSectionPosition
• A PageSection may be simple or have regions (left, center, right)