Edgewall Software

Changes between Initial Version and Version 3 of Ticket #4140


Ignore:
Timestamp:
Feb 9, 2007, 7:04:49 PM (17 years ago)
Author:
Christian Boos
Comment:

Related to #4431, but this ticket is about getting the specifics of PageOutline right in the case of the parser/formatter split.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #4140

    • Property Severity minor → normal
    • Property Priority low → normal
    • Property Keywords parser formatter macro outline added
    • Property Milestone → 0.11
    • Property Owner changed from Jonas Borgström to Christian Boos

  • Ticket #4140 – Description

    initial v3  
    11Hi,
    22
    3 Macros like the PageOutline make use of the OutlineFormatter to build a table of contents. But it seems awfully inneficient that you'll have to run through the page twice in order to do just that. How about having the standard Formatter build the outline[] array just like the OutlineFormatter does, so that one could refer to it at anytime during a macro? It'd be a really simple change too, merging both behaviours into one class. Then you'd just call the macros at the end of the wiki pages wherever you wanted an outline to be generated.
     3Macros like the !PageOutline make use of the !OutlineFormatter to build a table of contents. But it seems awfully inefficient that you'll have to run through the page twice in order to do just that. How about having the standard Formatter build the outline[] array just like the !OutlineFormatter does, so that one could refer to it at anytime during a macro? It'd be a really simple change too, merging both behaviours into one class. Then you'd just call the macros at the end of the wiki pages wherever you wanted an outline to be generated.
    44
    55I'd be glad to submit this, if you require an extra hand,