The default navigation scheme that is shipped with the
NatSkin
only works out for small to medium numbers of webs but does not
work out nicely on a large set of webs and even worse on subwebs.
This is actually a known issue for quite some time and Wohali
concluded that
NatSkin is tailored for private use only (...).
Meredith and others stumbled over that too but till now I didn't
address that in one of the other way. Actually, this is not a direct
issue of the
NatSkin or any other skin as they only include some
topic's content into a sidebar area.
Subwebs are still not well integrated into TWiki, IMHO, and
treated quite stepmotherly \footnote{Take the naming confusion as an other example: web.subweb.topic= vs. web/subweb.topic vs ...}.
But as TWiki4 rolls out more people
start using hierarchical webs but wonder why there's no good navigation scheme
for that. The
ONLY tml feature that I have found in TWiki that addresses
subwebness is the
$indentedname
format string feature of the WEBLIST tag,
a thing not usable at all for
TWikiApplications. So there's no easy way
to
- get all subwebs or
- get all sibling webs
whatsoever, which is needed to render
any sort of enhanced navigation.
So this bug item is kind of a
NatSkin issue but also a TWiki engine one.
In the past I did
not ask for extra gear to be implemented in the
core to support
NatSkin and I've rolled my own stuff in the
NatSkinPlugin.
I could do so easily now and implement an enhanced NATWEBLIST tag that
does what I want. But
PatternSkin and everybody should just get what is
missing in general. Let's see if something happens ...
--
See also
Can you give some specific enhancement requests please? This is all rather vague.
CC
I am going to be rude and set this No Action. The report is not at all specific and cannot be actioned by anyone.
But the two links above to two almost identical proposals are very relevant enhancements.
If you want more Michael you have to raise bug items that are specific. More generic and general discussions belong to Codev.
KJL