Setting User Preferences
Walk through the screen shots to see how easily user preferences are set. Screen Shot Index Tool Preferences:
Parsing Preferences: Class Parsing Parsing Threshold Parsing Control
Search Scope Preferences: Main Screen Package Selection
User Preferences are available from the Options menu. 
Tool Preferences
Tool Preferences has four sections. The first section, Tool Execution Dialog, controls what happens when you run a tool such as the compiler or applet viewer. You choose whether to see a display of the command line before it is executed (Show Dialog), whether to display the DOS window when the tools are run (Run Tools Hidden), and whether to prepend the current tool path onto the command line (allows tools to run without being in your PATH).
 |
The second section, Applet Viewer Execution Dialog, lets you choose how to run the applet viewer to view applets you are writing. You choose whether to see the command line before it is executed (Show Dialog) and select an HTML source to run in the applet viewer. The third section, Packages/Projects display, lets you choose what is displayed in the top left pane of the browser. You can Show Project names or Show Class Path directory entries. Show Projects enables you to also show the JDK in use. This is handy if you switch JDK's and want to know which version is running. The fourth section lets you color source code according to Java syntax. You must
also choose whether a prompt appears before your source code is saved. If checked, you must confirm saving any source code. If not checked, the source code will be saved automatically.
|
Source Code Color and Font Manager (return to index)
Push the Set Java Colors and Fonts button to view the Source Code Color and Font dialog. It is off by default because it takes longer to display files when it is on. Source code coloring lets you quickly read Java source code by assigning different colors to Java keywords, comments, string constants, and class names. The checkbox at the top enables/disables source code coloring.
 |
Parsing Preferences Overview (return to index)
Parsing is the process of building an index of .class files that you want to view or search. During parsing, view the status pane at the bottom of the browser for
feedback. You can interrupt parsing by hitting the Escape key. The more classes you parse means more memory will be used during a search and searches will take longer. You decide the scope for any search by choosing what is parsed. Three choices give you complete control over class and package level parsing. 1. Parse class references when a class is selected means that only the selected
class and the classes referenced by it are parsed. If you select a package in the Project/Packages pane, the entire package is parsed. 2. Parse class references when a class is parsed means that when a class is parsed, all classes referenced in that class are parsed and so on and so on until all referenced classes are parsed. 3. Do not parse class references. Only the class selected is parsed. This is the
default setting. No classes referenced are parsed--and they are not included in searches unless you cause them to be parsed.
 |
Parsing Threshold (return to index)
Specify how many classes to parse before being warned that your parsed class list is getting large. The warning explains why you should control the number of classes parsed in your Grinder environment. Also, specify a file name that contains the list of package names to be parsed when Grinder is parsed.
 |
Parsing Control (return to index)
You can selectively control the classes parsed by pushing the Package Parser button. This will display the Package Parsing dialog shown below. You add or remove classes to be parsed.
 |
Search Scope Preferences
(return to index)
Main Screen You control which classes are looked at when you search for senders, implementors, or references. The default scope is all parsed packages.
 |
Push the Parse Packages button to return to the Grinder Package Parsing (see Parsing Control) dialog window and parse additional packages to include in your
search. Or, if you only want to search specific packages, push the Select Packages button. The check box at the bottom sets whether a new window is created for each search, or whether new results are displayed in place of current results in the same window.
You specify the packages in your search. Select an individual package or all related packages. Add or remove directories
from the CLASSPATH to control what packages are visible in your Java environment. If the package selected is parsed, it is included in the search scope (bottom window). Otherwise, it is placed in the middle window and you to decide whether to parse it. Remember, only parsed packages can be included in a search scope. Only the packages displayed in the bottom pane will be searched after you close the dialog.
 |
 |  |  |  |
 |  |  |  |  |  |