Done:
http://trac.tiddlywiki.org/changeset/10631
http://fnd.lewcid.org/tmp/ListNavMacro.html
> However, installing brought an instant slowing of performance, which
> could be caused because the 'All' listing is always rendered at first.
All items have to be are rendered initially. The jQuery listnav plugin
just hides items dynamically (i.e. they remain present in the DOM).
> Also, on 'all' I have two dots in front of each listed item.
Not sure what you mean by that - got a test case?
-- F.
Seems to work for me (tried it on Alex's document) - test case?
> Would be really good if forced links could be sorted without the
> proceeding braces..
The jQuery listnav plugin just takes whatever the list item's text is.
If wikification works, so should sorting.
> I've produced a test case
You have blank lines in your source listing, which are not ignored by
the plugin, thus creating empty list items (which leads to the
appearance of two bullet points).
-- F.
That's the magic of test cases.
That's not a minimal test case, I'm afraid:
http://webkit.org/quality/reduction.html
> Using an alternative <<list filter [tag[..]]>> - because the internal
> filter only recognizes CamelCases
That sounds unlikely (though not impossible). I'm not quite following
you though...
-- F.
The wikification is optional, so you need to add wikified:true as macro
parameter. (Sorry, I kinda took that part for granted.)
> The empty list items are not produced under the tabs.
That's right, because they don't start with any letter.
> Looking under 'A' , Aaker [1] is rendered without the brackets, unlike under
> 'ALL' however it is not rendered as a link.
Actually, that particular entry is not rendered under "A" at all unless
wikified, because it starts with "[".
As explained to Wolfgang, the categorization and sorting are based on
what's being rendered, not on the raw wikitext.
-- F.