Trying hard not to open up another plugin

Actually, the NEXTDOC and PREVDOC were already added to link blog entries based on their numbering (see PREVDOC, NEXTDOC tags to automatically link blog entries (23 Aug 2005)) in the DocumentRelationsPlugin. Well and now I tried to render the latest comments section in the sidebar ignoring dupplicates. This is not possible - might I say - without the help of at least one extra plugin, be it the SpreadsheetPlugin, DBCachePlugin, FormQueryPlugin or whatever filtering and nesting tags outrageously. TWikiML is text replacement only. Point. And some extra programming logic which would be natural to php or jsp is not there. You have to do it in a perl plugin and invent some tag to display it on the surface. Compare it to taglibs for jsp or the like. But sometimes, you'd cry desperately for some serverside scripting within TWikiML just to do some little trick here and there. No, ok then we make the step move the NEXTDOC, PREVDOC tags out of the DocumentRelationsPlugin (which most possibly won't make it into the wild anyway) and collect some of the more difficult stuff that cannot be done using TopicFunctions in there. The tradeoff what means to use is not obvious in every case: use parametric INCLUDEs with SEARCHes (see TopicFunctions) vs. perl programming in the TWiki.BlogPlugin. Depends on complexity, efficiency and, well, some idea what the best way to go is. Kind of BestPractice. Maybe I'll compile some BestPractice that I tend to follow someday as soon as I've understood a little better what TWikiApplication programming is like and should be like.