// BUILD THE TOPIC DATABASE
//      place the topic code generated in the admin.htm
//      the order topics appear here does not matter,
//      they are referenced by the contents tree or
//      search results
/////////////////

searchDB[schix] = new Array();
searchDB[schix]["ID"] =				"topIntroduction";
searchDB[schix]["Title"] =			"Introduction";
searchDB[schix]["SubTitle"] =		"a brief introduction to the scHelp support development system";
searchDB[schix]["Url"] =			"";
searchDB[schix]["Target"] =			"";
searchDB[schix]["Description"] =	"";
searchDB[schix]["Topic"] =			"<p>\nscHelp is a script based help system. It requires only a modern browser capable of handling javascript. It is portable and help systems can be managed using nothing more than a web browser and a plain text editor. scHelp was built primarily to give developers a cross platform help system that can <strong>also</strong> be maintained cross platform.\n</p>\n\n<br />\n<div style=\"border: solid 1px #999; padding: 8px;\">\n<h3><a href=\"http://www.freewarefiles.com/ScHelp_program_48483.html\" style=\"color: #000; text-decoration: none;\" target=\"_blank\">Download scHelp</a></h3>\n<br />\nYou can download scHelp from <a href=\"http://freewarefiles.com\" target=\"_blank\">Freeware Files</a> by <a href=\"http://www.freewarefiles.com/ScHelp_program_48483.html\" target=\"_blank\">clicking here</a>. It is platform independent and requires only a modern web browser and a plain text editor.\n</div>\n<br />\n\n<p>\n<strong>Getting Started</strong>\n<br />\nTo begin using scHelp, simply make a copy of this file's parent directory and begin editing the contents of its <strong>Data</strong> directory. You can use the <em>admin.htm</em> administration tool to build topic entries and treeview nodes. Refer to this help system for more information on building help systems with scHelp.\n</p>\n\n<p>\n<strong>What scHelp is Good For</strong>\n<br />\nSmaller support systems that will be launched manually or via a hyperlink to the system itself or a given topic. Help systems on computers capable of viewing modern websites.\n</p>\n\n<p>\n<strong>What scHelp is Not Good For</strong>\n<br />\nExtremely complex help systems that require variables in TOC labels, topic text, file links etc. There are many extremely powerful commercial help system development tools out there, for very complicated help systems, commercial applications would probably be a better solution.\n<br />\nHelp systems that need to be integrated into the application itself on a level greater than simply launching specific topics.\n</p>";
searchDB[schix]["Keywords"] =		"";
searchDB[schix]["Status"] =			"home";
	searchRef[searchDB[schix]["ID"]] = searchDB[schix]["Url"]; schix ++;

searchDB[schix] = new Array();
searchDB[schix]["ID"] =				"topStructure";
searchDB[schix]["Title"] =			"scHelp File Structure";
searchDB[schix]["SubTitle"] =		"";
searchDB[schix]["Url"] =			"";
searchDB[schix]["Target"] =			"";
searchDB[schix]["Description"] =	"";
searchDB[schix]["Topic"] =			"<p>\nscHelp is designed to separate functionality from data. Doing this allows the help author to build support systems without touching files containing scHelp functionality.\n</p>\n\n<p>\nIn building support systems, the author need only edit the contents of the <strong>Data</strong> folder - unless he or she is making changes to scHelp's features or functionality.\n</p>\n\n<p>\n<strong>Data Folder Contents</strong>\n<br />\nInside the Data folder are four files and one directory:\n<ol>\n<li>\n<strong>Documents</strong>\nThe Documents directory houses any files that need to be linked to from within the help system.\n</li>\n<li>\n<strong>Search.js</strong>\n<br />\nThis file contains the article definitions. These are used in searching topics as well as searching through the help system. These entries can be generated using the <strong>[root]/admin.htm</strong> tool.\n</li>\n<li>\n<strong>Settings.js</strong>\n<br />\nThis file defines certain aspects of the help system such as the global heading that will be displayed in the help system, as well as the footer and root node caption.\n</li>\n<li>\n<strong>Style.css</strong>\n<br />\nStyle sheet classes can be defined here to override standard scHelp styles. Authors can look up various classes to override within the Main.css file.\n</li>\n<li>\n<strong>Topics.js</strong>\n<br />\nThis file defines the table of contents tree. Each declaration represents a node within the tree. Nodes are sorted in the order they appear within this file. These entries can be generated within the <strong>[root]/admin.htm</strong> tool.\n</li>\n</ol>\n</p>\n\n<hr />\n\n<p>\n<strong>scHelp System Folders</strong>\n<br />\nThese are the folders containing scHelp's functionality and default styles. These should only be modified by authors looking to extend scHelp or change scHelp itself. Most standard help system tasks can be done within the <strong>[root]/Data</strong> folder.\n</p>\n\n<ul>\n    <li>\n    <strong>Css</strong>:\n    <br />\n    The Css folder contains the standard scHelp style classes. These can be overwritten in the <strong>[root]/Data/Main.css</strong>\n    </li>\n    <li>\n    <strong>Images</strong>:\n    <br />\n    The Images folder contains the images that are used by scHelp\n    </li>\n    <li>\n    <strong>Scripts</strong>:\n    <br />\n    The Scripts folder contains all the Javascripts used by scHelp\n    </li>\n    <li>\n    <strong>Tree</strong>:\n    <br />\n    The Tree folder contains the treeview scripts, images and styles\n    </li>\n</ul>\n\n<hr />\n\n<p>\n<strong>scHelp System Files</strong>\n<br />\nThese files are the access points to scHelp and the defined scHelp support system.\n</p>\n\n<ul>\n    <li>\n    <strong>admin.htm</strong>\n    <br />\n    The admin file is the administrator interface for managing the scHelp support system. When help systems are distributed, this file should be removed from the folder that is given to the recipient of the support system\n    </li>\n    <li>\n    <strong>index.htm</strong>\n    <br />\n    The index file is the access point to the support system. To view the defined help, simply open this file in a web browser\n    </li>\n</ul>";
searchDB[schix]["Keywords"] =		"";
	searchRef[searchDB[schix]["ID"]] = searchDB[schix]["Url"]; schix ++;

searchDB[schix] = new Array();
searchDB[schix]["ID"] =				"top_TutorialGettingStarted_SetupProject";
searchDB[schix]["Title"] =			"Step 1";
searchDB[schix]["SubTitle"] =		"Set Up the Project's Properties";
searchDB[schix]["Url"] =			"";
searchDB[schix]["Target"] =			"";
searchDB[schix]["Description"] =	"";
searchDB[schix]["Topic"] =			"<p>\nWhen creating a new support system in scHelp, the first step is to make a copy of the scHelp directory and all of its contents. This new folder will become the new support system project. In the new project folder, open the <strong>[root]/Data/Settings.js</strong>. Here is what the Settings.js file contains:\n</p>\n\n<pre class=\"code\">\nvar MetaTitle = 'scHelp Support Engine';\n\nvar ProjectTitle = '&lt;h1&gt;scHelp&lt;/h1&gt;';\n\nvar ProjectFooter = 'Copyright (c) 2008 -- [author]';\n\nvar RootNodeCaption = 'scHelp Support System';\n</pre>\n\n<p>\nThe <em>MetaTitle</em> property defines the text to appear in the &lt;title&gt;&lt;/title&gt; tag - the browser will show this text in its application caption. The <em>ProjectTitle</em> is the title text or image that appears at the top of the help system. The <em>ProjectFooter</em> defines the footer that will be shown in the help system. The <em>RootNodeCaption</em> property defines the text that will show as the label for the treeview's root node.\n</p>";
searchDB[schix]["Keywords"] =		"";
	searchRef[searchDB[schix]["ID"]] = searchDB[schix]["Url"]; schix ++;

searchDB[schix] = new Array();
searchDB[schix]["ID"] =				"top_TutorialGettingStarted_AdminUI";
searchDB[schix]["Title"] =			"Step 2";
searchDB[schix]["SubTitle"] =		"Using the Admin UI";
searchDB[schix]["Url"] =			"";
searchDB[schix]["Target"] =			"";
searchDB[schix]["Description"] =	"";
searchDB[schix]["Topic"] =			"<p>\nThe <strong>[root]/admin.htm</strong> file can be opened in a web browser. It allows the author build the help system. There are two primary elements in the admin interface:\n</p>\n<ol>\n<li> The treeview contents</li>\n<li> The topic fields</li>\n</ol>\n\n<br />\n\n<p>\n<strong>Treeview</strong>\n<br />\nThe treeview in the admin interface allows the author to select various folders or topics that exist within the <strong>[root]/Data/Topics.js</strong> file. When a topic or folder is selected, its values are populated in the topic fields to the right of the treeview. These can then be modified and the output generated (<em>see below</em>).\n</p>\n\n<br />\n\n<p>\n<strong>Topic Fields</strong>\n<br />\nThe topic fields are where all the work is done. A topic can be created using the <strong>Clear</strong> button, or by simply entering a unique <strong>ID</strong>. When all the fields are populated, the <strong>Generate</strong> button should be used with new topics/folders and the <strong>Update</strong> button for existing ones. Below are descriptions of each of the admin interface's topic fields:\n</p>\n\n<ul>\n<li> <strong>ID</strong>\n<br />\nThis is the unique identifier for the current topic or folder. Each entry must have a unique identifier. If there are items that have the same ID, the first entry will be displayed. If there are duplicates within the treeview the help system may not work properly.\n</li>\n<li> <strong>Parent</strong>\n<br />\nThe parent setting is used by the treeview to determine the current node's hierarchy. If this is set to <em>root</em> it will be immediately visible in the tree, being at the root level. (any node within the treeview can be either a topic entry or a folder - folders are determined by the presence of child nodes which are set by selecting the folder node as the parent)\n</li>\n<li> <strong>Title</strong>\n<br />\nThe title is the text that is displayed at the top of the topic when it is displayed. It is also used by the treeview as the node's caption.\n</li>\n<li> <strong>Sub Title</strong>\n<br />\nThe sub title is shown smaller and below the title when the current topic is viewed.\n</li>\n<li> <strong>Keywords</strong>\n<br />\nKeywords allow the author to define search keywords that may not be found within the topic or its title.\n</li>\n<li> <strong>Topic</strong>\n<br />\nThe topic itself is entered here. Basic html syntax can be used within topics.\n</li>\n<li> <strong>Link</strong>\n<br />\nThe link field is used by topics that are simply links to resources outside of the help system. If there is a specified link, it will override the topic text itself, sending the viewer to the link instead of displaying the topic. To get rid of the link, remove the link specification from the <strong[root]/Data/Search.js</strong> file.\n</li>\n<li> <strong>Target</strong>\n<br />\nThe target field denotes the link's target using any legal html target value.\n</li>\n<li> <strong>Is Homepage</strong>\n<br />\nWhen this is checked the current topic becomes the one that is displayed by default within the help system.\n</li>\n</ul>";
searchDB[schix]["Keywords"] =		"";
	searchRef[searchDB[schix]["ID"]] = searchDB[schix]["Url"]; schix ++;

searchDB[schix] = new Array();
searchDB[schix]["ID"] =				"top_TutorialGettingStarted_GenCode";
searchDB[schix]["Title"] =			"Working With Generated Code";
searchDB[schix]["SubTitle"] =		"";
searchDB[schix]["Url"] =			"";
searchDB[schix]["Target"] =			"";
searchDB[schix]["Description"] =	"";
searchDB[schix]["Topic"] =			"<p>\nThe primary goal of the admin.htm file is to generate two pieces of code:\n</p>\n\n<ol>\n<li> The treeview node snippet</li>\n<li> The topic entry within the topics array</li>\n</ol>\n\n<p>\n<strong>Generating the code</strong>\n<br />\nWhen the topic fields have been populated the code is generated by clicking either the <strong>Generate</strong> or the <strong>Update</strong> button. Topics that aren't already present in the <strong>[root]/Data/Search.js</strong> and the <strong>[root]/Data/Topics.js</strong> file are generated using the <strong>Gnerate</strong> button. Existing items must be generated using the <strong>Update</strong> button. The generated code appears just below these buttons.\n</p>\n\n<p>\n<strong>Using the generated code</strong>\n<br />\nThe first generated code snippet is the Entry - or Topic code. It is to be placed within the <strong>[root]/Data/Search.js</strong> file. If the entry is already in that file, the newly generated code must <strong>replace</strong> the old code.\n</p>\n\n<p>\nThe next snippet is the tree entry code that is to be placed within the <strong>[root]/Data/Topics.js</strong> file. If the node is already in that file, the newly generated code must <strong>replace</strong> the old code.\n</p>";
searchDB[schix]["Keywords"] =		"";
	searchRef[searchDB[schix]["ID"]] = searchDB[schix]["Url"]; schix ++;

searchDB[schix] = new Array();
searchDB[schix]["ID"] =				"topAdvancedTechniques_TopicLinks";
searchDB[schix]["Title"] =			"Linking to Other Topics";
searchDB[schix]["SubTitle"] =		"";
searchDB[schix]["Url"] =			"";
searchDB[schix]["Target"] =			"";
searchDB[schix]["Description"] =	"";
searchDB[schix]["Topic"] =			"<p>\nTopics within the help system can link to one another. To link to a topic, the auther needs to know the target topic's unique identifier. This can be found within the admin.htm file. Simply select the desired topic in the admin ui, its id is shown in the id field. The syntax to link to a topic looks like this:\n</p>\n\n<p>\nTo link to a topic with the id <strong>topIntroduction</strong>:\n</p>\n\n<pre class=\"code\">\n&lt;a href=\"javascript:showTopic('topIntroduction');\"&gt;Click here&lt;/a&gt;\n</pre>\n\nor:\n\n<pre class=\"code\">\n&lt;a href=\"index.htm?tid=topIntroduction\"&gt;Click here&lt;/a&gt;\n</pre>\n\n<p>\nHere is an example (using the second example above, with a blank target), <a href=\"?tid=topIntroduction\" target=\"_blank\">click here</a>.\n</p>\n\n<p>\nOne thing to remember is the viewer may wish to return to the topic that contained the link to the other topic. It may be a good idea in some cases to provide a link back - or use the second example above with a target set to <em>_blank</em> to open the link in a new window.\n</p>";
searchDB[schix]["Keywords"] =		"";
	searchRef[searchDB[schix]["ID"]] = searchDB[schix]["Url"]; schix ++;

searchDB[schix] = new Array();
searchDB[schix]["ID"] =				"topAdvancedTechniques_ExternalLinks";
searchDB[schix]["Title"] =			"Linking to External Addresses";
searchDB[schix]["SubTitle"] =		"";
searchDB[schix]["Url"] =			"";
searchDB[schix]["Target"] =			"";
searchDB[schix]["Description"] =	"";
searchDB[schix]["Topic"] =			"<p>\nThe admin interface includes fields that allow writers to link nodes in the table of contents tree to external resources (other websites, images, etc). If a value is present in the <strong>Link</strong> field, the tree node is designated as an external link. A <strong>Target</strong> value can also be specified in the admin interface.\n</p>";
searchDB[schix]["Keywords"] =		"";
	searchRef[searchDB[schix]["ID"]] = searchDB[schix]["Url"]; schix ++;