Changes between Version 3 and Version 4 of WikiMacros
- Timestamp:
- 2015-04-20T20:49:42+02:00 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WikiMacros
v3 v4 1 = Trac Macros =1 = Trac Macros 2 2 3 3 [[PageOutline]] 4 4 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. 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. Its syntax is `[[macro-name(optional-arguments)]]`. 6 6 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).7 The 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. 8 8 9 == Using Macros ==9 == Using Macros 10 10 11 Macro calls are enclosed in two ''square brackets'' . Like Python functions, macros can also have arguments, a comma separated list within parentheses.11 Macro calls are enclosed in two ''square brackets'' `[[..]]`. Like Python functions, macros can also have arguments, a comma separated list within parentheses `[[..(,)]]`. 12 12 13 === Getting Detailed Help === 13 === Getting Detailed Help 14 14 15 The list of available macros and the full help can be obtained using the !MacroList macro, as seen [#AvailableMacros below]. 15 16 16 A brief list can be obtained via ![[MacroList(*)]] or ![[?]].17 A brief list can be obtained via `[[MacroList(*)]]` or `[[?]]`. 17 18 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 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 21 === Example 20 22 21 22 === Example === 23 24 A list of 3 most recently changed wiki pages starting with 'Trac': 23 A list of the 3 most recently changed wiki pages starting with 'Trac': 25 24 26 25 ||= Wiki Markup =||= Display =|| … … 48 47 }}} 49 48 }}} 50 {{{#!td style="padding-left: 2em; font-size: 80%" 51 [[?]] 49 {{{#!td style="padding-left: 2em" 50 {{{#!html 51 <div style="font-size: 80%" class="trac-macrolist"> 52 <h3><code>[[Image]]</code></h3>Embed an image in wiki-formatted text. 53 54 The first argument is the file … 55 <h3><code>[[InterTrac]]</code></h3>Provide a list of known <a class="wiki" href="/wiki/InterTrac">InterTrac</a> prefixes. 56 <h3><code>[[InterWiki]]</code></h3>Provide a description list for the known <a class="wiki" href="/wiki/InterWiki">InterWiki</a> prefixes. 57 <h3><code>[[KnownMimeTypes]]</code></h3>List all known mime-types which can be used as <a class="wiki" href="/wiki/WikiProcessors">WikiProcessors</a>. 58 Can be …</div> 59 }}} 60 etc. 52 61 }}} 53 62 54 == Available Macros ==63 == Available Macros 55 64 56 65 ''Note that the following list will only contain the macro documentation if you've not enabled `-OO` optimizations, or not set the `PythonOptimize` option for [wiki:TracModPython mod_python].'' … … 58 67 [[MacroList]] 59 68 60 == Macros from around the world ==69 == Macros from around the world 61 70 62 The [http://trac-hacks.org/ Trac Hacks] site provides a wide collection of macros and other Trac [TracPlugins plugins] contributed by the Trac community. If you 're looking for new macros, or have written one that you'd like to share with the world, pleasedon't hesitate to visit that site.71 The [http://trac-hacks.org/ Trac Hacks] site provides a wide 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 with the world, don't hesitate to visit that site. 63 72 64 == Developing Custom Macros == 73 == Developing Custom Macros 74 65 75 Macros, like Trac itself, are written in the [http://python.org/ Python programming language] and are developed as part of TracPlugins. 66 76 67 77 For more information about developing macros, see the [trac:TracDev development resources] on the main project site. 68 78 79 Here are 2 simple examples showing how to create a Macro. Also, have a look at [trac:source:tags/trac-1.0.2/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. 69 80 70 Here are 2 simple examples showing how to create a Macro with Trac 0.11. 81 === Macro without arguments 71 82 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.73 74 === Macro without arguments ===75 83 To test the following code, you should saved it in a `timestamp_sample.py` file located in the TracEnvironment's `plugins/` directory. 76 84 {{{ … … 92 100 def expand_macro(self, formatter, name, text): 93 101 t = datetime.now(utc) 94 return tag. b(format_datetime(t, '%c'))102 return tag.strong(format_datetime(t, '%c')) 95 103 }}} 96 104 97 === Macro with arguments === 98 To test the following code, you should saved it in a `helloworld_sample.py` file located in the TracEnvironment's `plugins/` directory. 105 === Macro with arguments 106 107 To test the following code, you should save it in a `helloworld_sample.py` file located in the TracEnvironment's `plugins/` directory. 99 108 {{{ 100 109 #!python … … 138 147 For example, when writing: 139 148 {{{ 140 {{{#!HelloWorld style="polite" 149 {{{#!HelloWorld style="polite" -silent verbose 141 150 <Hello World!> 142 151 }}} … … 150 159 One should get: 151 160 {{{ 152 Hello World, text = <Hello World!> , args = {'style': u'polite' }161 Hello World, text = <Hello World!> , args = {'style': u'polite', 'silent': False, 'verbose': True} 153 162 Hello World, text = <Hello World!> , args = {} 154 163 Hello World, text = <Hello World!> , args = None … … 157 166 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 167 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:168 You can also recursively use a wiki Formatter (`from trac.wiki import Formatter`) to process the `text` as wiki markup: 160 169 161 170 {{{ 162 171 #!python 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()) 172 from genshi.core import Markup 173 from trac.wiki.macros import WikiMacroBase 174 from trac.wiki import Formatter 175 import StringIO 176 177 class HelloWorldMacro(WikiMacroBase): 178 def expand_macro(self, formatter, name, text, args): 179 text = "whatever '''wiki''' markup you want, even containing other macros" 180 # Convert Wiki markup to HTML, new style 181 out = StringIO.StringIO() 182 Formatter(self.env, formatter.context).format(text, out) 183 return Markup(out.getvalue()) 168 184 }}}