Initial Load
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/.cvsignore b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/.cvsignore
new file mode 100644
index 0000000..6161a14
--- /dev/null
+++ b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/.cvsignore
@@ -0,0 +1,2 @@
+net.sf.vex.help_1.0.0.jar
+toc.html
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/.project b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/.project
new file mode 100644
index 0000000..83dd99c
--- /dev/null
+++ b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/.project
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.wst.xml.vex.documentation</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ <buildCommand>
+ <name>org.eclipse.pde.ManifestBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.pde.SchemaBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ </buildSpec>
+ <natures>
+ <nature>org.eclipse.pde.PluginNature</nature>
+ </natures>
+</projectDescription>
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/.template b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/.template
new file mode 100644
index 0000000..d65e0f4
--- /dev/null
+++ b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/.template
@@ -0,0 +1,4 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<form>
+ <p/><p><b>Tips on working with this plug-in project</b></p><li>For the view of the new plug-in at a glance, go to the <img href="pageImage"/><a href="OverviewPage">Overview</a>.</li><li>You can test the contributions of this plug-in by launching another instance of the workbench. On the <b>Run</b> menu, click <b>Run As</b> and choose <img href="runTimeWorkbenchImage"/><a href="action.run">Run-time Workbench</a> from the available choices.</li><li>You can add more functionality to this plug-in by adding extensions using the <a href="action.newExtension">New Extension Wizard</a>.</li><li>The plug-in project contains Java code that you can debug. Place breakpoints in Java classes. On the <b>Run</b> menu, select <b>Debug As</b> and choose <img href="runTimeWorkbenchImage"/><a href="action.debug">Run-time Workbench</a> from the available choices.</li>
+</form>
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/META-INF/MANIFEST.MF b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/META-INF/MANIFEST.MF
new file mode 100644
index 0000000..ccbb4aa
--- /dev/null
+++ b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/META-INF/MANIFEST.MF
@@ -0,0 +1,8 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: %plugin.name
+Bundle-Version: 0.5.0.qualifier
+Bundle-Vendor: %plugin.provider
+Bundle-SymbolicName: org.eclipse.wst.xml.vex.documentation;singleton:=true
+Require-Bundle: org.eclipse.help
+Bundle-Localization: plugin
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/build.properties b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/build.properties
new file mode 100644
index 0000000..7ab033f
--- /dev/null
+++ b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/build.properties
@@ -0,0 +1,6 @@
+bin.includes = plugin.xml,\
+ html/,\
+ toc.xml,\
+ tocconcepts.xml,\
+ toctasks.xml,\
+ META-INF/
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/build.xml b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/build.xml
new file mode 100644
index 0000000..8c4cd61
--- /dev/null
+++ b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/build.xml
@@ -0,0 +1,7 @@
+<project default="build">
+
+ <target name="build">
+ <xslt style="toc.xsl" in="toc.xml" out="toc.html" />
+ </target>
+
+</project>
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/concepts/editing.html b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/concepts/editing.html
new file mode 100644
index 0000000..f385bc7
--- /dev/null
+++ b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/concepts/editing.html
@@ -0,0 +1,22 @@
+<?xml version='1.0'?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+
+ <head>
+
+ <title>Editing Documents</title>
+
+ </head>
+
+ <body>
+
+ <h1>Editing Documents</h1>
+
+ <p>There are some subtle differences between editing a structured
+ document with Vex and using a regular word processor. The following
+ describes some of these differences.</p>
+
+ </body>
+
+</html>
+
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/concepts/extending.html b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/concepts/extending.html
new file mode 100644
index 0000000..f504227
--- /dev/null
+++ b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/concepts/extending.html
@@ -0,0 +1,30 @@
+<?xml version='1.0'?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+
+ <head>
+
+ <title>Extending Vex</title>
+
+ </head>
+
+ <body>
+
+ <h1>Extending Vex</h1>
+
+ <p>While Vex supports common document types such as DocBook and
+ XHTML out-of-the-box, you can also extend Vex with your own DTD
+ files and CSS stylesheets.</p>
+
+ <p>The first step to extending Vex is to
+ <a href="../tasks/create-plugin-project.html">create a plug-in
+ project</a>. Once this is done, you can copy the DTD and CSS files
+ you wish into the plug-in project. Finally, you must provide a
+ little more information to Vex by setting properties on the new DTD
+ and CSS files. Note that you must provide both a DTD and a CSS file
+ to be able to edit documents of the given type.</p>
+
+ </body>
+
+</html>
+
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/concepts/inserting.html b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/concepts/inserting.html
new file mode 100644
index 0000000..61d0872
--- /dev/null
+++ b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/concepts/inserting.html
@@ -0,0 +1,36 @@
+<?xml version='1.0'?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+
+ <head>
+
+ <title>Inserting Elements</title>
+
+ </head>
+
+ <body>
+
+ <h1>Inserting Elements</h1>
+
+ <p>As you create a document, you apply structure by inserting
+ elements. You insert a new element into a Vex document by
+ positioning the caret at the desired position, clicking the right
+ mouse button, and selecting <b>Insert ></b> <i>elementname</i>
+ from the context menu.</p>
+
+ <p>Vex is aware of the DTD that specifies the structure of your
+ document, and will not allow you to insert an element that violates
+ this structure. The list of elements that are available to insert
+ are therefore dependent on the current location of the caret.
+ Similarly, Vex will not allow you to enter text where it is not
+ permitted by the DTD.</p>
+
+ <p>If some content is selected when an element is inserted, the
+ selected content is placed within the inserted element. This is
+ handy when you have forgotten to apply an element, or when you wish
+ to rapidly enter text first and apply structure later.</p>
+
+ </body>
+
+</html>
+
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/concepts/selection.html b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/concepts/selection.html
new file mode 100644
index 0000000..a1e94b2
--- /dev/null
+++ b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/concepts/selection.html
@@ -0,0 +1,31 @@
+<?xml version='1.0'?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+ <title>Selection</title>
+ </head>
+ <body>
+ <h1>Selection</h1>
+ <p>The act of selecting a block of text to replace or to surround
+ with an element is performed the same in Vex as in most word
+ processors: by moving the caret while holding the <b>Shift</b> key
+ or by dragging the mouse between two positions. The main difference
+ is that in some cases, Vex will expand the selection so that it
+ does not span only a portion of an element.</p>
+ <p>To see this in action, place the caret in the middle of an
+ inline element containing some text. While holding the <b>Shift</b>
+ key, move the caret towards the end of the element. As the caret
+ passes the end marker for the element, note that the starting point
+ of the selection jumps to the start of the element. If you move the
+ caret back inside the element (while still holding <b>Shift</b>),
+ you'll notice that the start of the selection jumps back to its
+ original place.</p>
+ <p>When a block element is selected, Vex draws an outline around
+ the entire block, showing the element name in the lower right
+ corner. This allows you to see that the entire element is selected
+ rather than just its contents.</p>
+ <p>This selection behaviour is Vex's way of preserving the
+ structure of the document. It is based on the assumption that
+ normally you want to manage entire elements.</p>
+ </body>
+</html>
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/concepts/split-join.html b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/concepts/split-join.html
new file mode 100644
index 0000000..5a37271
--- /dev/null
+++ b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/concepts/split-join.html
@@ -0,0 +1,21 @@
+<?xml version='1.0'?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+ <title>Splits and Joins</title>
+ </head>
+ <body>
+ <h1>Splits and Joins</h1>
+ <p>Users indicate the end of a paragraph to a word processor by
+ pressing the <b>Enter</b> key. Vex has no built-in concept of
+ paragraphs; instead, this behaviour is simulated by using a <i>split
+ </i>. When you press the <b>Enter</b> key, Vex attempts to make two
+ copies of the current element, splitting the element content
+ between the two. Pressing <b>Enter</b> at the end of a paragraph
+ results in a new, empty paragraph, just as in a word processor.</p>
+ <p>A related concept is a <i>join</i>, where two elements of the
+ same type are joined together into one. You join two elements (such
+ as two paragraphs) by placing the caret near the boundary of the
+ elements and pressing <b>Backspace</b> or <b>Delete</b>.</p>
+ </body>
+</html>
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/concepts/unwrap-morph.html b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/concepts/unwrap-morph.html
new file mode 100644
index 0000000..a7af20b
--- /dev/null
+++ b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/concepts/unwrap-morph.html
@@ -0,0 +1,23 @@
+<?xml version='1.0'?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+ <title>Unwrapping and Morphing</title>
+ </head>
+ <body>
+ <h1>Unwrapping and Morphing</h1>
+ <p>Occasionally, you may find that you wish to delete an element
+ but leave the element's content in place. Vex provides this
+ shortcut in the <i>unwrap</i> command. To unwrap an element, simply
+ place the caret within the element (but not within a sub-element of
+ that element!), click the right mouse button, and select <b>Unwrap
+ </b>.</p>
+ <p>A similar operation is to replace the current element with a
+ different one. In Vex this is known as <i>morphing</i>. To morph an
+ element, position the caret within the element, click the right
+ mouse button, select <b>Morph</b>, then the name of the element to
+ which the element hsould be morphed.</p>
+ <p>As when inserting elements, Vex prevents unwraps and morphs that
+ would otherwise invalidate the document structure.</p>
+ </body>
+</html>
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/tasks/create-plugin-project.html b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/tasks/create-plugin-project.html
new file mode 100644
index 0000000..7282564
--- /dev/null
+++ b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/tasks/create-plugin-project.html
@@ -0,0 +1,48 @@
+<?xml version='1.0'?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+
+ <head>
+
+ <title>Creating a Plug-in Project</title>
+
+ </head>
+
+ <body>
+
+ <h1>Creating a Plug-in Project</h1>
+
+ <p>Vex can be extended to handle new document types by placing DTD
+ and CSS files into a special kind of project called a <i>plug-in
+ project</i>. You can create a plug-in project as follows.</p>
+
+ <ol>
+
+ <li>From the main menu, select <b>File > New >
+ Project...</b>.</li>
+
+ <li>Under the Vex folder in the resulting dialog, select Vex
+ Plug-in Project and click Next >.</li>
+
+ <li>Enter a name for you project and optionally a location in the
+ filesystem to place the project folder, then click Finish.</li>
+
+ </ol>
+
+ <p>The project will appear in the Navigator view with a folder icon
+ that has the Vex logo in the top left corner.</p>
+
+ <h5>Related Tasks</h5>
+
+ <ul>
+
+ <li><a href="register-dtd.html">Registering a DTD</a></li>
+
+ <li><a href="register-css.html">Registering a CSS file</a></li>
+
+ </ul>
+
+ </body>
+
+</html>
+
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/tasks/register-css.html b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/tasks/register-css.html
new file mode 100644
index 0000000..20c0e84
--- /dev/null
+++ b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/tasks/register-css.html
@@ -0,0 +1,57 @@
+<?xml version='1.0'?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+
+ <head>
+
+ <title>Registering a CSS Stylesheet</title>
+
+ </head>
+
+ <body>
+
+ <h1>Registering a CSS Stylesheet</h1>
+
+ <p>Vex uses a CSS stylesheet to determine the fonts, colours, and
+ spacing to use while editing your document. You can register a new
+ CSS stylesheet with Vex as follows.</p>
+
+ <ol>
+
+ <li>If necessary, <a href="create-plugin-project.html">create a
+ plug-in project</a> to contain your stylesheet.</li>
+
+ <li>Copy the CSS file and any related files to a directory in the
+ plug-in project. If you copy these files outside of Eclipse, you
+ may have to refresh the workspace in Eclipse by right-clicking
+ the project in the Navigator and selecting <b>Refresh</b> from
+ the context menu.</li>
+
+ <li>In the Navigator, right-click the CSS file and select
+ <b>Properties</b>.</li>
+
+ <li>Select the Vex Style property page and provide a Name for
+ your stylesheet. You must also select all document types to which
+ the style applies. Click OK when done.</li>
+
+ </ol>
+
+ <p>You can confirm that your DTD file was successfully registered
+ by checking out the <a href="show-configuration-view.html">Vex
+ Configuration view</a>.</p>
+
+ <h5>Related Tasks</h5>
+
+ <ul>
+
+ <li><a href="create-plugin-project.html">Creating a Plug-in
+ Project</a></li>
+
+ <li><a href="register-dtd.html">Registering a DTD</a></li>
+
+ </ul>
+
+ </body>
+
+</html>
+
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/tasks/register-dtd.html b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/tasks/register-dtd.html
new file mode 100644
index 0000000..fe075c7
--- /dev/null
+++ b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/tasks/register-dtd.html
@@ -0,0 +1,61 @@
+<?xml version='1.0'?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+
+ <head>
+
+ <title>Creating a New Document Type</title>
+
+ </head>
+
+ <body>
+
+ <h1>Registering a DTD</h1>
+
+ <p>You can register a new document type with Vex if you have a DTD
+ file describing the document structure.</p>
+
+ <ol>
+
+ <li>If necessary, <a href="create-plugin-project.html">create a
+ plug-in project</a> to contain your DTD.</li>
+
+ <li>Copy the DTD file and any related files to a directory in the
+ plug-in project. If you copy these files outside of Eclipse, you
+ may have to refresh the workspace in Eclipse by right-clicking
+ the project in the Navigator and selecting <b>Refresh</b> from
+ the context menu.</li>
+
+ <li>In the Navigator, right-click the DTD file and select
+ <b>Properties</b>.</li>
+
+ <li>Select the Vex Document Type property page and provide a
+ Name, Public ID, and System ID to use for this document type. You
+ may optionally select which elements in the DTD may be used for
+ document root elements when done. Click OK when done.</li>
+
+ </ol>
+
+ <p>You can confirm that your DTD file was successfully registered
+ by checking out the <a href="show-configuration-view.html">Vex
+ Configuration view</a>.</p>
+
+ <p>Note that you must also <a href="register-css.html">register a
+ CSS stylesheet</a> and bind it to your new document type before you
+ can edit documents with the type.</p>
+
+ <h5>Related Tasks</h5>
+
+ <ul>
+
+ <li><a href="create-plugin-project.html">Creating a Plug-in
+ Project</a></li>
+
+ <li><a href="register-css.html">Registering a CSS file</a></li>
+
+ </ul>
+
+ </body>
+
+</html>
+
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/tasks/show-configuration-view.html b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/tasks/show-configuration-view.html
new file mode 100644
index 0000000..3cec0d2
--- /dev/null
+++ b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/tasks/show-configuration-view.html
@@ -0,0 +1,32 @@
+<?xml version='1.0'?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+
+ <head>
+
+ <title>Displaying the Vex Configuration View</title>
+
+ </head>
+
+ <body>
+
+ <h1>Displaying the Vex Configuration View</h1>
+
+ <p>The Vex Configuration view shows all document types and styles
+ registered with Vex. It is useful for confirming that you have
+ successfully registered new document types and styles in a plug-in
+ project.</p>
+
+ <ul>
+
+ <li>From the main menu, select <b>Window > Show View >
+ Other...</b>.</li>
+
+ <li>Under the Vex folder, select <b>Vex Configuration</b>.</li>
+
+ </ul>
+
+ </body>
+
+</html>
+
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/toc.html b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/toc.html
new file mode 100644
index 0000000..dced7f9
--- /dev/null
+++ b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/html/toc.html
@@ -0,0 +1,21 @@
+<?xml version='1.0'?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+
+ <head>
+
+ <title>Vex User Guide</title>
+
+ </head>
+
+ <body>
+
+ <h1>Vex User Guide</h1>
+
+ <p>Welcome to the Vex User Guide. Please select the desired concept
+ or task from the links in the left pane.</p>
+
+ </body>
+
+</html>
+
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/plugin.properties b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/plugin.properties
new file mode 100644
index 0000000..b874dcc
--- /dev/null
+++ b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/plugin.properties
@@ -0,0 +1,2 @@
+plugin.name=VEX Documentation (Incubating)
+plugin.provider=Eclipse.org
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/plugin.xml b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/plugin.xml
new file mode 100644
index 0000000..6216fb5
--- /dev/null
+++ b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/plugin.xml
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?eclipse version="3.2"?>
+<plugin>
+
+ <extension
+ point="org.eclipse.help.toc">
+ <toc
+ file="toc.xml"
+ primary="true">
+ </toc>
+ <toc
+ file="tocconcepts.xml">
+ </toc>
+ <toc
+ file="toctasks.xml">
+ </toc>
+ </extension>
+
+</plugin>
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/toc.xml b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/toc.xml
new file mode 100644
index 0000000..92fa499
--- /dev/null
+++ b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/toc.xml
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?NLS TYPE="org.eclipse.help.toc"?>
+
+<toc label="Vex User Guide" topic="html/toc.html">
+ <topic label="Concepts">
+ <anchor id="concepts"/>
+ </topic>
+ <topic label="Tasks">
+ <anchor id="tasks"/>
+ </topic>
+</toc>
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/toc.xsl b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/toc.xsl
new file mode 100644
index 0000000..368bf8a
--- /dev/null
+++ b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/toc.xsl
@@ -0,0 +1,52 @@
+<!--
+
+ Stylesheet for creating the file html/toc.html based on tocconcepts.xml
+ and toctasks.xml.
+
+-->
+<xsl:stylesheet version="1.0"
+ xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
+
+
+ <xsl:template match="/">
+ <html>
+ <head>
+ <title>Vex User Guide</title>
+ </head>
+ <body>
+
+ <xsl:apply-templates/>
+
+ </body>
+ </html>
+ </xsl:template>
+
+ <xsl:template match="toc" name="toc">
+ <xsl:param name="hlevel" select="1"/>
+ <xsl:element name="h{$hlevel}">
+ <xsl:value-of select="@label"/>
+ </xsl:element>
+ <xsl:apply-templates/>
+ </xsl:template>
+
+ <xsl:template match="topic[anchor]">
+ <xsl:for-each select="document(concat('toc', anchor/@id, '.xml'))/toc">
+ <xsl:call-template name="toc">
+ <xsl:with-param name="hlevel" select="2"/>
+ </xsl:call-template>
+ </xsl:for-each>
+ </xsl:template>
+
+ <xsl:template match="topic[topic]">
+ <li><a href="{@href}"><xsl:value-of select="@label"/></a></li>
+ <ul>
+ <xsl:apply-templates/>
+ </ul>
+ </xsl:template>
+
+ <xsl:template match="topic">
+ <li><a href="{@href}"><xsl:value-of select="@label"/></a></li>
+ </xsl:template>
+
+</xsl:stylesheet>
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/tocconcepts.xml b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/tocconcepts.xml
new file mode 100644
index 0000000..3fda2ab
--- /dev/null
+++ b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/tocconcepts.xml
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?NLS TYPE="org.eclipse.help.toc"?>
+
+<toc label="Concepts" link_to="toc.xml#concepts">
+ <topic label="Editing Documents" href="html/concepts/editing.html">
+ <topic label="Inserting Elements" href="html/concepts/inserting.html" />
+ <topic label="Selection" href="html/concepts/selection.html" />
+ <topic label="Unwrapping and Morphing" href="html/concepts/unwrap-morph.html" />
+ <topic label="Splits and Joins" href="html/concepts/split-join.html" />
+ </topic>
+ <topic label="Extending Vex" href="html/concepts/extending.html"/>
+</toc>
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/toctasks.xml b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/toctasks.xml
new file mode 100644
index 0000000..995267c
--- /dev/null
+++ b/sourceediting/documentation/org.eclipse.wst.xml.vex.documentation/toctasks.xml
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?NLS TYPE="org.eclipse.help.toc"?>
+
+<toc label="Tasks" link_to="toc.xml#tasks">
+ <topic label="Creating a Plug-in Project" href="html/tasks/create-plugin-project.html"/>
+ <topic label="Registering a DTD" href="html/tasks/register-dtd.html"/>
+ <topic label="Registering a CSS Stylesheet" href="html/tasks/register-css.html"/>
+ <topic label="Displaying the Vex Configuration View" href="html/tasks/show-configuration-view.html"/>
+</toc>