|
|
Getting StartedThis section discusses the following topics:
Installing the Globalyzer ClientFor installation instructions, click here. Also, prior to starting Globalyzer you must have already created at least one Rule Set. If your rules repository is empty, Globalyzer will not start. For instructions on creating and managing Rule Sets, click here.Starting the Globalyzer Client
After you have been successfully logged into the server, the main Globalyzer window appears. Globalyzer Window OverviewWhen you start Globalyzer, the application window appears, as shown below. The main parts of the interface are labeled, and briefly described below.
The Toolbar has buttons linked to the most common actions used in Globalyzer. All these can also be found in the Menubar. The Source Tree pane displays the current Base Source Directory along with its subdirectories and files. Note that only files that match the File Extensions list for the currently-selected Scan will be displayed. The Scan Results pane contains all the scan results. By using the dropdowns in this pane you can navigate between different scans and/or result types, and apply and add filters to the scan results. When you double-click on a row in the Scan Results table, Globalyzer will open the associated source file in the Source Files pane and highlight the issue. The Quick Summary pane displays a summary from the most recent scan. Each Results type (Embedded Strings, Unsafe Methods, General Patterns and Static File References) has its own section in the Summary. The Status pane will display various messages. For example, during a scan, the names of individual files scanned will be displayed. Using GlobalyzerBefore you scan code, you must create one or more Rule Sets, or obtain access to Rule Sets created by someone else for your project. After you have a Rule Set to use, you can configure the Globalyzer Client to use the Rule Set and set up other properties Globalyzer needs to perform a scan. For instance, you need to tell Globalyzer where to find source files to scan, where to put reports, and so on. These procedures are described in Configuring Rule Sets and Scanning Source Code. If you intend to use Globalyzer to fix code, then you also need to configure several project properties. For instance, you need to specify a method to replace embedded text that has been externalized. These properties and procedures are described in Fixing Source Code. Exiting GlobalyzerTo exit Globalyzer, select File=>Exit from the Menubar. Globalyzer will display a warning if there are unsaved Source File changes.
Only files that were modified since last being saved will show up in the list. To select or deselect a single file, click the checkbox next to the filename. All -- Selects all of the listed files. None -- Deselects all of the listed files. OK -- Saves the selected files and then exits Globalyzer. Cancel -- Closes the dialog box without saving any files: Exit is aborted.
|