PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
  • Overview
  • The static audit of project
  • Starting the static audit
  • List of errors detected by the static audit
  • The audit of content of application library
  • Overview
  • Interpreting the results of the audit regarding the library content
  • The audit of setup content
  • Overview
  • Interpreting the results of the audit regarding the setup content
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
Overview
The static audit is a feature of the environment used to study the source code of a project in order to detect different problems and to propose improvements.
The static audit includes:
The static audit of project

Starting the static audit

To start the static audit of the project:or
  • Select "Project .. Edition audit .. General report".
The current project will be analyzed.
To start the static audit of the project:or
  • Select "Project .. Edition audit .. Trigger the edition audit".On the "Project" pane, in the "Audit and performances" group, expand "Edition audit" and select "Trigger the edition audit".
Versions 17 and later
The wizard for running the audit starts. Select the type of audit to perform:
  • Audit of entire project. The current project will be analyzed.
  • Audit of some project elements. In the following plane, select the elements to audit. At the end of the wizard, tbe audit will be started on the selected elements.
New in version 17
The wizard for running the audit starts. Select the type of audit to perform:
  • Audit of entire project. The current project will be analyzed.
  • Audit of some project elements. In the following plane, select the elements to audit. At the end of the wizard, tbe audit will be started on the selected elements.
The wizard for running the audit starts. Select the type of audit to perform:
  • Audit of entire project. The current project will be analyzed.
  • Audit of some project elements. In the following plane, select the elements to audit. At the end of the wizard, tbe audit will be started on the selected elements.
To start the static audit of the project:
  • From the "Static audit" Widget found in the Project dashboard, click the gray arrow of Widget. The static audit of project starts.
or
  • On the "Project" pane, in the "Audit and performances" group, expand "Edition audit" and select "Trigger the edition audit". The wizard for running the audit starts. Select the type of audit to perform:
    • Audit of entire project. The current project will be analyzed.
    • Audit of some project elements. In the following plane, select the elements to audit. At the end of the wizard, tbe audit will be started on the selected elements.
The audit window is opened:
Window for static audit of the project
1: In the main area, the audit presents the different problems detected.
2: For each problem, the editor proposes an automatic resolution by clicking the "..." button. Depending on the type of problem, the resolution can consist in opening a configuration window to correct a value or it can be done automatically.
3: Each information notified by the static audit of project can be ignored. To do so, select "Ignore this information" from the popup menu of information table. This button allows you to see the information that was disabled and to re-enable it.
4: The "Refresh" button restarts the project analysis and refresh the display inside the table.
5: The "Print" button is used to print a detailed report about the detected problems.
Note: The window for static audit is a non-modal window and it can remain opened while correcting the errors. It doe not interfere with the use of the development environment.
Versions 17 and later
Automatic startup of the static audit
To remind you of running the static audit, its startup is proposed at regular time intervals (according to the activity and to the modifications performed).
New in version 17
Automatic startup of the static audit
To remind you of running the static audit, its startup is proposed at regular time intervals (according to the activity and to the modifications performed).
Automatic startup of the static audit
To remind you of running the static audit, its startup is proposed at regular time intervals (according to the activity and to the modifications performed).

List of errors detected by the static audit

The static audit of project can detect the following errors:
Compilation problems detected by the static audit
A native access is used by the project but it is not installed on the computer.
Unused code was detected.
Unused variables have been detected.
Project elements are orphan elements (they are never used in the code of the project).
Versions 16 and later
Compilation errors (GUI or code) have been detected.
New in version 16
Compilation errors (GUI or code) have been detected.
Compilation errors (GUI or code) have been detected.
Versions 21 and later
The project is using more than 1000 elements. We recommend that you use the 64-bit version of WINDEV, WEBDEV and WINDEV Mobile.
New in version 21
The project is using more than 1000 elements. We recommend that you use the 64-bit version of WINDEV, WEBDEV and WINDEV Mobile.
The project is using more than 1000 elements. We recommend that you use the 64-bit version of WINDEV, WEBDEV and WINDEV Mobile.
Versions 21 and later
The compilation directory (<ProjectName>.CPL directory) is found on a network disk. The editor performances may be slowed down. We recommend that you use a local directory. This directory can be configured in the project options.
New in version 21
The compilation directory (<ProjectName>.CPL directory) is found on a network disk. The editor performances may be slowed down. We recommend that you use a local directory. This directory can be configured in the project options.
The compilation directory (<ProjectName>.CPL directory) is found on a network disk. The editor performances may be slowed down. We recommend that you use a local directory. This directory can be configured in the project options.
Problems in the analysis detected by the static audit
A native access is used by the project but it is not installed on the computer.
Problems of SCM (Source Code Manager) detected by the static audit
Project elements have been checked out from the SCM since a long time without being checked back in.
Elements are currently checked out in test mode.
Versions 21 and later
Tip: we advise you to disable the archiving of the analysis in SCM.
New in version 21
Tip: we advise you to disable the archiving of the analysis in SCM.
Tip: we advise you to disable the archiving of the analysis in SCM.
Versions 22 and later
Tip: we advise you to convert the analysis to the new format. See New analysis format for more details.
New in version 22
Tip: we advise you to convert the analysis to the new format. See New analysis format for more details.
Tip: we advise you to convert the analysis to the new format. See New analysis format for more details.
Problems common to the window editor, page editor and report editor detected by the static audit
Spelling mistakes have been detected.
Unused groups of controls have been detected.
Some elements do not contain all project languages.
Some elements are not updated from their templates.
Versions 16 and later
Dissociated styles have been detected.
New in version 16
Dissociated styles have been detected.
Dissociated styles have been detected.
Problems of window editor detected by the static audit
Unused styles have been detected.
An internal window is not updated from its template.
Versions 17 and later
A "File path" type input mask is selected, but path entry assistance is not offered.
New in version 17
A "File path" type input mask is selected, but path entry assistance is not offered.
A "File path" type input mask is selected, but path entry assistance is not offered.
Versions 23 and later
Identifying the windows managing (or not) the large fonts
One or more windows include a display mode in large font that differs from the mode used by most application windows.
The management mode of large fonts must be identical for all application windows.
The "..." button allows you to get the list of project windows with their management mode of large fonts. All you have to do is choose the requested option and apply the modifications.
New in version 23
Identifying the windows managing (or not) the large fonts
One or more windows include a display mode in large font that differs from the mode used by most application windows.
The management mode of large fonts must be identical for all application windows.
The "..." button allows you to get the list of project windows with their management mode of large fonts. All you have to do is choose the requested option and apply the modifications.
Identifying the windows managing (or not) the large fonts
One or more windows include a display mode in large font that differs from the mode used by most application windows.
The management mode of large fonts must be identical for all application windows.
The "..." button allows you to get the list of project windows with their management mode of large fonts. All you have to do is choose the requested option and apply the modifications.
Problems of page editor detected by the static audit
The referencing optimizations have not been applied.
Problems of report editor detected by the static audit
A report is based on a Table control that does not exist.
An internal report is using a report that does not exist.
Versions 19 and later
A report is using the "Integrated code" option while this is not required.
New in version 19
A report is using the "Integrated code" option while this is not required.
A report is using the "Integrated code" option while this is not required.
Problems of the query editor detected by the static audit
One or more optimizations on the project queries have been detected.
Versions 19 and later
One or more queries affect data files that do no longer exist in the analysis.
New in version 19
One or more queries affect data files that do no longer exist in the analysis.
One or more queries affect data files that do no longer exist in the analysis.
Problems of the automatic test detected by the static audit
One or more automatic tests have encountered errors.
Problems of code editor detected by the static audit
Unused multilingual messages have been detected.
Too many errors have been disabled.
The percentage of comments in the project is too low.
The average number of lines per process is too high.
Problems of project editor detected by the static audit
One or more configurations generate several targets.
The automatic check-out from SCM is not enabled.
The skin template of the project is not installed on the computer.
The former mechanism of developer groupware is used.
The performance profiler has not been used since a long time. In this case, the static audit proposes to start the performance profiler.
The description file of programming charter was not found.
The project has not been cleaned since a long time. In this case, the static audit proposes to start the project cleaner.
The GUI errors are disabled.
The spelling checker of OpenOffice is not installed on the computer.
The project is huge and it does not use the SCM.
Versions 16 and later
Elements are found in different versions.
New in version 16
Elements are found in different versions.
Elements are found in different versions.
Versions 16 and later
Unused elements are found in the project directory. In this case, the static audit is used to start the search for orphan elements.
New in version 16
Unused elements are found in the project directory. In this case, the static audit is used to start the search for orphan elements.
Unused elements are found in the project directory. In this case, the static audit is used to start the search for orphan elements.
Versions 19 and later
The project is using the developer groupware and not the Source Code Manager.
New in version 19
The project is using the developer groupware and not the Source Code Manager.
The project is using the developer groupware and not the Source Code Manager.
Note: The above-mentioned list is not exhaustive, new errors can be added over time.
The audit of content of application library

Overview

The audit regarding the content of the application library displays the size of the different project elements included in the application library. This information is displayed in a table and in a TreeMap: this allows you to view the importance of the size of elements in relation to the other ones.
To start the audit regarding the content of application library:or
  • Select "Project .. Edition audit .. Analysis of the library (EXE, WDK, WDL)".On the "Project" pane, in the "Audit and performances" group, expand "Edition audit" and select "Analysis of library (EXE, WDK, WDL)".
To start the audit regarding the content of application library:
  • From the "Static audit" widget found in the Project dashboard, click the gray arrow of widget. The static audit starts. Select the "Library analysis" tab.
or
  • On the "Project" pane, in the "Audit and performances" group, expand "Edition audit" and select "Analysis of library (EXE, WDK, WDL)".
Note: the application library (WDL, WDK, EXE...) must have been generated at least once in order to use this audit.

Interpreting the results of the audit regarding the library content

The audit of the library content is used to detect the following problems:
  • Presence of an unwanted file in the application library
  • Graphic visualization of size occupied by each file.
From the audit window, ability to directly display an element selected in its editor. To do so, select the element and click the "View" button.
The audit of setup content
WINDEV

Overview

The audit regarding the content of application setup displays the size of different elements included in the application setup. This information is displayed in a table and in a TreeMap: this allows you to view the importance of the size of elements in relation to the other ones.
To start the audit of application setup:
  • From the Project dashboard, click the button: Static audit and select the "Analysis of setup pack" tab.
or
  • Select "Project .. Edition audit .. Analysis of the setup pack".On the "Project" pane, in the "Audit and performances" group, expand "Edition audit" and select "Analysis of setup pack".
To start the audit of application setup:
  • From the "Static audit" widget found in the Project dashboard, click the gray arrow of widget. The static audit starts. Select the "Analysis of setup pack" tab.
or
  • On the "Project" pane, in the "Audit and performances" group, expand "Edition audit" and select "Analysis of setup pack".
Note: The setup must have been generated at least once in order to use this audit.
WINDEV

Interpreting the results of the audit regarding the setup content

The audit of the setup content is used to detect the following problems:
  • Presence of an unwanted file in the application setup: test files for example.
  • Presence of the same file several times in the setup.
  • Graphic visualization of size occupied by each file.
Minimum required version
  • Version 15
This page is also available for…
Comments
Click [Add] to post a comment