Changes between Version 41 and Version 42 of TracDev/Proposals/AdvancedWikiFormatting

Timestamp:

Jun 10, 2011, 8:40:31 PM (13 years ago)

Author:

Christian Boos

Comment:

a few clean-ups in the #Transclusion section

TracDev/Proposals/AdvancedWikiFormatting

@@ -209 +209 @@
 }}}
 
-Alternatively, the default content of the include processor could be made available to the  wiki variables present in the template in a special variable, e.g. "INCLUDE_CONTENT".
-
-Variable expansion could also be done using a dedicated syntax (e.g. `@INCLUDE_CONTENT@`, like [MoinMoin:HelpOnVariables MoinMoin] or [http://www.dokuwiki.org/plugin:templater plugin:templater] in dokuwiki), the `{{{...}}}` style of MediaWiki conflicts with our inline verbatim style.
-
 The Template:ReleaseInfo page would have the following content:
 {{{
@@ -220 +216 @@
  }}}
 }}}
+
+Alternatively, the default content of the include processor could be made available to the  wiki variables present in the template in a special variable, e.g. "INCLUDE_CONTENT".
+
+{{{
+{{{#!include page="Template:ReleaseInfo2" version="1.0"
+ This version is feature complete, mind you.
+  - all existing tickets are implemented
+  - there are no known (or unknown) bugs
+  - there's even no feature left to be implemented, all is there
+}}}
+}}}
+
+The Template:ReleaseInfo2 page would have the following content:
+{{{
+ Version:: @version|unknown@
+ Description:: @INCLUDE_CONTENT@
+}}}
+
+Variable expansion could also be done using a dedicated syntax (e.g. `@@`, like [MoinMoin:HelpOnVariables MoinMoin] or [http://www.dokuwiki.org/plugin:templater plugin:templater] in dokuwiki), the `{{{...}}}` style of MediaWiki conflicts with our inline verbatim style.
 
 Instead of `#!param`, we could also use `!#define` to create a variable that could be used in the document itself, or rather in the current scope. 
@@ -242 +257 @@
  - `[[Include(#ReleaseInfo, version=2.0, description=not there yet)]]`
  - `{{#ReleaseInfo|version=2.0|description=not there yet}}` (MediaWiki:Help:Template)
-Note that `.#abc` and `#abc` are targeting the same node.
+Note that `.#abc` and `#abc` are targeting the same node. XXX Maybe even only use `abc` here?
 
 "Define" could also be used for much small repetitive text, like repetitive URLs, when one doesn't want to define an InterWiki prefix for it, e.g.
- - 
-`[[Define(issue=http://bugs.python.org/issue@1@)]]` and `{{issue|1234}}`
- - `@issue=http://bugs.python.org/issue{{1}}@` (?)
- - `@issue=http://bugs.python.org/issue@` and `@issue@1234` (?)
+ - `[[Define(issue=[http://bugs.python.org/issue@1@ Issue @1@])]]` and `[[Include(issue, 1234)]]`
+ - `{{issue=[http://bugs.python.org/issue@1@ Issue @1@])]]` and `{{issue|1234}}`
+ - `@issue=[http://bugs.python.org/issue{{1}} Issue {{1}}]@` and `@issue|1234@`
+
+
 
 In summary, we would have the following constructions:
@@ -278 +294 @@
 
 A technical difficulty with the short form for transclusion `{{...}}` is the need to handle the nesting of `{{...}}` pairs, to allow for multiple level of expansion, like shown in [http://meta.wikimedia.org/wiki/Help:Advanced_templates advanced templates] in MediaWiki.
-
-The `<name>` parameter given to includes should itself be subject to expansion , and if this corresponds to an unbound variable, the inclusion will be dynamic (parsing deferred to the formatting stage).
-//Or should parsing always be deferred?//.
+One level can easily be taken care of by using both the `{{...}}` and `@...@` styles.
+
+The `<name>` parameter given to includes should itself be subject to expansion , and if this corresponds to an unbound variable, the inclusion will be dynamic.
 
 Recursion should be detected (//trying to include `<name>` when `<name>` is already in the stack of includes//) and prevented (//as if `<name>` was missing, i.e. replaced by nothing or the given `default` value//).