xcfit 0.2.0

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/MarkupLists/properties.xml

@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<properties>
+<Files/>
+<RecentChanges/>
+<WhereUsed/>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/MarkupLiteralText/content.txt

@@ -0,0 +1,9 @@
+Sometimes you want to show a !-WikiWord-! without having it turn into a link.  Or sometimes you might want to show some wiki markup text such as !-'''bold'''-! without having the markup take effect.  To do this you use the ''literal'' markup text.
+
+Any text enclosed in '''!-!--!''' and '''-!''' will be treated as a literal and will not be processed for wiki words or other markup widgets.  This is also a "cool" way to add HTML to a wiki page.
+
+|!c '''Markup Text'''|!c '''Displays as'''|
+|!-!-WikiWord-!-!|!-WikiWord-!|
+|!-!-'''bold'''-!-!|!-'''bold'''-!|
+|!-!-&lt;i&gt;hello&lt;/i&gt;-!-!|!-<i>hello</i>-!|
+

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/MarkupLiteralText/properties.xml

@@ -0,0 +1,10 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<properties>
+<Files/>
+<Normal/>
+<RecentChanges/>
+<Static/>
+<WhereUsed/>
+<saveId>1225603481926</saveId>
+<ticketId>-5671299916402952716</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/MarkupNesting/content.txt

@@ -0,0 +1,39 @@
+Some markup elements can not be nested within other markup elements without creating an ambiguous meaning. In this case, we can use the nesting delimiters '''!-!(-!''' and '''!-)!-!'''.  These delimiters act like parenthesis - they do not add any content to the page but just group the interpretation of the enclosed markup correctly.
+
+We can use this to nest tables, for example:
+
+!-|this|table|-!
+!-|has| !(|a|nested|table|)! |-!
+
+displays as:
+
+|this|table|
+|has| !(|a|nested|table|)! |
+
+Without nesting:
+
+!-|this|table|-!
+!-|has| |a|nested|table| |-!
+
+is displayed as a single table.
+
+|this|table|
+|has| |a|nested|table| |
+
+Nesting always creates a 'virtual' new line, so elements that must start on a new line can be nested within other content.
+
+!-This line has !(!note a nested note)! within.-!
+
+displays as:
+
+This line has !(!note a nested note)! within.
+
+Without nesting:
+
+!-This line has !note a nested note within.-!
+
+displays as:
+
+This line has !note a nested note within.
+
+ 

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/MarkupNesting/properties.xml

@@ -0,0 +1,11 @@
+<?xml version="1.0"?>
+<properties>
+	<Edit>true</Edit>
+	<Files>true</Files>
+	<Properties>true</Properties>
+	<RecentChanges>true</RecentChanges>
+	<Refactor>true</Refactor>
+	<Search>true</Search>
+	<Versions>true</Versions>
+	<WhereUsed>true</WhereUsed>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/MarkupNote/content.txt

@@ -0,0 +1,6 @@
+You can make a note by starting a line with '''!note'''
+
+|!c '''Markup Text'''|!c '''Displayed as'''|
+|!-!note this text is a note-!|!note this text is a note|
+
+

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/MarkupNote/properties.xml

@@ -0,0 +1,9 @@
+<?xml version="1.0"?>
+<properties>
+	<Files/>
+	<LastModified>20090327102259</LastModified>
+	<RecentChanges/>
+	<WhereUsed/>
+	<saveId>1238167379384</saveId>
+	<ticketId>6044718649644820583</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/MarkupPageInclude/content.txt

@@ -0,0 +1,25 @@
+To include the content from one page into another you may use the !-!include-! widget
+
+Usage:
+'''!-!include PageName-!'''
+
+For example if you wanted to all the content from .FrontPage to be displayed here you would simply type:
+
+!-!include .FrontPage-!
+
+As a result you will see .FrontPage below:
+-----
+!include .FrontPage
+-----
+|'''Parameters:'''|
+|!style_code(-seamless)|''causes the included page to be rendered without an enclosing box.''|
+|!style_code(-c)|''causes the included page to be collapsed.''|
+|!style_code(-setup)|''causes the included page to be used for test/suite setup.''|
+|!style_code(-teardown)|''causes the included page to be used for test/suite teardown.''|
+
+!3 '''Watch out for !include cycles'''
+Don't include a page that already includes the page that you are including from. ;-)
+
+!3 Including Test snippets
+It is often useful to include portions of test tables into your tests. You do this to bring in common setup data or common test sequences (possibly modified with variables).  A convenient way to do this is to use the Backwards Search notation as follows:{{{!include <UtilityPage.MyUtility}}}
+This will hunt up the parent chain until !-UtilityPage-! is found, and then its child !-MyUtility-! will be included.

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/MarkupPageInclude/properties.xml

@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<properties>
+<Files/>
+<RecentChanges>true</RecentChanges>
+<WhereUsed/>
+<saveId>1232747484629</saveId>
+<ticketId>-5093174657906389793</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/MarkupPath/content.txt

@@ -0,0 +1,15 @@
+There are some special functions in FitNesse that require you to name a directory path.  You do this with the !path directive.
+
+|!c '''Markup Text'''|!c '''Displays as'''|
+|!-!path c:\directory-!|!path c:\directory|
+
+You can also specify all the .jar files in a directory by using a wildcard:
+{{{!-!path /usr/javalib/*.jar-!}}}
+
+Or you can specify all .jar files in a directory ''and all subdirectories'' by using the ** wildcard.
+{{{!-!path /usr/javalib/**.jar-!}}}
+
+Paths such as these will be used when you press the ''test'' or ''suite'' buttons on a page.
+
+
+

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/MarkupPath/properties.xml

@@ -0,0 +1,9 @@
+<?xml version="1.0"?>
+<properties>
+	<Files/>
+	<LastModified>20090228113824</LastModified>
+	<RecentChanges>true</RecentChanges>
+	<WhereUsed/>
+	<saveId>1213127675393</saveId>
+	<ticketId>7889220604288275533</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/MarkupPicture/content.txt

@@ -0,0 +1,19 @@
+Picture can be added by using the '''!img''' marker followed by a URL
+As a shortcut, any URL ending in '''.gif''' or '''.jpg''' will also be included as an image.
+
+|!c '''Markup Text'''|!c '''Displayed as:'''|
+|{{{!img http://files/fitnesse/images/fitnesse-logo.png}}}|!img http://files/fitnesse/images/fitnesse-logo.png|
+|{{{http://files/fitnesse/images/fitnesse_architecture.jpg}}}|http://files/fitnesse/images/fitnesse_architecture.jpg|
+
+You may align images to the left or right and wrap following text around the images by using '''!img-l''' and '''!img-r''' respectively.
+
+|{{{!img-l (Gettysburg address)}}}|!img-l http://files/fitnesse/images/fitnesse-logo.png Fourscore and seven years ago our fathers brought forth on this continent a new nation, conceived in liberty and dedicated to the proposition that all men are created equal. Now we are engaged in a great civil war, testing whether that nation or any nation so conceived and so dedicated can long endure. We are met on a great battlefield of that war. We have come to dedicate a portion of that field as a final resting-place for those who here gave their lives that that nation might live. It is altogether fitting and proper that we should do this. But in a larger sense, we cannot dedicate, we cannot consecrate, we cannot hallow this ground. The brave men, living and dead who struggled here have consecrated it far above our poor power to add or detract. The world will little note nor long remember what we say here, but it can never forget what they did here. It is for us the living rather to be dedicated here to the unfinished work which they who fought here have thus far so nobly advanced. It is rather for us to be here dedicated to the great task remaining before us that from these honored dead we take increased devotion to that cause for which they gave the last full measure of devotion that we here highly resolve that these dead shall not have died in vain, that this nation under God shall have a new birth of freedom, and that government of the people, by the people, for the people shall not perish from the earth.|
+|{{{!img-r (Gettysburg address)}}}|!img-r http://files/fitnesse/images/fitnesse-logo.png Fourscore and seven years ago our fathers brought forth on this continent a new nation, conceived in liberty and dedicated to the proposition that all men are created equal. Now we are engaged in a great civil war, testing whether that nation or any nation so conceived and so dedicated can long endure. We are met on a great battlefield of that war. We have come to dedicate a portion of that field as a final resting-place for those who here gave their lives that that nation might live. It is altogether fitting and proper that we should do this. But in a larger sense, we cannot dedicate, we cannot consecrate, we cannot hallow this ground. The brave men, living and dead who struggled here have consecrated it far above our poor power to add or detract. The world will little note nor long remember what we say here, but it can never forget what they did here. It is for us the living rather to be dedicated here to the unfinished work which they who fought here have thus far so nobly advanced. It is rather for us to be here dedicated to the great task remaining before us that from these honored dead we take increased devotion to that cause for which they gave the last full measure of devotion that we here highly resolve that these dead shall not have died in vain, that this nation under God shall have a new birth of freedom, and that government of the people, by the people, for the people shall not perish from the earth.|
+
+You may also set the width of the image if you wish by using '''!-!img -w nnn-!''' where nnn is the width of the image, set the border of the image using '''!-!img -b x-!''' where x is the width of the border and set the margin around the image using '''!-!img -m y-!''' where y is the margin.  You may also combine all of these attributes.
+
+|!c '''Markup Text'''|!c '''Displayed as:'''|
+|{{{!img -w 200 http://files/fitnesse/images/fitnesse-logo.png}}}|!img -w 200 http://files/fitnesse/images/fitnesse-logo.png|
+|{{{!img -b 2 http://files/fitnesse/images/fitnesse-logo.png}}}|!img -b 2 http://files/fitnesse/images/fitnesse-logo.png|
+|{{{!img -m 10 http://files/fitnesse/images/fitnesse-logo.png}}}|!img -m 10 http://files/fitnesse/images/fitnesse-logo.png|
+|{{{!img -w 200 -b 2 -m 10 http://files/fitnesse/images/fitnesse-logo.png}}}|!img -w 200 -b 2 -m 10 http://files/fitnesse/images/fitnesse-logo.png|

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/MarkupPicture/properties.xml

@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<properties>
+<Files/>
+<RecentChanges>true</RecentChanges>
+<WhereUsed/>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/MarkupPreformatted/content.txt

@@ -0,0 +1,23 @@
+If you want a stretch of text that should be left alone then you can enclose that text in three braces as follows:
+!-{{{-!{{{Text to be left alone}}}!-}}}-!
+Between the braces no wiki words will be identified, no markup syntax will be decoded.  The text will be displayed in mono font exactly as it was typed. We use this technique a lot for showing samples of fixture code:
+{{{
+import fit.ColumnFixture;
+
+public class AddRemovePlayerFixture extends ColumnFixture {
+  public String playerName;
+  private Game theGame;
+
+  public boolean addPlayer() {
+    theGame = StaticGame.getInstance();
+    Player thePlayer = theGame.addPlayer(playerName);
+    return theGame.playerIsPlaying(thePlayer);
+  }
+
+  public int countPlayers() {
+    return theGame.getNumberOfPlayers();
+  }
+} }}}
+
+
+

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/MarkupPreformatted/properties.xml

@@ -0,0 +1,7 @@
+<?xml version="1.0"?>
+<properties>
+	<Files/>
+	<LastModified>20090228113824</LastModified>
+	<RecentChanges>true</RecentChanges>
+	<WhereUsed/>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/MarkupStrike/content.txt

@@ -0,0 +1,4 @@
+To put a --strike-- through word or phrase simply surround the text with two dashes.
+
+|!c '''Markup Text'''|!c '''Displayed as'''|
+|!-I want --this-- to be struck.-!|I want --this-- to be struck.|

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/MarkupStrike/properties.xml

@@ -0,0 +1,7 @@
+<?xml version="1.0"?>
+<properties>
+  <Files/>
+  <LastModified>20060717205955</LastModified>
+  <RecentChanges/>
+  <WhereUsed/>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/MarkupStyle/content.txt

@@ -0,0 +1,27 @@
+To set the style of a word or phrase use the !-!style_<class>(text)-! widget. This widget has three forms.  !style_code[!-!style_<class>(text)-!], !style_code(!-!style_<class>{text}-!), and !style_code{!-!style_<class>[text]-!}
+
+!note Yes, that means that you cannot put a style around a single string that has all three closing terminators.  I'm sure you can figure out the workaround.
+Here are some of the available classes you can use.
+
+| !c '''Markup Text''' | !c '''Displayed as''' |
+| !-!style_error(an error)-! | !style_error(an error) |
+| !-!style_pass(pass)-! | !style_pass(pass) |
+| !-!style_fail(fail)-! | !style_fail(fail) |
+| !-!style_ignore(ignore)-! | !style_ignore(ignore) |
+| !-!style_caps{Caps}-! | !style_caps{Caps} |
+| !-!style_code[code]-! | !style_code[code] |
+| !-!style_red[red]-! and other colors... | !style_red[red], !style_orange[orange], !style_yellow[yellow], !style_green[green], !style_blue[blue], !style_indigo[indigo], !style_violet[violet], !style_pink[pink], !style_lightYellow[lightYellow], !style_lightGreen[lightGreen], !style_lightBlue[lightBlue], !style_chocolate[chocolate], !style_darkOrange[darkOrange], !style_darkRed[darkRed], !style_olive[olive], !style_darkBlue[darkBlue], !style_darkGreen[darkGreen] |
+| !-!style_code(!style_red[code red])-! | !style_code(!style_red[code red]) |
+| !-!style_note[note]-! | !style_note[note] |
+| !-!style_right[right]-! | !style_right[right] |
+| !-!style_strike[strike]-! | !style_strike[strike] |
+| !-!style_meta[meta]-! | !style_meta[meta] |
+| !-!style_included[included]-! | !style_included[included] |
+| !-!style_setup[setup]-! | !style_setup[setup] |
+| !-!style_collapse_rim[collapse_rim]-! | !style_collapse_rim[collapse_rim] |
+| !-!style_pageHelp[pageHelp]-! | !style_pageHelp[pageHelp] |
+| !-x !style_hidden[hidden] x-! | x !style_hidden[hidden] x |
+| !-!style_test_output_name[test_output_name]-! | !style_test_output_name[test_output_name] |
+| !-!style_fit_label[fit_label]-! | !style_fit_label[fit_label] |
+| !-!style_fit_stacktrace[fit_stacktrace]-! | !style_fit_stacktrace[fit_stacktrace] |
+| !-!style_fit_grey[fit_grey]-! | !style_fit_grey[fit_grey] |

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/MarkupStyle/properties.xml

@@ -0,0 +1,13 @@
+<?xml version="1.0"?>
+<properties>
+	<Edit>true</Edit>
+	<Files>true</Files>
+	<Properties>true</Properties>
+	<RecentChanges>true</RecentChanges>
+	<Refactor>true</Refactor>
+	<Search>true</Search>
+	<Versions>true</Versions>
+	<WhereUsed>true</WhereUsed>
+	<saveId>1232130397426</saveId>
+	<ticketId>2924400028923341443</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/MarkupTable/content.txt

@@ -0,0 +1,41 @@
+Tables can be created very easily.  Use the vertical stroke as the first character of the line, and separate each table cell with it:
+
+'''Markup Text'''
+{{{|Alpha|
+|Beta|gamma|Delta|
+|1|2|3|}}}----
+'''Displays as:'''
+|Alpha|
+|Beta|gamma|Delta|
+|1|2|3|
+----
+You can use most wiki markup directives in table cells, including !c, !1, !2, !3, bold, and italic.
+!2 Literal tables.
+If you don't want any markup directives interpreted in the table, then you can use a special form that is preceded with a ! and like this:
+
+'''Markup Text'''
+{{{!|ThisTableWillNotInterpret|!c any directives|'''it is treated'''|
+|!1 like a literal|--and is especially useful--|''for test tables.''|
+|^SinceTheyTend| * to have WikiWord symbols in them.|}}}
+'''Displays as:'''
+!|ThisTableWillNotInterpret|!c any directives|'''it is treated'''|
+|!1 like a literal|--and is especially useful--|''for test tables.''|
+|^SinceTheyTend| * to have WikiWord symbols in them.|
+
+!2 Hidden table heads
+You can hide the first row of a table. This allows you to write comment tables that just look like ordinary HTML tables.
+The complete table still gets executed, the first row is just hidden by a CSS rule. 
+Precede the first row with a '-'. This also works for literal tables.
+
+'''Markup Text'''
+{{{-!|Comment|
+|Beta|gamma|Delta|
+|1|2|3|}}}
+'''Displays as:'''
+-!|Comment|
+|Beta|gamma|Delta|
+|1|2|3|
+
+!2 Plain Text Tables
+
+!see [[!-PlainTextTable-!][<UserGuide.FitNesseWiki.MarkupLanguageReference.PlainTextTable]]

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/MarkupTable/properties.xml

@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<properties>
+<Files/>
+<Normal/>
+<RecentChanges/>
+<Search/>
+<Static/>
+<WhereUsed/>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/MarkupVariables/content.txt

@@ -0,0 +1,82 @@
+!2 Defining and Expressing Variables.
+You can define a variable to represent any amount of text.
+ * Variable names may contain letters, numbers, periods and underscores; e.g., MYTEST.someVar or user.name or USER_NAME 
+ * You can define a variable in three ways: 
+  * !style_code(!-!define var {text}-!) - as a delimited block of text 
+  * !style_code[!-!define var othervar-!] - by copying the value of another variable 
+  * !style_code(!-!define var {${= 10 / 2 =}}-!) - as an [[expression][MarkupExpressions]] 
+ * The variable text can span many lines as shown below:
+!style_code{!define myVariable {
+This is the
+text of my
+variable
+}}
+!define myVariable {
+this is the
+text of my
+variable
+}
+
+You express the value of a variable like this: !style_code{!-${myVariable}-!}.  This expression is replaced with the value of the variable.
+
+''The value of the variable is: ${myVariable}.''
+
+If the variable value contains wiki markup, it is interpreted as the variable is expressed.
+
+!style_code{!-!define markedUp {This is '''bold'''}-!}
+!define markedUp {This is '''bold'''}
+!style_code{!-${markedUp}-!} is expressed as: ${markedUp}
+
+A variable can reference other variables.
+
+!style_code{!-!define y {y-value}-!}
+!define y {y-value}
+!style_code{!-!define x {The value of y is ${y}}-!}
+!define x {The value of y is ${y}}
+!style_code{!-${x}-!} is expressed as: ${x}
+!style_code{!-!define y {new-y-value}-!}
+!define y {new-y-value}
+!style_code{!-${x}-!} is expressed as: ${x}
+
+A variable can be copied from another variable.
+!style_code{!-!define z y-!}
+!define z y
+!style_code{!-${z}-!} is expressed as: ${z}
+
+A variable can contain an expression
+!style_code{!-!define n 10-!}
+!define n {10}
+!style_code{!-!define q 2 -!}
+!define q {2}
+!style_code{!-!define d {${= ${n} / ${q} =}}-!}
+!define d {${= ${n} / ${q} =}}
+!style_code{!-${d}-!} is : ${d}
+IMPORTANT: If the variables used in the expression change than also the result changes! 
+!style_code{!-!define q 5 -!}
+!define q {5}
+!style_code{!-${d}-!} is : ${d}
+
+!3 Variable Scope
+If a variable is expressed on a page, but is not found, then its parent pages are searched in order.
+If the variable is not found in any ancestor pages, FitNesse will inspect System.properties.
+
+!3 Defining Variables In URL Input
+You can define variables in the URL input by using the format of ''key''=''value'' (''key'' as variable name & ''value'' as variable value).  ''key'' and ''value'' can be any string values.  Multiple variables can be specified separated by ''&''.
+Variable values specified in the URL input are given precedence over variables defined on the page or in System.properties for the same key.
+
+See [[Restful Services][<UserGuide.AdministeringFitNesse.RestfulServices]]
+
+!3 Variables on [[included pages][MarkupPageInclude]]
+ * if you include a sub page into a  main page than you can use the variables define on the main page also in the included pages.
+ * If you modify a variable on the sub page then the main page will also have the modified value.
+ * If you define a variable on the sub page you can reference it later on the main page. 
+See [[Parameterized Includes][<UserGuide.WritingAcceptanceTests.AcceptanceTestPatterns.ParameterizedIncludes]] 
+
+!3 Difference between variables and [[SLIM symbols][<UserGuide.WritingAcceptanceTests.SliM.SymbolsInTables]] 
+ * Variables are evaluated at render time, before the test executes. This allows for values to be set based on page hierarchy and other things that are purely inputs to the tests.
+ * Symbols only exist at execution time. They can be changed at runtime, so are distinct from variables, which cannot.
+
+!3 Predefined Variables
+There are several [[pre-defined variables][<UserGuide.QuickReferenceGuide#VARIABLES]] that you can use on your pages.
+
+See [[Variable fitnesse test][.FitNesse.SuiteAcceptanceTests.SuiteWidgetTests.TestVariables]], [[Parent Variable fitnesse test][.FitNesse.SuiteAcceptanceTests.SuiteWidgetTests.TestParentVariables]], [[Define Variables in System Properties test][.FitNesse.SuiteAcceptanceTests.SuiteWidgetTests.TestVariablesFromSystemProperties]] and [[Variables, Symbols and Include pages][.FitNesse.SuiteAcceptanceTests.SuiteSlimTests.VariablesUsedInSubSubpage]]

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/MarkupVariables/properties.xml

@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<properties>
+<Files/>
+<Normal/>
+<RecentChanges/>
+<Search/>
+<Static/>
+<WhereUsed/>
+<saveId>1238167551817</saveId>
+<ticketId>6509577387506798141</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/PlainTextTable/content.txt

@@ -0,0 +1,76 @@
+Tables can be created very easily from plain text.  
+
+'''Markup Text'''
+{{{![
+simple plain
+text pasted
+from somewhere
+]!}}}----
+'''Displays as:'''
+![
+simple plain
+text pasted
+from somewhere
+]!
+One note on editing plain text tables with the rich text editor: the content is displayed as
+{{{
+<plaintexttable>
+simple plain
+text pasted
+from somewhere
+</plaintexttable>
+}}}
+In order to add extra lines, use <Shift>-<Enter> to add lines when editing the plain text table. It is not possible to create plain text tables from the rich text editor.
+
+----
+These are ''literalized'' tables, so most wiki markup does not work inside them.
+
+You can create cells by declaring a delimiter as the first character after the '''['''.  Only punctuation characters will work.:
+{{{![:
+Name:Bob
+Address:Here
+Street:Cranbrook:Zip:60048
+]!}}}
+'''Displays as:'''
+![:
+Name:Bob
+Address:Here
+Street:Cranbrook:Zip:60048
+]!
+----
+If you want to hide the first row of the table, you can put it right after the delimiter following a space.  The first row is still there, it's just hidden.  
+{{{![: Location
+Name:Bob
+Address:Here
+Street:Cranbrook:Zip:60048
+]!}}}
+'''Displays as:'''
+![: Location
+Name:Bob
+Address:Here
+Street:Cranbrook:Zip:60048
+]!
+----
+If you want to hide the first row but don't want a delimiter, you still need the space right after the '''['''.
+----
+
+Example:
+{{{![ BDD:JukeBoxDriver
+Given a jukebox with price set to $1.00
+When a customer deposits $2.00
+And presses B5
+And presses C21
+Then Stairway to Heaven will play.
+And Comforably Numb will play.
+]!}}}
+'''Displays as:'''
+![ BDD:JukeBoxDriver
+Given a jukebox with price set to $1.00
+When a customer deposits $2.00
+And presses B5
+And presses C21
+Then Stairway to Heaven will play.
+And Comforably Numb will play.
+]!
+
+