Changes between Version 2 and Version 3 of Wiki Macros
- Timestamp:
- Jul 25, 2010, 3:04:54 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Wiki Macros
v2 v3 8 8 9 9 == Using Macros == 10 Macro calls are enclosed in two ''square brackets''. Like Python functions, macros can also have arguments, a comma separated list within parentheses.11 10 12 Trac macros can also be written as TracPlugins. This gives them some capabilities that macros do not have, such as being able to directly access the HTTP request. 11 Macro calls are enclosed in two ''square brackets''. Like Python functions, macros can also have arguments, a comma separated list within parentheses. 12 13 === Getting Detailed Help === 14 The list of available macros and the full help can be obtained using the !MacroList macro, as seen [#AvailableMacros below]. 15 16 A brief list can be obtained via ![[MacroList(*)]] or ![[?]]. 17 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?]]. 19 20 13 21 14 22 === Example === … … 16 24 A list of 3 most recently changed wiki pages starting with 'Trac': 17 25 18 {{{ 19 [[RecentChanges(Trac,3)]] 26 ||= Wiki Markup =||= Display =|| 27 {{{#!td 28 {{{ 29 [[RecentChanges(Trac,3)]] 30 }}} 20 31 }}} 21 22 Display: 23 [[RecentChanges(Trac,3)]] 32 {{{#!td style="padding-left: 2em;" 33 [[RecentChanges(Trac,3)]] 34 }}} 35 |----------------------------------- 36 {{{#!td 37 {{{ 38 [[RecentChanges?(Trac,3)]] 39 }}} 40 }}} 41 {{{#!td style="padding-left: 2em;" 42 [[RecentChanges?(Trac,3)]] 43 }}} 44 |----------------------------------- 45 {{{#!td 46 {{{ 47 [[?]] 48 }}} 49 }}} 50 {{{#!td style="padding-left: 2em; font-size: 80%" 51 [[?]] 52 }}} 24 53 25 54 == Available Macros == … … 34 63 35 64 == Developing Custom Macros == 36 Macros, like Trac itself, are written in the [http://python.org/ Python programming language] .65 Macros, like Trac itself, are written in the [http://python.org/ Python programming language] and are developed as part of TracPlugins. 37 66 38 For more information about developing macros, see the [ wiki:TracDev development resources] on the main project site.67 For more information about developing macros, see the [trac:TracDev development resources] on the main project site. 39 68 40 69 41 == Implementation == 70 Here are 2 simple examples showing how to create a Macro with Trac 0.11. 42 71 43 Here are 2 simple examples on how to create a Macro with [wiki:0.11 Trac 0.11] have a look at source:trunk/sample-plugins/Timestamp.py for an example that shows the difference between old style and new style macros and also source:trunk/wiki-macros/READMEwhich provides a little more insight about the transition.72 Also, have a look at [trac:source:tags/trac-0.11/sample-plugins/Timestamp.py Timestamp.py] for an example that shows the difference between old style and new style macros and at the [trac:source:tags/trac-0.11/wiki-macros/README macros/README] which provides a little more insight about the transition. 44 73 45 74 === Macro without arguments === 46 It should be saved as `TimeStamp.py` as Trac will use the module name as the Macro name 75 To test the following code, you should saved it in a `timestamp_sample.py` file located in the TracEnvironment's `plugins/` directory. 47 76 {{{ 48 77 #!python … … 55 84 from trac.wiki.macros import WikiMacroBase 56 85 57 class Time stampMacro(WikiMacroBase):86 class TimeStampMacro(WikiMacroBase): 58 87 """Inserts the current time (in seconds) into the wiki page.""" 59 88 … … 61 90 url = "$URL$" 62 91 63 def expand_macro(self, formatter, name, args):92 def expand_macro(self, formatter, name, text): 64 93 t = datetime.now(utc) 65 94 return tag.b(format_datetime(t, '%c')) … … 67 96 68 97 === Macro with arguments === 69 It should be saved as `HelloWorld.py` (in the plugins/ directory) as Trac will use the module name as the Macro name 98 To test the following code, you should saved it in a `helloworld_sample.py` file located in the TracEnvironment's `plugins/` directory. 70 99 {{{ 71 100 #!python 101 from genshi.core import Markup 102 72 103 from trac.wiki.macros import WikiMacroBase 73 104 … … 87 118 url = "$URL$" 88 119 89 def expand_macro(self, formatter, name, args):120 def expand_macro(self, formatter, name, text, args): 90 121 """Return some output that will be displayed in the Wiki content. 91 122 92 123 `name` is the actual name of the macro (no surprise, here it'll be 93 124 `'HelloWorld'`), 94 ` args` is the text enclosed in parenthesis at the call of the macro.125 `text` is the text enclosed in parenthesis at the call of the macro. 95 126 Note that if there are ''no'' parenthesis (like in, e.g. 96 [[HelloWorld]]), then `args` is `None`. 127 [[HelloWorld]]), then `text` is `None`. 128 `args` are the arguments passed when HelloWorld is called using a 129 `#!HelloWorld` code block. 97 130 """ 98 return 'Hello World, args = ' + unicode(args) 99 100 # Note that there's no need to HTML escape the returned data, 101 # as the template engine (Genshi) will do it for us. 131 return 'Hello World, text = %s, args = %s' % \ 132 (Markup.escape(text), Markup.escape(repr(args))) 133 102 134 }}} 103 135 136 Note that `expand_macro` optionally takes a 4^th^ parameter ''`args`''. When the macro is called as a [WikiProcessors WikiProcessor], it's 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. On the contrary, when called as a macro, `args` is `None`. (''since 0.12''). 104 137 105 === {{{expand_macro}}} details === 106 {{{expand_macro}}} should return either a simple Python string which will be interpreted as HTML, or preferably a Markup object (use {{{from trac.util.html import Markup}}}). {{{Markup(string)}}} just annotates the string so the renderer will render the HTML string as-is with no escaping. You will also need to import Formatter using {{{from trac.wiki import Formatter}}}. 138 For example, when writing: 139 {{{ 140 {{{#!HelloWorld style="polite" 141 <Hello World!> 142 }}} 107 143 108 If your macro creates wiki markup instead of HTML, you can convert it to HTML like this: 144 {{{#!HelloWorld 145 <Hello World!> 146 }}} 147 148 [[HelloWorld(<Hello World!>)]] 149 }}} 150 One should get: 151 {{{ 152 Hello World, text = <Hello World!> , args = {'style': u'polite'} 153 Hello World, text = <Hello World!> , args = {} 154 Hello World, text = <Hello World!> , args = None 155 }}} 156 157 Note that the return value of `expand_macro` is '''not''' HTML escaped. Depending on the expected result, you should escape it by yourself (using `return Markup.escape(result)`) or, if this is indeed HTML, wrap it in a Markup object (`return Markup(result)`) with `Markup` coming from Genshi, (`from genshi.core import Markup`). 158 159 You can also recursively use a wiki Formatter (`from trac.wiki import Formatter`) to process the `text` as wiki markup, for example by doing: 109 160 110 161 {{{ 111 162 #!python 112 text = "whatever wiki markup you want, even containing other macros"113 # Convert Wiki markup to HTML, new style114 out = StringIO()115 Formatter(self.env, formatter.context).format(text, out)116 return Markup(out.getvalue())163 text = "whatever wiki markup you want, even containing other macros" 164 # Convert Wiki markup to HTML, new style 165 out = StringIO() 166 Formatter(self.env, formatter.context).format(text, out) 167 return Markup(out.getvalue()) 117 168 }}}