<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to Configuration</title><link>https://sourceforge.net/p/specproc2browser/wiki/Configuration/</link><description>Recent changes to Configuration</description><atom:link href="https://sourceforge.net/p/specproc2browser/wiki/Configuration/feed" rel="self"/><language>en</language><lastBuildDate>Tue, 28 Feb 2023 14:21:41 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/specproc2browser/wiki/Configuration/feed" rel="self" type="application/rss+xml"/><item><title>Configuration modified by clochardM33</title><link>https://sourceforge.net/p/specproc2browser/wiki/Configuration/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v22
+++ v23
@@ -3,7 +3,7 @@
 1. Does it run and does it open results pages? The general stuff.
 2. The file locations. The very important web server settings.

-Get to the configuration from **Start** | **SpecProc2Browser** | **SpecProc2Browser Configration**
+Get to the configuration from **Start** | **SpecProc2Browser** | **SpecProc2Browser Configuration**

 The configuration is saved on Close.

@@ -13,14 +13,14 @@
 When this is set SP2B runs automatically at the end of a SpecProc batch.
 If this is not set SP2B does not run.

-**Open Results Page when finsished**
+**Open Results Page when finished**
 When this is set the SpecProc results Summary page(s) are opened in your default web browser.
 If this is not set files are copied to the web server location, but nothing is opened in the web browser.

 ### Server Configuration

 **Web Server wwwRoot File Location**
-The file path to the local web sever web root folder.
+The file path to the local web server web root folder.
 Defaults to `C:\inetpub\wwwroot\` which is correct for IIS See [Web Server Setup]

 * This is the folder that your local web server uses as its home page location.
@@ -42,29 +42,29 @@
 * Don't worry about spaces in names, they are fine, Windows and Browsers sort them out.

 You do not have to change this value for different MassLynx projects. They are automatically structured below this location.
-For example is you processed data from ABC1.PRO and XYZ2.PRO (and you were using the default configuration) they would go into 
+For example. if you processed data from ABC1.PRO and XYZ2.PRO (and you were using the default configuration) they would go into 
 `http://localhost/SpecProcResults/Your data goes here/ABC1.PRO`
 and
 `http://localhost/SpecProcResults/Your data goes here/XYZ2.PRO`

 *Best practice* for situations where you have groupings that are above the project level, say on different instruments, is to maintain that grouping at the difference level using this setting.
-For example if you wish to have results from multiple instruments on the same web server then for each instrument configure this to reflect the instrument.
+For example, if you wish to have results from multiple instruments on the same web server then for each instrument configure this to reflect the instrument.
 This could be something like:

 * `SpecProcResults\Instrument #1\`
 * `SpecProcResults\Instrument #2\`
 * `SpecProcResults\Instrument #N\`
-However there is only one current configuration and results are written into that.
+However, there is only one current configuration and results are written into that.
 It is up to you to maintain this setting as and when you need to change it.

 **Style Sheet File Location - Relative to SpecProc Results**
 The folder that the style sheets are copied into relative to the results folder.
 Defaults to `SpecProcStyles\`

-This is the location of the files used to style and decortate the results files.
+This is the location of the files used to style and decorate the results files.
 It is forced to be relative to the results folder which makes the results folder fully portable as it will maintain the display rules if you copy it to another web server.
 There is no realistic need to ever change this. It is included for completeness.
-However if you change the results folder you need to remake this folder otherwise your web pages will come up blank (there will be no style rules). See below.
+However, if you change the results folder you need to remake this folder otherwise your web pages will come up blank (there will be no style rules). See below.

 **Create Folders/Copy Files**
 Press this button to build the file structure you have configured. This will create the folder paths (where they don't already exist) and copy the necessary style sheets.
@@ -75,6 +75,6 @@
 This is a live set of links to show you what your configuration will create.

 ## Saving Configuration
-You do not need to explicitly save the configuration. It is saved when you close the configration window.
-However if the file validation detects that one or more path does not exist it you will be prompted to create the missing folders and files.
+You do not need to explicitly save the configuration. It is saved when you close the configuration window.
+However, if the file validation detects that one or more path does not exist it you will be prompted to create the missing folders and files.
 You do this by either following the prompt or pressing in the Create Folder/Copy Files button.
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">clochardM33</dc:creator><pubDate>Tue, 28 Feb 2023 14:21:41 -0000</pubDate><guid>https://sourceforge.netffbed7c534941d646bad7372bef41ae7d37a7514</guid></item><item><title>Configuration modified by clochardM33</title><link>https://sourceforge.net/p/specproc2browser/wiki/Configuration/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v21
+++ v22
@@ -70,8 +70,6 @@
 Press this button to build the file structure you have configured. This will create the folder paths (where they don't already exist) and copy the necessary style sheets.
 It does not overwrite any data.

-**Offer Create Folders on close**
-Not supported

 ### File Structure
 This is a live set of links to show you what your configuration will create.
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">clochardM33</dc:creator><pubDate>Tue, 28 Feb 2023 12:17:59 -0000</pubDate><guid>https://sourceforge.net8dd5ba4d6819f02227d23a5fe73109340fedfd9e</guid></item><item><title>Configuration modified by clochardM33</title><link>https://sourceforge.net/p/specproc2browser/wiki/Configuration/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v20
+++ v21
@@ -77,4 +77,6 @@
 This is a live set of links to show you what your configuration will create.

 ## Saving Configuration
-
+You do not need to explicitly save the configuration. It is saved when you close the configration window.
+However if the file validation detects that one or more path does not exist it you will be prompted to create the missing folders and files.
+You do this by either following the prompt or pressing in the Create Folder/Copy Files button.
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">clochardM33</dc:creator><pubDate>Mon, 27 Feb 2023 16:46:53 -0000</pubDate><guid>https://sourceforge.net716a170714bbe8e08a928433c07ee1f4745fa288</guid></item><item><title>Configuration modified by clochardM33</title><link>https://sourceforge.net/p/specproc2browser/wiki/Configuration/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v19
+++ v20
@@ -73,4 +73,8 @@
 **Offer Create Folders on close**
 Not supported

+### File Structure
+This is a live set of links to show you what your configuration will create.

+## Saving Configuration
+
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">clochardM33</dc:creator><pubDate>Mon, 27 Feb 2023 16:44:04 -0000</pubDate><guid>https://sourceforge.net43fa9681ca05330f58a92c26d68af791639fbf92</guid></item><item><title>Configuration modified by clochardM33</title><link>https://sourceforge.net/p/specproc2browser/wiki/Configuration/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v18
+++ v19
@@ -57,3 +57,20 @@
 However there is only one current configuration and results are written into that.
 It is up to you to maintain this setting as and when you need to change it.

+**Style Sheet File Location - Relative to SpecProc Results**
+The folder that the style sheets are copied into relative to the results folder.
+Defaults to `SpecProcStyles\`
+
+This is the location of the files used to style and decortate the results files.
+It is forced to be relative to the results folder which makes the results folder fully portable as it will maintain the display rules if you copy it to another web server.
+There is no realistic need to ever change this. It is included for completeness.
+However if you change the results folder you need to remake this folder otherwise your web pages will come up blank (there will be no style rules). See below.
+
+**Create Folders/Copy Files**
+Press this button to build the file structure you have configured. This will create the folder paths (where they don't already exist) and copy the necessary style sheets.
+It does not overwrite any data.
+
+**Offer Create Folders on close**
+Not supported
+
+
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">clochardM33</dc:creator><pubDate>Mon, 27 Feb 2023 16:42:42 -0000</pubDate><guid>https://sourceforge.net2b4b2f15bff6fd28687d71f7526d52280c5e0211</guid></item><item><title>Configuration modified by clochardM33</title><link>https://sourceforge.net/p/specproc2browser/wiki/Configuration/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v17
+++ v18
@@ -47,9 +47,13 @@
 and
 `http://localhost/SpecProcResults/Your data goes here/XYZ2.PRO`

-*Best practice* for situations where you have groupings that are above the project level, say on different instruments, is to maintain that grouping at this level.
+*Best practice* for situations where you have groupings that are above the project level, say on different instruments, is to maintain that grouping at the difference level using this setting.
 For example if you wish to have results from multiple instruments on the same web server then for each instrument configure this to reflect the instrument.
 This could be something like:
+
 * `SpecProcResults\Instrument #1\`
 * `SpecProcResults\Instrument #2\`
 * `SpecProcResults\Instrument #N\`
+However there is only one current configuration and results are written into that.
+It is up to you to maintain this setting as and when you need to change it.
+
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">clochardM33</dc:creator><pubDate>Mon, 27 Feb 2023 16:34:34 -0000</pubDate><guid>https://sourceforge.net2cca90ec08ee047ad297b33e6f460ab39fdc1e5d</guid></item><item><title>Configuration modified by clochardM33</title><link>https://sourceforge.net/p/specproc2browser/wiki/Configuration/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v16
+++ v17
@@ -23,22 +23,23 @@
 The file path to the local web sever web root folder.
 Defaults to `C:\inetpub\wwwroot\` which is correct for IIS See [Web Server Setup]

-This is the folder that your local web server uses as its home page location.
-All other file paths are relative to this.
-It is essential that this is correct otherwise all file and web-page-open actions will use invalid addressing.
-The validation icon reflects the folders status.
+* This is the folder that your local web server uses as its home page location.
+* All other file paths are relative to this.
+* It is essential that this is correct otherwise all file and web-page-open actions will use invalid addressing.
+* The validation icon reflects the folders status.

 *Best practice* is to Browse to the location rather than typing it in. This will ensure that the folder exists and the syntax is correct.
+

 **SpecProc Results Folder  - Relative to wwwRoot**
 The folder that your SpecProc results are copied into.
 Defaults to `SpecProcResults\Your data goes here\`

-It is relative to the web server root.
-This can have any value and as many levels as you you like, provided it makes a value URL.
-This is same as the address you would type into a browser to get to your results files.
-For example with the default value you would go to `http://localhost/SpecProcResults/Your data goes here/`
-Don't worry about spaces in names, they are fine, Windows and Browsers sort them out.
+* It is relative to the web server root.
+* This can have any value and as many levels as you you like, provided it makes a value URL.
+* This is same as the address you would type into a browser to get to your results files.
+* For example with the default value you would go to `http://localhost/SpecProcResults/Your data goes here/`
+* Don't worry about spaces in names, they are fine, Windows and Browsers sort them out.

 You do not have to change this value for different MassLynx projects. They are automatically structured below this location.
 For example is you processed data from ABC1.PRO and XYZ2.PRO (and you were using the default configuration) they would go into 
@@ -46,3 +47,9 @@
 and
 `http://localhost/SpecProcResults/Your data goes here/XYZ2.PRO`

+*Best practice* for situations where you have groupings that are above the project level, say on different instruments, is to maintain that grouping at this level.
+For example if you wish to have results from multiple instruments on the same web server then for each instrument configure this to reflect the instrument.
+This could be something like:
+* `SpecProcResults\Instrument #1\`
+* `SpecProcResults\Instrument #2\`
+* `SpecProcResults\Instrument #N\`
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">clochardM33</dc:creator><pubDate>Mon, 27 Feb 2023 16:31:23 -0000</pubDate><guid>https://sourceforge.netac64f274561afbf9a8153158ce2cb5265860d6ee</guid></item><item><title>Configuration modified by clochardM33</title><link>https://sourceforge.net/p/specproc2browser/wiki/Configuration/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v15
+++ v16
@@ -40,3 +40,9 @@
 For example with the default value you would go to `http://localhost/SpecProcResults/Your data goes here/`
 Don't worry about spaces in names, they are fine, Windows and Browsers sort them out.

+You do not have to change this value for different MassLynx projects. They are automatically structured below this location.
+For example is you processed data from ABC1.PRO and XYZ2.PRO (and you were using the default configuration) they would go into 
+`http://localhost/SpecProcResults/Your data goes here/ABC1.PRO`
+and
+`http://localhost/SpecProcResults/Your data goes here/XYZ2.PRO`
+
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">clochardM33</dc:creator><pubDate>Mon, 27 Feb 2023 16:23:52 -0000</pubDate><guid>https://sourceforge.net089bbc01be5012671fad2017d5b7749ae8e937a5</guid></item><item><title>Configuration modified by clochardM33</title><link>https://sourceforge.net/p/specproc2browser/wiki/Configuration/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v14
+++ v15
@@ -37,6 +37,6 @@
 It is relative to the web server root.
 This can have any value and as many levels as you you like, provided it makes a value URL.
 This is same as the address you would type into a browser to get to your results files.
+For example with the default value you would go to `http://localhost/SpecProcResults/Your data goes here/`
+Don't worry about spaces in names, they are fine, Windows and Browsers sort them out.

-
-
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">clochardM33</dc:creator><pubDate>Mon, 27 Feb 2023 16:19:45 -0000</pubDate><guid>https://sourceforge.net8911e8814402a6f0354bab81c5729c425d8b1d77</guid></item><item><title>Configuration modified by clochardM33</title><link>https://sourceforge.net/p/specproc2browser/wiki/Configuration/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v13
+++ v14
@@ -21,7 +21,7 @@

 **Web Server wwwRoot File Location**
 The file path to the local web sever web root folder.
-*Defaults to* C:\inetpub\wwwroot\ which is correct for IIS See [Web Server Setup]
+Defaults to `C:\inetpub\wwwroot\` which is correct for IIS See [Web Server Setup]

 This is the folder that your local web server uses as its home page location.
 All other file paths are relative to this.
@@ -32,7 +32,7 @@

 **SpecProc Results Folder  - Relative to wwwRoot**
 The folder that your SpecProc results are copied into.
-*Defaults to* SpecProcResults\Your data goes here\
+Defaults to `SpecProcResults\Your data goes here\`

 It is relative to the web server root.
 This can have any value and as many levels as you you like, provided it makes a value URL.
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">clochardM33</dc:creator><pubDate>Mon, 27 Feb 2023 16:16:53 -0000</pubDate><guid>https://sourceforge.net86ccba4b961a33a91732c220ea0cac73dbbbdd77</guid></item></channel></rss>