Changes between Version 83 and Version 84 of SandBox


Ignore:
Timestamp:
Feb 27, 2016 1:16:21 PM (21 months ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SandBox

    v83 v84  
    11= The Sandbox =
    2 
    3 Click "EDIT THIS PAGE" at the bottom to see the wikiml and comments
    4 
    5 == Anchors ==
    6 
    7 All this auto-formatting makes for big pages real fast. see [#point1 (1)] on this problem (and avoid scrolling to the bottom)
    8 Will this work? [SandBox?action=edit (2)]
    9 
    10 [#blah (foo)]
    11 
    12 == Syntax highlighting ==
    13 
    14 {{{
    15 #!sh (Bourne/Bash shell)
    16 while :; do echo "foo"; done
    17 }}}
    18 
    19 = RST support =
    20 
    21 {{{
    22 #!rst
    23 FooBar Header
    24 =============
    25 reStructuredText is **nice**. It has its own webpage_.
    26 
    27 A table:
    28 
    29 =====  =====  ======
    30    Inputs     Output
    31 ------------  ------
    32   A      B    A or B
    33 =====  =====  ======
    34 False  False  False
    35 True   False  True
    36 False  True   True
    37 True   True   True
    38 =====  =====  ======
    39 
    40 
    41 
    42 RST TracLinks
    43 -------------
    44 
    45 See also ticket `#42`:trac:.
    46 
    47 .. _webpage: http://docutils.sourceforge.net/rst.html
    48 }}}
    49 
    50 [=#blah (foo)]
    51 
    52 {{{
    53 #!rst
    54 
    55 .. code-block:: python
    56 
    57    class Test:
    58 
    59        def TestFunction(self):
    60            pass
    61 
    62 }}}
    63 
    64 = html =
    65 
    66 {{{
    67 #!div class="important" style="border: 2pt solid; text-align: center"
    68 This is the ''only'' way to go in Trac 0.11
    69 }}}
    70 
    71 {{{
    72 #!div class="wikipage" style="border: 1pt dotted"
    73 Only `wikipage` (same as specifying no class attribute)
    74 }}}
    75 
    76 {{{
    77 #!div class="wikipage compact " style="border: 1pt solid"
    78 Use combined classes (`compact` and `wikipage`)
    79 }}}
    80 
    81 {{{
    82 #!div class="compact" style="border: 1pt dotted"
    83 Only `compact`
    84 }}}
    85 
    86 {{{
    87 #!div class="" style="border: 1pt solid"
    88 No classes (//not// the same as specifying no class attribute...)
    89 }}}
    90 == test ==
    91 
    92 {{{#!table class=""
    93 ||  0||  1||  2||
    94 || 10|| 20|| 30||
    95 || 11|| 22|| 33||
    96 ||||||=  numbers  =||
    97 }}}
    98 
    99 
    100 {{{
    101 #!html
    102 <h1 style="text-align: left; color: blue">How well does Lynx/links/elinks support the table below?</h1>
    103 }}}
    104 
    105 Simple 2x2 table with rich content:
    106 {{{#!th align=left
    107  - Left
    108  - Header
    109 }}}
    110 {{{#!th align=left
    111  - Right
    112  - Header
    113 }}}
    114 |----------------------------------
    115 {{{#!td style="background: #ffd"
    116  - Left
    117  - Content
    118 }}}
    119 {{{#!td style="vertical-align: top"
    120 !RightContent
    121 }}}
    122 |----------------------------------
    123 || ... and this can be mixed||\
    124 ||with pipe-based cells ||
    125 {{{#!td colspan=2
    126 Pick the style the more appropriate
    127 to your content
    128 
    129 See WikiFormatting#Tables for details
    130 on the pipe-based table syntax.
    131 }}}
    132 
    133 If one needs to add some
    134 attributes to the table itself...
    135 
    136 {{{
    137 #!table style="border:none;text-align:center;margin:auto"
    138   {{{#!tr ====================================
    139     {{{#!th style="border: none"
    140     Left header
    141     }}}
    142     {{{#!th style="border: none"
    143     Right header
    144     }}}
    145   }}}
    146   {{{#!tr ==== style="border: 1px dotted grey"
    147     {{{#!td style="border: none"
    148     1.1
    149     }}}
    150     {{{#!td style="border: none"
    151     1.2
    152     }}}
    153   }}}
    154   {{{#!tr ====================================
    155     {{{#!td style="border: none"
    156     2.1
    157     }}}
    158     {{{#!td
    159     2.2
    160     }}}
    161   }}}
    162 }}}
    163 
    164 
    165 
    166 === Preprocessors ===
    167 
    168 {{{#!comment
    169 #!html
    170     Insert custom HTML in a wiki page.
    171 #!htmlcomment
    172     Insert an HTML comment in a wiki page (since 0.12).
    173 
    174 Note that #!html blocks have to be self-contained, i.e. you can't start an HTML element in one block and close it later in a second block. Use the following processors for achieving a similar effect.
    175 
    176 #!div
    177     Wrap an arbitrary Wiki content inside a <div> element (since 0.11).
    178 #!span
    179     Wrap an arbitrary Wiki content inside a <span> element (since 0.11).
    180 
    181 #!td
    182     Wrap an arbitrary Wiki content inside a <td> element (since 0.12)
    183 #!th
    184     Wrap an arbitrary Wiki content inside a <th> element (since 0.12)
    185 #!tr
    186     Can optionally be used for wrapping #!td and #!th blocks, either for specifying row attributes of better visual grouping (since 0.12)
    187 
    188 See WikiHtml for example usage and more details about these processors.
    189 Other Markups
    190 
    191 #!rst
    192     Trac support for Restructured Text. See WikiRestructuredText.
    193 #!textile
    194     Supported if  Textile is installed. See  a Textile reference.
    195 
    196 Code Highlighting Support
    197 
    198 Trac includes processors to provide inline syntax highlighting:
    199 
    200     #!c (C), #!cpp (C++), #!python (Python), #!perl (Perl), #!ruby (Ruby), #!php (PHP), #!asp (ASP), #!java (Java), #!js (Javascript), #!sql (SQL), #!xml (XML or HTML), #!sh (Bourne/Bash shell), etc.
    201 
    202 Trac relies on external software packages for syntax coloring, like  Pygments.
    203 
    204 See TracSyntaxColoring for information about which languages are supported and how to enable support for more languages.
    205 
    206 Note also that by using the MIME type as processor, it is possible to syntax-highlight the same languages that are supported when browsing source code. For example, you can write:
    207 
    208 {{{
    209 #!text/html
    210 <h1>text</h1>
    211 }}}
    212 
    213 }}}
    214 
    215 == Macros ==
    216 
    217 {{{#!comment
    218 [[TicketQuery(41)]]
    219 }}}
    220 
    221 {{{#!comment
    222 the format=group seems promising
    223 [[TitleIndex(format=hierarchy)]]
    224 
    225 Insert an alphabetic list of all wiki pages into the output.
    226 
    227 Accepts a prefix string as parameter: if provided, only pages with names that start with the prefix are included in the resulting list. If this parameter is omitted, all pages are listed. If the prefix is specified, a second argument of value 'hideprefix' can be given as well, in order to remove that prefix from the output.
    228 
    229 Alternate format and depth named parameters can be specified:
    230 
    231     format=compact: The pages are displayed as comma-separated links.
    232     format=group: The list of pages will be structured in groups according to common prefix. This format also supports a min=n argument, where n is the minimal number of pages for a group.
    233     format=hierarchy: The list of pages will be structured according to the page name path hierarchy. This format also supports a min=n argument, where higher n flatten the display hierarchy
    234     depth=n: limit the depth of the pages to list. If set to 0, only toplevel pages will be shown, if set to 1, only immediate children pages will be shown, etc. If not set, or set to -1, all pages in the hierarchy will be shown.
    235 }}}
    236 
    237 {{{#!comment
    238 blah
    239 [[TracAdminHelp]]               # all commands
    240 [[TracAdminHelp(wiki)]]         # all wiki commands
    241 [[TracAdminHelp(wiki export)]]  # the "wiki export" command
    242 [[TracAdminHelp(upgrade)]]      # the upgrade command
    243 }}}
    244 
    245 {{{#!comment
    246 VERY VERBOSE
    247 [[MacroList(*)]]
    248 
    249     perm -- show only that users, a permission action given by value has been granted to
    250     locked -- retrieve users, who's account has/has not been locked depending on boolean value
    251     format -- output style: 'count', 'list' or comma-separated values (default)
    252     nomatch -- replacement wiki markup that is displayed, if there's no match and output style isn't 'count' either
    253 
    254 'count' is also recognized without prepended key name. Other non-keyed parameters are:
    255 
    256     locked -- alias for 'locked=True'
    257     visit -- show a list of accounts with last-login information, only available in table format
    258     name -- forces replacement of maching username with their corresponding full names, if available; adds a full names column if combined with 'visit'
    259     email -- append email address to usernames, if available
    260 
    261 Requires USER_VIEW permission for output in any format other then 'count'. A misc placeholder with this statem
    262 
    263 }}}
    264 
    265 
    266 == Images ==
    267 
    268 "attached" image doesn't show up under attachments at the bottom. Is it there?
    269 [[Image(photo.jpg)]]                           # simplest
    270     [[Image(muttlogo.png, 120px)]]                    # with image width size
    271     [[Image(muttlogo.png, right)]]                    # aligned by keyword
    272     [[Image(muttlogo.png, nolink)]]                   # without link to source
    273     [[Image(muttlogo.png, align=right)]]              # aligned by attribute
    274 
    275 '''This works'''
    276 [[Image(muttlogo.png)]]
    277 
    278 '''This does not'''
    279 {{{ [[Image(http://dev.mutt.org/trac/attachment/wiki/SandBox/muttlogo.png)]] }}}
    280 
    281 == He said She said ==
    282 
    283 >> ... (I said)
    284 > (he replied)
    285 >>> does this need parenthesis?
    286 >>>> (or does it only work with them?)
    287 > does this actually use color?
    288 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> if so how many? (4?)
    289 
    290 == Attachment file size limit ==
    291 
    292 {{{
    293 Error: Upload failed
    294 Maximum attachment size: 262144 bytes
    295 }}}
    296 
    297 '''''I'm guessing you have to be a wiki-admin to remove the private GPG key file you uploaded by accident'''''
    298 
    299 == Comments ==
    300 
    301 This won't work as expected
    302 {{{
    303 {{{#!comment trac doesn't seem to support single in-line comment syntax like this.}}}
    304 }}}
    305 
    306 This will work
    307 {{{
    308 {{{#!comment
    309 This is a great comment but it must use a dedicated comment line above and closing bottom curly braces.
    310 }}}
    311 }}}
    312 
    313 {{{#!comment
    314 The trac developers really spared no efforts in making the worst comment formatting syntax I've ever seen anywhere.
    315 Only this three line form works.
    316 }}}
    317 
    318 {{{#!comment
    319 {{{#!comment The trac developers really spared no efforts in making the worst comment formatting syntax I've ever seen anywhere. }}}
    320 {{{#!comment Why can't I make a single line comment? Every comment has to have 3 lines. Bug or feature? }}}
    321 }}}
    3222
    3233This is just a page to practice and learn WikiFormatting.
    3244
    3255Go ahead, edit it freely.
    326 
    327 term:: definition on
    328         multiple lines
    329 
    330 
    331 sandbox:: a place to make test edits
    332  even on multiple lines
    333   with spacing
    334  1. Does auto-inc still work?
    335   a. within a term?
    336 
    337 * This page should be organized better
    338   with a focus on readability
    339   1. It should look professional
    340     a. and contain concise
    341      powerful examples
    342      i. that prevent bad questions
    343         a. and make users happy
    344         a. another small letter
    345         a. another small letter a
    346   2. Is indenting just being preserved?
    347      i. this is another "i"
    348      i. this is another "i"
    349      i. does auto-increment apply at all indented character lines?
    350   3. Does number sequence matter?
    351   1. Like this line starts with number ONE not FOUR
    352          
    353 == Bullet Styles ==
    354 
    355 * # 1 auto numbering appears broken with bullets
    356 * # 1
    357 * # 1. Three
    358  * 1 Indent spacing matters
    359  * 1 Indent
    360   * 1. Indent
    361   * 1. Indent
    362 
    363 == Font Styles ==
    364 
    365 http://dev.mutt.org/trac/wiki/WikiFormatting#FontStyles
    366 
    367 bold, italic, Wikipedia style
    368 
    369 '''bold''', ''italic'', '''''Italic Bold Wikipedia style'''''
    370 
    371 {{{
    372 '''bold''', ''italic'', '''''Italic Bold Wikipedia style'''''
    373 }}}
    374 
    375 === escaping code blocks styles ===
    376 
    377 ==== inline ====
    378 
    379 {{{ {{{ '''bold''', ''italic'', '''''Wikipedia style''''' }}} }}}
    380 
    381 ==== standalone ====
    382 
    383 {{{
    384 {{{
    385 '''bold''', ''italic'', '''''Wikipedia style'''''
    386 }}}
    387 }}}
    388 
    389 === font effects ===
    390 
    391 
    392 `monospaced` and `''nowiki''`
    393 
    394 {{{ `monospaced and ''nowiki''` }}}
    395 
    396 `''isn't this supposed to not show the quotes? or !WhatIsThisNoWikiStyleDoing?''`
    397 
    398 `NO QUOTES isn't this supposed to not show the quotes? or !WhatIsThisNoWikiStyleDoing?`
    399 
    400 === Level 3 ^([#hn this is important])^
    401 
    402 CamelCaseAutoLink
    403 
    404 {{{ !CamelCaseEscapedWithExclamationPoint }}}
    405 
    406 [=#point1 (1)] Welcome the bottom of the page. Come again.