Re: footer navigation headers

[Per Bothner]

I think this link shows a good default output (with no configuration settings),
assuming --split=section (and of course some non-default css):

http://per.bothner.com/tmp/DomTerm-txjs/Wire-byte-protocol.html
<
There is a navigation header for each node, and a single navigation footer.

You can remove excess headers with CSS:
 
div.section div.header { display: none }
div.subsection div.header { display: none }
div.subsubsection div.header { display: none }

and the result is reasonable.

The way I did it (see attached patch) is probably not the right one.
Things will probably misbehave for certain configuration settings.
WORDS_IN_PAGE is disabled, for one.  (Though I don't think we should be obliged
to support every existing configuration setting in the same way as before.
It's ok to remove some little-used settings, especially if they no longer make 
sense.)

For what it's worth, what I tried was to split _default_format_element_footer
into two parts:

(1) _default_format_element_footer is called at the end of each node,
as before.  It emits rules, footnotes, but no navigation buttons.

(2) _default_format_element_footer is emitted at the end of each page.
It emits navigation buttons.  It is actually called in _convert_heading_command
at the top of the page, which is why WORDS_IN_PAGE is ignored, but that
could be changed with some more complicated logic.

--
        --Per Bothner
per@bothner.com   http://per.bothner.com/

footer-navigation2.patch
Description: Text Data