On Mon 19 Mar 2007, Nick Burch <openguides(a)gagravarr.org> wrote:
They weren't placed into the navbar for reasons of
css control. If they
were within a div with id=navbar, it became significantly harder to give
different styling to these than the rest of the navbar.
One workaround might be to do (id names probably want to be better):
<div id="navbar">
[...]
<div id="common-links">
I wouldn't say that's a workaround - I'd say that's the correct way to
do it! Well, modulo the "main-navbar" thing; it would be better to
give each navbar "module" its own id. I don't understand why you're
special-casing the categories/locales - surely people are just as
likely to want to style other elements of the navbar as they are to
want to style these particular elements. But anyway, yes, I'll move
them into the navbar, if this is the only reason you left them out.
The other
thing is that they should really be specified in wiki.conf,
since (a) they should be configurable, and (b) they need to be run
through the node_name_to_node_param method of the formatter before
being plonked on the page.
Dom had a think about this, and I think decided we'd need to extend
Config::Tiny, or use something else, to be able to do it properly. Dom -
am I remembering you comments correctly?
Bob (um, or was it doop? One of them, anyway) suggested that we could
move to using YAML instead of Config::Tiny.
Kake