Changes between Initial Version and Version 1 of WikiMacros

Jul 30, 2021, 7:40:25 AM (16 months ago)



  • WikiMacros

    v1 v1  
     1= Trac Macros
     5'''Trac macros''' extend Trac with custom functionality. Macros are a special type of plugin and are written in Python. A macro generates HTML in any context supporting WikiFormatting.
     7The macro syntax is `[[macro-name(optional-arguments)]]`.
     9'''WikiProcessors''' are another kind of macro, commonly used for source code highlighting using a processor like `!#python` or `!#apache`:
     17== Using Macros
     19Macro calls are enclosed in double-square brackets `[[..]]`. Like Python functions macros can have arguments, which take the form of a comma separated list within parentheses `[[..(,)]]`. A common macro used is a list of the 3 most recent changes to a wiki page, or here, for example, all wiki pages starting with 'Trac':
     21||= Wiki Markup =||= Display =||
     23  {{{
     24  [[RecentChanges(Trac,3)]]
     25  }}}
     27{{{#!td style="padding-left: 2em;"
     31=== Getting Detailed Help
     33The list of available macros and the full help can be obtained using the !MacroList macro, see [#AvailableMacros below].
     35A brief list can be obtained via `[[MacroList(*)]]` or `[[?]]`.
     37Detailed 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?]]`.
     39== Available Macros
     43== Contributed macros
     45The [ Trac Hacks] site provides a large collection of macros and other Trac [TracPlugins plugins] contributed by the Trac community. If you are looking for new macros, or have written one that you would like to share, please visit that site.
     47== Developing Custom Macros
     49Macros, like Trac itself, are written in the [ Python programming language] and are a type of [TracPlugins plugin].
     51Here are 2 simple examples showing how to create a Macro. For more information about developing macros, see the [trac:TracDev development resources] and [trac:browser:branches/1.4-stable/sample-plugins sample-plugins].
     53=== Macro without arguments
     55To test the following code, copy it to `` in the TracEnvironment's `plugins/` directory.
     58from trac.util.datefmt import datetime_now, format_datetime, utc
     59from trac.util.html import tag
     60from import WikiMacroBase
     62class TimestampMacro(WikiMacroBase):
     63    _description = "Inserts the current time (in seconds) into the wiki page."
     65    def expand_macro(self, formatter, name, content, args=None):
     66        t = datetime_now(utc)
     67        return tag.strong(format_datetime(t, '%c'))
     70=== Macro with arguments
     72To test the following code, copy it to `` in the TracEnvironment's `plugins/` directory.
     75from trac.util.translation import cleandoc_
     76from import WikiMacroBase
     78class HelloWorldMacro(WikiMacroBase):
     79    _description = cleandoc_(
     80    """Simple HelloWorld macro.
     82    Note that the name of the class is meaningful:
     83     - it must end with "Macro"
     84     - what comes before "Macro" ends up being the macro name
     86    The documentation of the class (i.e. what you're reading)
     87    will become the documentation of the macro, as shown by
     88    the !MacroList macro (usually used in the WikiMacros page).
     89    """)
     91    def expand_macro(self, formatter, name, content, args=None):
     92        """Return some output that will be displayed in the Wiki content.
     94        `name` is the actual name of the macro (no surprise, here it'll be
     95        `'HelloWorld'`),
     96        `content` is the text enclosed in parenthesis at the call of the
     97          macro. Note that if there are ''no'' parenthesis (like in, e.g.
     98          [[HelloWorld]]), then `content` is `None`.
     99        `args` will contain a dictionary of arguments when called using the
     100          Wiki processor syntax and will be `None` if called using the
     101          macro syntax.
     102        """
     103        return 'Hello World, content = ' + unicode(content)
     106Note that `expand_macro` optionally takes a 4^th^ parameter ''`args`''. When the macro is called as a [WikiProcessors WikiProcessor], it is also possible to pass `key=value` [WikiProcessors#UsingProcessors processor parameters]. If given, those are stored in a dictionary and passed in this extra `args` parameter. When called as a macro, `args` is `None`.
     108For example, when writing:
     110{{{#!HelloWorld style="polite" -silent verbose
     111<Hello World!>
     115<Hello World!>
     118[[HelloWorld(<Hello World!>)]]
     121One should get:
     123Hello World, text = <Hello World!>, args = {'style': u'polite', 'silent': False, 'verbose': True}
     124Hello World, text = <Hello World!>, args = {}
     125Hello World, text = <Hello World!>, args = None
     128Note that the return value of `expand_macro` is '''not''' HTML escaped. Depending on the expected result, you should escape it yourself (using `return Markup.escape(result)`), or if this is indeed HTML, wrap it in a Markup object: `return Markup(result)` (`from trac.util.html import Markup`).
     130You can also recursively use a wiki formatter to process the `content` as wiki markup:
     133from import format_to_html
     134from import WikiMacroBase
     136class HelloWorldMacro(WikiMacroBase):
     137    def expand_macro(self, formatter, name, content, args):
     138        content = "any '''wiki''' markup you want, even containing other macros"
     139        # Convert Wiki markup to HTML
     140        return format_to_html(self.env, formatter.context, content)