** Double-click on image to enlarge,
click once to minimize again.
Files
List browser
Shows list of files
where project HTML report pages going to be (re)generated.
Columns: File name, Full Path, Status (updated,
new, recompiled, _blank_).
Report
Main Page File Name (below the browser)
Project
report main page file name.
Options
Open the project
report generator Options window (see below).
Generate
Start the project
report generating process.
Open
Open the report main
page in the default Windows HTML browser.
Options
Opens the Project
Source Code Scan Options window. See description
below.
** Double-click on image to enlarge,
click once to minimize again.
Database
structure and Tables reports
(re)generates the
project database analysis and structure HTML reports
for all tables, whole database and database schema
changes history page. Automatically keeps historical
information for all database schema changes.
Module
Changes History
(re)generates
the changes history for all project modules. Such
changes as adding modules to the project and removing
from the project are also supported.
You can turn this option off if you are already
using a project source-code management tool such
as VSS or Roundtable for example.
Project
Performance report
(re)generates the
project Performance report page
Project
Integrity reports
(re)generates the
project Integrity report page
Calls
Tree
(re)generates the
project Calls tree for every parent module of the
application (a module, which has no any external
calls)
Regenerate
all Module Structure reports
(re)generates reports
for all project modules, even for the not changed
ones.
Folders
Tree navigation
Explorer-like navigation
folders tree. Builds it on the project files list
page.
Code
Analysis (user-defined) report
(re)generates code
analysis project report and all modules code analysis
pages. An open-source external 4GL procedure, shown
in the read-only fill-in below, is the procedure,
responsible for all user-defined reporting stuff.
Generate
Prolint reports
(re)generates Prolint
module report pages. All Prolint parsing and analysis
results are stored in a separate project file -
Prolint.tab.
** Double-click on image to enlarge,
click once to minimize again.
Skip
reports without data
skips the module
reports sections where there is no any parsing/analysis
information available.
Used
in modules
builds
a list of caller modules.
Module
calls tree
builds the module
calls tree including external and internal procedures
calls, functions calls and includes usage.
Input/Output
parameters
builds a list of
the module INPUT/OUTPUT parameters.
Shared
resources
builds a list of shared resources defined on
the module, i.e.: shared-variables, shared-frames,
shared-worktables.
Internal
functions defined
builds a list of
all module functions defined.
Internal
procedures defined
builds a list of
all module internal procedures defined.
External
procedures used
builds a list of
all module external procedures called from the module.
Internal
functions used
builds
a list of all module functions called from the module.
Internal
procedures used
builds a list of
all module internal procedures called from the module.
Includes
used
builds a list of
all include files used in the module.
OS
Programs Used
builds a list of
all module external non 4GL modules calls.
DB
Tables usage
builds a database
tables usage statistics for the following parameters:
ACCESS, REFERENCE, SORT-ACCESS and UPDATE.
DB
Indexes usage
builds a list of
the database indexes used by the module in queries,
FIND and FOR statements.
No
Tables Lock definition
builds a list including
all not-indexed searches (WHOLE-INDEX) and index
names that really used.
Internal
Procedures specification
builds a list of
internal procedures, its input/output parameters
and the procedure description. As a description
used all text enclosed into /* ... */ and written
after the PROCEDURE <procedure-name> definition.
Can be used as an automatic source-code documenting
procedure.