Modified: forrest/site/pluginDocs/plugins_0_80/usingPlugins.html URL: http://svn.apache.org/viewcvs/forrest/site/pluginDocs/plugins_0_80/usingPlugins.html?rev=357603&r1=357602&r2=357603&view=diff ============================================================================== --- forrest/site/pluginDocs/plugins_0_80/usingPlugins.html (original) +++ forrest/site/pluginDocs/plugins_0_80/usingPlugins.html Sun Dec 18 17:31:25 2005 @@ -192,7 +192,7 @@ plugin mechanism.</p> <a name="N10016"></a><a name="What+plugins+are+available%3F"></a> <h3 class="underlined_5">What plugins are available?</h3> -<p>You can run the command <span class="codefrag ">forrest available-plugins</span> to get +<p>You can run the command <span class="codefrag">forrest available-plugins</span> to get a list of the known plugins for Forrest.</p> <p>If you would like to have your own plugin added to this list then contact the <a href="../../mail-lists.html">developer mailing list</a>.</p> @@ -203,11 +203,11 @@ <h2 class="underlined_10">How is a Plugin Installed?</h2> <div class="section"> <p>If a site requires one or more plugins then the site designer will - have named them in the <span class="codefrag ">project.required.plugins</span> property - in the projects <span class="codefrag ">forrest.properties</span> file. When Forrest + have named them in the <span class="codefrag">project.required.plugins</span> property + in the projects <span class="codefrag">forrest.properties</span> file. When Forrest builds the site it will automatically discover the plugin and install it. In otherwords, the user need do nothing. For example, - <span class="codefrag ">project.required.plugins=org.apache.forrest.plugin.input.OpenOffice.org,org.apache.forrest.plugin.input.simplifiedDocbook</span> + <span class="codefrag">project.required.plugins=org.apache.forrest.plugin.input.OpenOffice.org,org.apache.forrest.plugin.input.simplifiedDocbook</span> will cause Forrest to load the plugins called "org.apache.forrest.plugin.input.OpenOffice.org" and "org.apache.forrest.plugin.input.simplifiedDocbook".</p> <p>In the absence of a version number for the plugin (as is the case in the examples above) @@ -216,7 +216,7 @@ is incompatible with your current site. To force Forrest into using a specific version of a plugin you shuld add "-VERSION_NUMBER" to the end of the plugin name. For example, to force forrest to use the 1.0 version of the OpenOffice.org plugin you would use - <span class="codefrag ">org.apache.forrest.plugin.input.OpenOffice.org-1.0</span> If you define a version of the + <span class="codefrag">org.apache.forrest.plugin.input.OpenOffice.org-1.0</span> If you define a version of the plugin that does not exist then it will fall back to using the most recent version avialable. This feature is useful when developing a new site as you can quickly force a plugin upgrade by deleting all installed @@ -231,25 +231,25 @@ At this time some of the functionality previously in Forrest was extracted into a plugin. However, we have not broken backward compatability with earlier versions. In the absence of a - <span class="codefrag ">project.required.plugins</span> property in the projects - <span class="codefrag ">forrest.properties</span> file all plugins that contain + <span class="codefrag">project.required.plugins</span> property in the projects + <span class="codefrag">forrest.properties</span> file all plugins that contain functionality previously part of Forrest itself will be loaded automatically. Unless you intend to use new functionality provided by a plugin you will not need to make any changes top your project.</p> <p>If you do require additional plugin functionality, be sure to include all required plugins in the - <span class="codefrag ">project.required.plugins</span> property in the project's - <span class="codefrag ">forrest.properties</span>. You can view - <span class="codefrag ">main/webapp/default-forrest.properties</span> + <span class="codefrag">project.required.plugins</span> property in the project's + <span class="codefrag">forrest.properties</span>. You can view + <span class="codefrag">main/webapp/default-forrest.properties</span> to see the names of plugins that provide previously core functionality.</p> <p>It is also worth noting that there is a small performance improvement if you remove plugins that are not in use. Therefore, if you do not use one or more of the plugins named in the - <span class="codefrag ">project.required.plugins</span> property of - <span class="codefrag ">main/webapp/default-forrest.properties</span> + <span class="codefrag">project.required.plugins</span> property of + <span class="codefrag">main/webapp/default-forrest.properties</span> it is recomended that you override this value in your project's - <span class="codefrag ">forrest.properties</span> file.</p> + <span class="codefrag">forrest.properties</span> file.</p> </div> @@ -260,7 +260,7 @@ and full docbook plugins may try and process the same files. In this instance the one that is mounted first will take precedence. Plugins are mounted in the order they appear in the - <span class="codefrag ">project.required.plugins</span> property, therefore the mounting + <span class="codefrag">project.required.plugins</span> property, therefore the mounting order and therefore processing precedence is under user control.</p> </div>
Modified: forrest/site/tools/eclipse.html URL: http://svn.apache.org/viewcvs/forrest/site/tools/eclipse.html?rev=357603&r1=357602&r2=357603&view=diff ============================================================================== --- forrest/site/tools/eclipse.html (original) +++ forrest/site/tools/eclipse.html Sun Dec 18 17:31:25 2005 @@ -332,7 +332,7 @@ </h3> <p> First, you need to activate the Site.xml view. This can be done by: - <span class="codefrag "> + <span class="codefrag"> Window -> Show View -> Other... -> Forrest -> SiteXML -> OK </span> Now you will see the the view open up in Eclipse. To view a tree, click on the project you are working and you should see the structure of the site.xml as a tree in the view. @@ -374,7 +374,7 @@ </h3> <p> First, you need to activate the Tab.xml view. This can be done by: - <span class="codefrag "> + <span class="codefrag"> Window -> Show View -> Other... -> Forrest -> TabXML -> OK </span> Now you will see the the view open up in Eclipse. To view a tree, click on the project you are working and you should see the structure of the tabs.xml as a tree in the view. Modified: forrest/site/tools/forrestbar.html URL: http://svn.apache.org/viewcvs/forrest/site/tools/forrestbar.html?rev=357603&r1=357602&r2=357603&view=diff ============================================================================== --- forrest/site/tools/forrestbar.html (original) +++ forrest/site/tools/forrestbar.html Sun Dec 18 17:31:25 2005 @@ -192,7 +192,7 @@ downloaded .xpi file into your browser's window and drop it.</p> <p>To build ForrestBar locally rather than downloading, go to FORREST_HOME/tools/forrestbar and run the following command: - <span class="codefrag ">forrest -f build.xml</span> and the .xpi file will be built for you + <span class="codefrag">forrest -f build.xml</span> and the .xpi file will be built for you in FORREST_HOME/tools/forrestbar/build. You can then install it by dragging and dropping as indicated above.</p> </div> Modified: forrest/site/tools/forrestbot-web-interface.html URL: http://svn.apache.org/viewcvs/forrest/site/tools/forrestbot-web-interface.html?rev=357603&r1=357602&r2=357603&view=diff ============================================================================== --- forrest/site/tools/forrestbot-web-interface.html (original) +++ forrest/site/tools/forrestbot-web-interface.html Sun Dec 18 17:31:25 2005 @@ -195,8 +195,8 @@ <h2 class="underlined_10">Build</h2> <div class="section"> <p>To build the webapp from source, you need <a href="http://maven.apache.org/";>Apache Maven</a> installed. From a - command prompt, go to the <span class="codefrag ">forrest/tools/forrestbot/webapp</span> - directory and execute "<span class="codefrag ">maven war</span>".</p> + command prompt, go to the <span class="codefrag">forrest/tools/forrestbot/webapp</span> + directory and execute "<span class="codefrag">maven war</span>".</p> </div> Modified: forrest/site/tools/xxe.html URL: http://svn.apache.org/viewcvs/forrest/site/tools/xxe.html?rev=357603&r1=357602&r2=357603&view=diff ============================================================================== --- forrest/site/tools/xxe.html (original) +++ forrest/site/tools/xxe.html Sun Dec 18 17:31:25 2005 @@ -202,8 +202,8 @@ <div class="section"> <ol> -<li>Delete the <span class="codefrag ">forrest</span> directory from the XXE application - config directory. (e.g. <span class="codefrag ">D:\Program +<li>Delete the <span class="codefrag">forrest</span> directory from the XXE application + config directory. (e.g. <span class="codefrag">D:\Program Files\XMLmind_XML_Editor\config</span>) <ul> @@ -227,13 +227,13 @@ <ol> <li>Extract into the XXE application config directory (e.g. - <span class="codefrag ">D:\Program Files\XMLmind_XML_Editor\config</span>)<br> + <span class="codefrag">D:\Program Files\XMLmind_XML_Editor\config</span>)<br> <strong>OR</strong> </li> <li>Extract into your XXE user directory (e.g. - <span class="codefrag ">~/.xxe/addon/config</span>) (only in version 1.3+ of this config). + <span class="codefrag">~/.xxe/addon/config</span>) (only in version 1.3+ of this config). From version 1.3, this is the recommended installation location, as it permits upgrading XXE without having to reinstall this config</li> @@ -250,16 +250,16 @@ <li>Make sure the FORREST_HOME environment variable is set</li> -<li>Change directory to <span class="codefrag ">forrest/tools/xxe</span> +<li>Change directory to <span class="codefrag">forrest/tools/xxe</span> </li> -<li>Run <span class="codefrag ">ant</span> in this directory</li> +<li>Run <span class="codefrag">ant</span> in this directory</li> </ol> <p>To work directly with the SVN version, check out http://svn.apache.org/repos/asf/forrest/trunk/tools/xxe/ into the - <span class="codefrag ">forrest</span> folder in the XXE <span class="codefrag ">config</span> folder. Run the + <span class="codefrag">forrest</span> folder in the XXE <span class="codefrag">config</span> folder. Run the build there to copy the DTDs</p> <p> <a href="http://www.xmlmind.com/xmleditor/_distrib/docs/configure/index.html";>XXE Modified: forrest/site/zone.html URL: http://svn.apache.org/viewcvs/forrest/site/zone.html?rev=357603&r1=357602&r2=357603&view=diff ============================================================================== --- forrest/site/zone.html (original) +++ forrest/site/zone.html Sun Dec 18 17:31:25 2005 @@ -230,7 +230,7 @@ <div class="section"> <p> Configuration files and directory structures are stored in SVN at - <span class="codefrag ">https://svn.apache.org/repos/asf/forrest/zone</span> + <span class="codefrag">https://svn.apache.org/repos/asf/forrest/zone</span> </p> <p> @@ -287,7 +287,7 @@ </p> <p> Various local software is installed in - <span class="codefrag ">/export/opt/</span> (not managed with SVN) ... + <span class="codefrag">/export/opt/</span> (not managed with SVN) ... </p> <a name="N10065"></a><a name="s-forrest"></a> <h3 class="underlined_5">Forrest</h3>
