home

sandbox

This is the testing grounds for everyone on ~camp to get used to WikiCreole!

YES! The spaces work in the links now.

Here's the basics:
http://www.wikicreole.org/imageServlet?page=CheatSheet%2Fcreole_cheat_sheet.png

Let's make sure the normal use cases work...

...well shit it gets a little confusing but it seems like spaces work now! Seems like any remaining inconsistencies have more to do with how the "link" works in creoledump

Trying Tables

These will work the same:

This is a Table yep
item one yep
item two yep
title two Yay
another item uh-huh

(yikes, apparently tables HAVE to have something between them to work properly...)

This is a Table yep
item one yep
item two yep
title two Yay
another item uh-huh

Obviously this second one is better.. it looks the same on the page, but it's easier to read in the textbox below... therefore easier to edit for the others.

The No-Formatting Tag

There is a small difference between the no-formatting for a single line and the no-formatting for many lines.

There is the inline non-formatting and then...

There is also the:

the non-formatting tag
      that takes multiple lines

 and it will not create [[links]]

or even

==headers==

so it's ideal for sharing bits of WikiCreole AS-IS without it triggering [[creoledump]] to turning it into HTML.

These are ideal for printing bits of code, without WikiCreole going crazy wit it. The "{{{" are a pretty rare tag, so usually everything can be nicely contained in there.

OH YEAH! and then you can make ASCII ART, TOO!!! :D :D :D

     _____________
    ( YESSSSS!!!!!)
     V
\       /
 \(^u^)/
    |
    |
   / \
  /   \

test+article+name+with+pluses ...these will apparently be interpreted as spaces.

test%23article%23name%23with%23hashsymbols

test#article#name#with#hashsymbols

What+about+this+plus+

+

+

Interestingly, an HTML-entity like + will not be translated in the body, but it will be translated in the textbox. Then if you hit "Save Changes" it will translate the expression of the HTML-entity into the body as well.

...it even does this in the "non-formatting" text, so it really should be fixed. Whatever keeps it from expressing the HTML-entity that it represents in the body should be applied to the textbox below as well to prevent the expression of the HTML-entity in the textbox. That would be better continuity.


Revision: 37


Older versions:
    1     2     3     4     5     6     7     8     9     10     11     12     13     14     15     16     17     18     19     20     21     22     23     24     25     26     27     28     29     30     31     32     33     34     35     36