<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">

<HTML>
<HEAD>
	<TITLE>Searchlight [overview]</TITLE>
</HEAD>

<BODY BGCOLOR="#f0f0ff" TEXT="#000000">
<FONT FACE="Trebuchet MS, Verdana, Arial, Helvetica">

<CENTER>
<TABLE WIDTH="80%" BORDER="0">
<TR>
<TD>

<!--HEADING START-->
<FONT COLOR="#00368f">
<B><U><FONT SIZE="+3">S</FONT><FONT SIZE="+2">earchlight </FONT><FONT SIZE="+3">O</FONT><FONT SIZE="+2">verview&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</U>
</FONT></B>
</FONT><P>
<!--HEADING END-->

Searchlight is a compact stand-alone search engine designed for use on any small or medium-sized Web site consisting of multiple pages. By entering keywords or phrases, users can search specified pages on your site (and pages at any other URLs you choose).<P>

Searchlight can search an unlimited number of pages, and present an unlimited number of results. In order to speed up the retrieval and search process, you can also gather the pages to be searched into a single file and ensure that this file is cached for immediate use. Searchlight's search results can, of course, be clicked to open the corresponding web page or file.<P>

Searchlight's compact design makes it ideal for slotting into the narrow left frame of a frameset, allowing the pages found by the search to be opened into the frameset's main frame.  Similarly, Searchlight could be opened in a separate 'satellite' window, to open search results in a new window.

</TD>
</TR>
</TABLE>
</CENTER>
</BODY>
</HTML>
^intro.htm
^Searchlight Intro
^








<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">

<HTML>
<HEAD>
	<TITLE>[applettag]</TITLE>

	<STYLE>
	<!--
	A {color : #ff4040; text-decoration : none; font-weight : bold }
	A.visited { color : #ff4040; text-decoration : none }
	-->
	</STYLE>

</HEAD>

<BODY BGCOLOR="#f0f0ff" TEXT="#000000">
<FONT FACE="Trebuchet MS, Verdana, Arial, Helvetica">

<SCRIPT LANGUAGE="JScript">
<!--
    ua=navigator.userAgent;
    v=navigator.appVersion.substring(0,1);
    if ((ua.lastIndexOf("MSIE")!=-1) && (v!='1') && (v!='2') && (v!='3')) {
        document.body.onmouseover=makeCool;
        document.body.onmouseout=makeNormal;
    }

    function makeCool() {
        src = event.toElement;
        if (src.tagName == "A") {
            src.oldcol = src.style.color;
            src.style.color = "4040FF"; 
        }
    }

    function makeNormal() {
        src=event.fromElement;
        if (src.tagName == "A") {
            src.style.color = src.oldcol;
        }
    }
	
//-->
</SCRIPT>


<CENTER>
<TABLE WIDTH="80%" BORDER="0">
<TR>
<TD>

<!--HEADING START-->
<FONT COLOR="#00368f">
<B><U><FONT SIZE="+3">J</FONT><FONT SIZE="+2">ava </FONT><FONT SIZE="+3">A</FONT><FONT SIZE="+2">pplet</FONT> <FONT SIZE="+3">B</FONT><FONT SIZE="+2">asics&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</U>
</FONT></B>
</FONT><P>
<!--HEADING END-->

<FONT COLOR="#00386f"><B>What Is A Java Applet?</B></FONT><BR>
An applet is one or more .class files which together form a program.  Unlike other types of program, applets are designed to be run from within a web (HTML) page. In this way, they differ from scripts such JavaScript which are text commands typed into the HTML page itself.<P>

<FONT COLOR="#00386f"><B>How Does It Work?</B></FONT><BR>
The <SMALL>&lt;APPLET&gt;</SMALL> tag on a web page points to a .class file in a particular location, in much the same way that an <SMALL>&lt;IMG SRC=&gt;</SMALL> tag points to an image.  The .class file included in this applet tag is downloaded to your own computer, along with any other .class files it needs, when you arrive at a page 'containing' an applet. Once the necessary files have downloaded, your browser runs the program and places it on the web page (using the dimensions also included in the applet tag) in much the same way that an image is displayed.
<P>


<A NAME="tag"><FONT COLOR="#00386f"><B>The Applet Tag</B></FONT></A><BR>
The basic applet tag required to include an applet in your page looks like this:
<BLOCKQUOTE><B>&lt;APPLET CODE=&quot;SomeApplet.class&quot; WIDTH=100 HEIGHT=100&gt;<BR>&lt;/APPLET&gt;</B></BLOCKQUOTE>
This is the most basic tag possible: the three attributes <small>CODE=</small>, <small>WIDTH=</small> and <small>HEIGHT=</small> are all required, along with the closing <small>&lt;/APPLET&gt;</small> tag.<P>

<BLOCKQUOTE>
<LI><small><B>CODE=</B></small> specifies the name of the class file that the browser should fetch. Some applets consist of several class files, but only one will ever be included in the tag, and the applet's documentation will tell you <I>which</I> one. (Including the <B>.class</B> extension in this attribute is optional - your browser already knows that it's looking for a file with the .class extension, so doesn't really need telling again.)<P>

<LI><small><B>WIDTH=</B></small> and <small><B>HEIGHT=</B></small> specify the dimensions of the applet - the amount of real estate on a page that the browser should assign to the applet.  With some applets, the dimensions will be of no more than aesthetic concern and you'll choose the size that looks best.  With others, the dimensions might have to match the dimensions of an image used by the applet, or you might need to increase the size in order to display more entries in a menu applet.  All <B>Cool Focus</B> applet documentation explains how to best judge your applet dimensions.
</BLOCKQUOTE>

<A NAME="params"><FONT COLOR="#00386f"><B>Applet Parameters</B></FONT></A><BR>
In some cases the simple tag above is all that's needed for an applet to run.
<P>
However, some kindly applet developers include a variety of settings that the page designer can adjust to suit his own needs, by defining <I>parameters</I>.  At <B>Cool Focus</B> , we specialize in making our applets as user-editable as is humanly possible.  Every parameter has its own <I>name</I>, and offers a choice of two or more settings, or <I>values</I>.  For example, a parameter that lets you select a background color for an applet might be called BgColor. To set your chosen color, you'd include the following parameter before the final <small>&lt;/APPLET&gt;</small> tag, altering the entry between the double-quotes according to the color you want to use:


<BLOCKQUOTE><B>
&lt;APPLET CODE=&quot;SomeApplet.class&quot; WIDTH=100 HEIGHT=100&gt;<BR>
&lt;param name=BgColor value=&quot;FF0000&quot;&gt;<BR>
&lt;/APPLET&gt;
</B></BLOCKQUOTE>


<LI>Note that the <I>value</I> you give for a parameter <I>must</I> be enclosed in double-quotes.<P>

<LI>Note also that the <I>name</I> of the parameter is case-sensitive.<P>

<LI>PARAM tags can be placed in any order between your main &lt;APPLET&gt;...&lt;/APPLET&gt; tags. The applet is simply told to search through these PARAM tags for a parameter with a particular name, and it will do the job just as efficiently however you choose to organize them.<P>

Many of the possible parameters you can alter will also have a <I>default</I> setting.  If you want to use the default setting for one of the parameters, you can leave it out of your HTML code.  For example, if the default background color for the applet example above were FF0000 (red), the inclusion of the parameter we've just entered is making no difference to how the applet will look on the page.<P>

<A NAME="codebase"><FONT COLOR="#00386f"><B>The CodeBase Attribute</B></FONT></A><BR>
Also like an image, if you want to use an applet on your page you must make sure that the .class file referred to in the tag is available for download from the web server, and <I>that it can be found</I>. If the applet consists of several .class files, all must be kept together.  The image tag uses a single attribute, <small>SRC=</small>, to specify both the name and the location of an image file (<small>SRC=&quot;docs/images/myimage.gif&quot;</small>, or just <small>SRC=&quot;image.gif&quot;</small>). For an applet, the name and location of the class file(s) are split between two attributes, <small>CODE=</small> and <small>CODEBASE=</small>, respectively.<P>

In the example tag given above, only the <small>CODE=</small> attribute is used. The browser therefore expects all necessary .class files to be in the same directory as the current HTML page.  If the class files are in a different directory, such as a subdirectory called 'classes', you add the attribute <small><B>CODEBASE=&quot;classes&quot;</B></small>. If they're in the parent directory, use <small><B>CODEBASE=&quot;../&quot;</B></small>.  You can also specify an absolute location, such as <small><B>CODEBASE=&quot;http://www.someserver.com/somedirectory/classes&quot;</B></small>.<P>

<FONT COLOR="#00386f"><B>Other Optional Attributes</B></FONT><BR>
Similar again to the <small>IMG</SMALL> tag, the <SMALL>APPLET</SMALL> tag can take optional parameters to define alignment and spacing.<P>

<BLOCKQUOTE>
<LI><small><B>ALIGN=</B></small> allows the usual values of <small>LEFT | RIGHT | TOP | MIDDLE | BOTTOM | ABSMIDDLE | ABSBOTTOM | TEXTTOP | BASELINE</small>. Right or Left alignment allows you to place text or an image beside an applet. Top or bottom are useful when placing multiple applets in a row (perhaps to create a menu-like strip of buttons), ensuring that the top of the applets are always aligned, regardless of how the applets differ in height.<P>

<LI><small><B>HSPACE=</B></small> and <small><B>VSPACE=</B></small> create additional blank space around an applet either horizontally (Hspace) or vertically (Vspace). <P>
</BLOCKQUOTE>

<A NAME="fonts"><FONT COLOR="#00386f"><B>Java Fonts</B></FONT></A><BR>
Because Java is intended to be a cross-platform language, it can't support all the various font technologies in use on all computers (such as the TrueType fonts used by Windows).  Instead, Java supports just 5 fonts which will be available on any computer that has a Java-enabled browser or the Java Development Kit installed: these are Dialog, Helvetica, Courier, TimesRoman, and the less useful Symbol.  Although applets will still display text if you enter something different into their Font parameters, they will do so by using the default font. In most <B>Cool Focus</B> applets, the default font is either Dialog or Helvetica.<P>


<FONT COLOR="#00386f"><B>More Information</B></FONT><BR>
For more information about Java, visit Sun Microsystems' Java site at <A HREF="http://java.sun.com">java.sun.com</A>.


<P>
<FONT SIZE="1"> Java is a registered trademark of Sun Microsystems, Inc.</FONT>

</TD>
</TR>
</TABLE>
</CENTER>
</BODY>
</HTML>
^javabasics.htm
^Java Applet Basics
^








<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">

<HTML>
<HEAD>
	<TITLE>Searchlight [getting started]</TITLE>

	<STYLE>
	<!--
	A {color : #ff4040; text-decoration : none; font-weight : bold }
	A.visited { color : #ff4040; text-decoration : none }
	-->
	</STYLE>
</HEAD>

<BODY BGCOLOR="#f0f0ff" TEXT="#000000" LINK="#ff4040" VLINK="#ff4040" ALINK="#4040c0">
<FONT FACE="Trebuchet MS, Verdana, Arial, Helvetica" SIZE="2">
<BASE TARGET="_self">

<SCRIPT LANGUAGE="JScript">
<!--
    ua=navigator.userAgent;
    v=navigator.appVersion.substring(0,1);
    if ((ua.lastIndexOf("MSIE")!=-1) && (v!='1') && (v!='2') && (v!='3')) {
        document.body.onmouseover=makeCool;
        document.body.onmouseout=makeNormal;
    }

    function makeCool() {
        src = event.toElement;
        if (src.tagName == "A") {
            src.oldcol = src.style.color;
            src.style.color = "4040FF"; 
        }
    }

    function makeNormal() {
        src=event.fromElement;
        if (src.tagName == "A") {
            src.style.color = src.oldcol;
        }
    }
	
//-->
</SCRIPT>

<CENTER>
<TABLE WIDTH="80%" BORDER="0">
<TR>
<TD>

<!--HEADING START-->
<FONT COLOR="#00368f">
<B><U><FONT SIZE="+3">G</FONT><FONT SIZE="+2">etting </FONT><FONT SIZE="+3">S</FONT><FONT SIZE="+2">tarted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</U>
</FONT></B>
</FONT><P>
<!--HEADING END-->

<FONT SIZE="-1">
<OL>
<LI>Place the two class files (rySearchlight.class and rySearch.class) in the directory containing the HTML document into which you want to insert the applet (or into a different directory, and add the correct <A HREF="javabasics.htm#codebase">CODEBASE=</A> attribute to the applet tag given below).<P>

<LI>Check that you've made these <A HREF="reg.htm#runreg">additional changes</A> to your setup as required for all registered applets.<P>

<LI>Add the following applet tag to your HTML document in the position you want Searchlight to appear:
<P>
<BLOCKQUOTE>
&lt;APPLET CODE=&quot;rySearchlight.class&quot; WIDTH=200 HEIGHT=250&gt;<P>
&lt;param name=Copyright value=&quot;Searchlight (c) 1997 Cool Focus [www.coolfocus.com]&quot;&gt;<BR>
&lt;param name=ShowShortURLS value=&quot;yes&quot;&gt;<BR>
&lt;param name=Target value=&quot;_top&quot;&gt;<P>

<B>&lt;!-- Option #1: specify a single file containing the text of the pages to be searched --&gt;</B><BR>
&lt;param name=SingleSearch value=&quot;master.htm&quot;&gt;<BR>
&lt;param name=SSMaxLines value=&quot;2000&quot;&gt;<BR>
&lt;param name=SSMaxURLs value=&quot;100&quot;&gt;<P>

<B>&lt;!-- Option #2: specify each document to be searched individually --&gt;</B><BR>
&lt;param name=URL1 value=&quot;intro.htm&quot;&gt;<BR>
&lt;param name=Name1 value=&quot;Searchlight Overview&quot;&gt;<BR>
&lt;param name=URL2 value=&quot;javabasics.htm&quot;&gt;<BR>
&lt;param name=Name2 value=&quot;Java Applet Basics&quot;&gt;<BR>
&lt;param name=URL3 value=&quot;getstarted.htm&quot;&gt;<BR>
&lt;param name=Name3 value=&quot;Getting Started&quot;&gt;<BR>
&lt;param name=URL4 value=&quot;params.htm&quot;&gt;<BR>
&lt;param name=Name4 value=&quot;Searchlight Parameters&quot;&gt;<BR>
&lt;param name=URL5 value=&quot;trouble.htm&quot;&gt;<BR>
&lt;param name=Name5 value=&quot;Troubleshooting&quot;&gt;<BR>
&lt;param name=URL6 value=&quot;feedback.htm&quot;&gt;<BR>
&lt;param name=Name6 value=&quot;Contacting Cool Focus&quot;&gt;<P>
&lt;/APPLET&gt;
</BLOCKQUOTE><P>

<LI>Save the document and open it in your browser.  Provided the class files are located where you have specified in the tag and parameter, Searchlight will start. Initially, Searchlight will appear 'grayed-out' while it reads the documents at the URLs specified in the URL parameters - during this time, a 'percentage complete' figure will appear in the browser status bar.<P>

<LI>Searchlight requires a space of fixed size on the page: width=200, height=250. If you reduce these figures, parts of the applet will not be visible.<P>

<LI>Change the URL and Name parameters given in this example to those you want to use (adding as many as you need), and adjust the first two parameters as necessary. Details of all parameters are given in <A HREF="paramindex.htm" TARGET="_top">The Parameters Explained</A>.<P>

<I>Note that the more URL parameters you use (and the more text each referenced file contains) the longer Searchlight will take to carry out its initial processing. Using Option #1 rather than Option #2 cuts this time dramatically, with the added bonus that the single file can be <A HREF="tip.htm">cached in advance</A> of being needed, although this requires a little more space on your web server.</I><P>




</OL>
</TD>
</TR>
</TABLE>
</CENTER>
</BODY>
</HTML>
^getstarted.htm
^Getting Started
^








<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">

<HTML>
<HEAD>
	<TITLE>[Java Tips]</TITLE>
	<STYLE>
	<!--
	A {color : #0080C0; text-decoration : none; font-weight : bold }
	A:visited { color : #0080C0; text-decoration : none }
	A:hover { color : #00CCFF; text-decoration : none }
	-->
	</STYLE>
</HEAD>
<BODY BGCOLOR="#F0F0FF" TEXT="#000000" LINK="#0080C0" VLINK="#0080C0" ALINK="#00CCFF">
<FONT FACE="Trebuchet MS, Verdana, Arial, Helvetica">

<CENTER>
<TABLE WIDTH="90%" BORDER="0">
<TR>
<TD>

<!--HEADING START-->
<FONT COLOR="#0080c0">
<B><U><FONT SIZE="+3">J</FONT><FONT SIZE="+2">ava </FONT><FONT SIZE="+3">A</FONT><FONT SIZE="+2">pplet</FONT> <FONT SIZE="+3">T</FONT><FONT SIZE="+2">ips&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</U>
</FONT></B>
</FONT><P>
<!--HEADING END-->
<FONT FACE="Trebuchet MS, Verdana, Arial, Helvetica" SIZE="2">

Although Java is supposed to be a cross-platform language, there are now so many implementations of it that it's hard to be sure what an applet will look like in a particular version of a particular browser without taking a look. This page gathers together a few tips, browser inconsistencies and irritations that you may want to consider when adding applets to your pages.<P>

<FONT COLOR="#0080C0"><B>Including An HTML Alternative</B></FONT><BR>
A Java menu system might make your site un-navigable to users with old browsers that don't support Java. However, you can include as much standard HTML code as you like before the applet's closing &lt;/APPLET&gt; tag.  If you place HTML links here to all the pages on your menu, browsers that <I>do</I> support Java will ignore them; those that don't will ignore the &lt;APPLET&gt; and &lt;PARAM&gt; tags and just display that HTML.<P>

<FONT COLOR="#0080C0"><B>Using The Dialog Font</B></FONT><BR>
Many applets place text centrally within an area. Buttons and menus are obvious examples, such as our <B>TextButton</B>.  When the applet is run, a browser's own Java Virtual Machine determines the horizontal position of the text by measuring the width of the area available and the length of the text string.  Some browsers (particularly Netscape Navigator 4.<I>x</I>) cannot accurately gauge the width of a string when it uses Java's Dialog font, imagining that it's longer than it actually is, and placing it left of center.  You may wish to avoid using Dialog for centered text, and stick to Helvetica, Courier or TimesRoman. <P>

<FONT COLOR="#0080C0"><B>Using Any Font At All</B></FONT><BR>
Many menu applets place lines of text in vertical columns.  Examples are drop-down menus such as our <B>ClassicMenu</B>.  In this type of applet, the vertical position of each line is determined as a factor of font-height, which allows Web authors to use a larger font without the lines of text beginning to overlap.  All Netscape Navigator versions allow vastly more vertical space between each line of text than any other Java platform.  Thus a menu containing 6 items in this browser will be longer than the same menu in Internet Explorer or Sun's own HotJava and Appletviewer.  Because the same measurements are used to calculate the size of the menu needed to display these lines of text, Navigator will still create a long enough menu, but in some cases your applet height may not be sufficient for the lower entries to be visible.
 
When setting up any applet that creates columns of text, always check the longest column in Netscape before publishing the page to ensure that applet-height is sufficient to display the longest columns.  In Internet Explorer and other browsers this space at the bottom of the applet will be 'dead-space', but will at least be filled with your chosen background color (usually a parameter named BgColor in Cool Focus applets).<P>


<FONT COLOR="#0080C0"><B>Refresh/Reload</B></FONT><BR>
In some Netscape versions, the Reload command does not reread applet parameters, and does not repaint the applet correctly if you changed its dimensions before Reloading.  Always use the 'power-reload': hold Shift while clicking the reload button.  In Internet Explorer v4.0 and higher, the Refresh command does do its job properly, but a similar power-refresh (Ctrl+Refresh) will re-read the applet class file and all related files (such as images or text files used by the applet).<P>


<FONT COLOR="#0080C0"><B>Security: Applets Calling External Files</B></FONT><BR>
'External files' can be thought of as anything but a Java .class file and the current HTML document.  Many applets call external files such as sound-effects and images, and others (such as our own <B>NewsAgent</B> and <B>Searchlight</B>) read their parameters and other information from text-files.  Clearly Java has to have some security measures to prevent a rogue applet on a Web site reading information from a visitor's own computer, but this type of security is largely unnecessary when the applet is reading files from its own host (as it is when you're setting up and testing pages on your home system).<P>

Although Internet Explorer 3.02 suffered from security paranoia, Microsoft recognized how ludicrous and irritating this was and released a patch: IE4 and the patched 3.02 can read local files provided that they are in the same directory as the current HTML document or in a subdirectory.  
Netscape Navigator will sometimes (though, typically, not always) refuse to run an applet on your local system if it calls external files, displaying a SecurityException or NullPointerException message in its statusbar and Java Console window.<P>

If an applet simply calls non-vital files such as sound effects, turn off the Sound option while testing in this browser. If the requirement to load external files is fundamental to the applet's use, you'll need to upload your pages to the Web server and test them in this browser via HTTP. Alternatively, you can use our free utility, ComTest, written specifically to get around this irritation.  ComTest is available for download from <A HREF="http://www.coolfocus.com" TARGET="_top">Cool Focus</A>.

<FONT COLOR="#f0f0ff"><BR><BR><BR>.</FONT>
</TD>
</TR>
</TABLE>
</CENTER>
</BODY>
</HTML>
^navigator.htm
^Java & Navigator 4.x
^








<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">

<HTML>
<HEAD>
	<TITLE>Searchlight [useful notes]</TITLE>

	<STYLE>
	<!--
	A {color : #ff4040; text-decoration : none; font-weight : bold }
	A.visited { color : #ff4040; text-decoration : none }
	-->
	</STYLE>
</HEAD>

<BODY BGCOLOR="#f0f0ff" TEXT="#000000" LINK="#ff4040" VLINK="#ff4040" ALINK="#4040c0">
<FONT FACE="Trebuchet MS, Verdana, Arial, Helvetica" SIZE="2">
<BASE TARGET="_self">

<SCRIPT LANGUAGE="JScript">
<!--
    ua=navigator.userAgent;
    v=navigator.appVersion.substring(0,1);
    if ((ua.lastIndexOf("MSIE")!=-1) && (v!='1') && (v!='2') && (v!='3')) {
        document.body.onmouseover=makeCool;
        document.body.onmouseout=makeNormal;
    }

    function makeCool() {
        src = event.toElement;
        if (src.tagName == "A") {
            src.oldcol = src.style.color;
            src.style.color = "4040FF"; 
        }
    }

    function makeNormal() {
        src=event.fromElement;
        if (src.tagName == "A") {
            src.style.color = src.oldcol;
        }
    }
	
//-->
</SCRIPT>

<CENTER>
<TABLE WIDTH="80%" BORDER="0">
<TR>
<TD>

<!--HEADING START-->
<FONT COLOR="#00368f">
<B><U><FONT SIZE="+3">U</FONT><FONT SIZE="+2">seful </FONT><FONT SIZE="+3">N</FONT><FONT SIZE="+2">otes&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</U>
</FONT></B>
</FONT><P>
<!--HEADING END-->

<FONT SIZE="-1">

<UL>
<LI>Unlike most other Cool Focus applets, Searchlight has few user-editable parameters. Because Searchlight is a utility, options we usually regard as essential for web designers (applet size, fonts, colors, behavior) have been left out to avoid unnecessary 'bloat'.<P>

<LI>Use the Up/Down buttons on the Search Results page to scroll backwards and fowards through the results. These become active only when there are more than 8 matches, and either arrow will become inactive when there are no more results to be displayed in the corresponding direction.<P>

<LI>Searchlight returns not only the text of HTML documents, but plain text (.txt) documents, file and directory names,  paths, hosts and URLs, and HTML tags.<P>

<LI>After setting up your URL/Name parameters (or the equivalent markers in <A HREF="params.htm#singlesearch">SingleSearch</A> mode), you might wish to check that the displayed Names or URLs fit neatly within Searchlight's borders.  Run a search for a word that occurs in every referenced URL (such as &quot;html&quot; if your entries are all web pages) so that every URL will be a match.<P>

<LI>Some Netscape Navigator / Communicator users will find that Navigator either refuses to initialize or insists that no matches are found when running Searchlight <I>locally</I> with links to local files. This is a result of Navigator's security paranoia which prevents it loading and reading local files. Users of any Cool Focus applet can use our free utility, <A HREF="ComTest.htm">ComTest</A>, available from the Free Stuff section at <A HREF="http://www.coolfocus.com" TARGET="_top">Cool Focus</A>.

</UL>




</BODY>
</HTML>
^notes.htm
^Useful Notes
^




