close Warning: Can't synchronize with repository "(default)" (The repository directory has changed, you should resynchronize the repository with: trac-admin $ENV repository resync '(default)'). Look in the Trac log for more information.

Changes between Version 2 and Version 3 of WikiMacros


Ignore:
Timestamp:
2015-05-25T08:23:07-07:00 (10 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WikiMacros

    v2 v3  
    33[[PageOutline]]
    44
    5 Trac macros are plugins to extend the Trac engine with custom 'functions' written in Python. A macro inserts dynamic HTML data in any context supporting WikiFormatting.
     5Trac macros are plugins to extend the Trac engine with custom 'functions' written in Python. A macro inserts dynamic HTML data in any context supporting WikiFormatting. Its syntax is `[[macro-name(optional-arguments)]]`.
    66
    7 Another kind of macros are WikiProcessors. They typically deal with alternate markup formats and representation of larger blocks of information (like source code highlighting).
     7The WikiProcessors are another kind of macros. They typically deal with alternate markup formats and transformation of larger "blocks" of information (like source code highlighting). They are used for processing the multiline `{{{#!wiki-processor-name ... }}}` blocks.
    88
    99== Using Macros ==
     
    1414The list of available macros and the full help can be obtained using the !MacroList macro, as seen [#AvailableMacros below].
    1515
    16 A brief list can be obtained via ![[MacroList(*)]] or ![[?]].
     16A brief list can be obtained via `[[MacroList(*)]]` or `[[?]]`.
    1717
    18 Detailed help on a specific macro can be obtained by passing it as an argument to !MacroList, e.g. ![[MacroList(MacroList)]], or, more conveniently, by appending a question mark (?) to the macro's name, like in ![[MacroList?]].
     18Detailed help on a specific macro can be obtained by passing it as an argument to !MacroList, e.g. `[[MacroList(MacroList)]]`, or, more conveniently, by appending a question mark (`?`) to the macro's name, like in `[[MacroList?]]`.
    1919
    2020
     
    102102    def expand_macro(self, formatter, name, text):
    103103        t = datetime.now(utc)
    104         return tag.b(format_datetime(t, '%c'))
     104        return tag.strong(format_datetime(t, '%c'))
    105105}}}
    106106
     
    148148For example, when writing:
    149149{{{
    150 {{{#!HelloWorld style="polite"
     150{{{#!HelloWorld style="polite" -silent verbose
    151151<Hello World!>
    152152}}}
     
    160160One should get:
    161161{{{
    162 Hello World, text = <Hello World!> , args = {'style': u'polite'}
     162Hello World, text = <Hello World!> , args = {'style': u'polite', 'silent': False, 'verbose': True}
    163163Hello World, text = <Hello World!> , args = {}
    164164Hello World, text = <Hello World!> , args = None