RadixWare Programmer Guide/Development Support Means

From RadixWiki
Jump to: navigation, search

Managing Versions

To manage versions, RadixWare Designer applies Subversion. The table below describes the supported operations:

Operation

Toolbar Button

Description

Show Changes

show-changes.png

Shows changes made after the last SVN Commit operation.

Diff

diff.png

Shows differences between two defined revisions.

Update

update.png

Updates to the last definition revision from the SVN repository.

note.jpgWhen executing this command, the files of the Kernel segment are not unloaded from repository. After the new version installation, it is recommended to update the working copy by the external facilities (for example, using the svn up command) before RadixWare Designer startup.

Commit

commit.png

Commits changes made to the SVN repository.

Search History

search-history.png

Opens the change log enabling to search through it.

Revert Modifications

revert.png

Reverts the changes made after the last SVN Commit operation.

All the above-mentioned operations are available in the Team menu item and in the context menu of definitions in RadixWare Designer navigation tree.

Compiling Project

RadixWare Designer enables to compile the whole project as well as separate definitions. The following operation types are supported:

Name

Hot Key

Toolbar Button

Description

Check

Alt+F10

-

Checks the definition (or the whole project) for syntactic and other similar mistakes.

Compile

F9

-

Compiles one definition. Enables to select the environments for which compilation must be executed.

Clean

-

-

Cleans the files created during the last build or compile operation.

Build

F10

build.png

Builds all definitions of the selected module or of the whole project.

Clean and Build

Ctrl+Shift+F10

clean-build.png

Executes the Clean and Build operations in turn.

To start any of the above-mentioned operations, select the Build menu or use the context menu of the selected definition in RadixWare Designer navigation tree.


For the description of dialog box that will open when compiling the definitions, refer to Dialog Box for Compiling Definition.

Dialog Box for Compiling Definition

The dialog box for compiling definition looks as follows:

build-dialog.png

The dialog box contains the following elements:

  • Pre-check options. Set the respective flags to enable the check of the certain project elements prior to the project compilation:
    • Check SQL class syntax. Check for syntax of SQL queries used in the reports and SQL classes. If the flag is set, specify the following parameters:
      • Database connection. The parameters of the DB connection used when checking syntax. To set up the connections list and establish the DB connection using one of the set connections, use the dialog box opened by clicking the Dots.jpg button next to the parameter.
      • Maximum preprocessor combinations. The maximum allowed number of combinations obtained as a result of the SQL query conversion by the preprocessor. The restriction is used only if different text of SQL query is obtained as a result of the SQL constructions conversion with the different values of the input parameters. The default value is 10.
  • Check all overwrite paths. The check for uniqueness of definition description regarding all overwrites, including those in the parallel layers (the overwrites in the parallel layers can result in the ambiguous behaviour that must be eliminated in the upper layers).
  • File:Edit.jpgCheck dependencies of modules
  • Select environment for operation. The group contains the flags. Setting the flags enables compilation for the respective environments:
    • Common
    • Server
    • Client-Common
    • Desktop
    • Web
  • Verify class linkage. If the flag is set, the compiled definition will be verified for the class linkage errors.
  • Multi-thread. If the flag is set, the compilation will be multi-thread.
  • Process UDS. If the flag is set, the definitions of the UDS segment will be also compiled.

Making Release

Prior to release creation, compile the project.

To make the release, specify the set of layers to be included in the release first. For this purpose, check the layers to be included in the release in the Distributable Layers parameter of the branch editor dialog box (refer to Edit Development Branch).

After that, select the Make Release item from the context menu of the project root branch in RadixWare Designer navigation tree. In the displayed dialog box, specify the following parameters:

  • Release Version. The version of the release being made. The version number consists of several digits separated by point. It is created automatically. The version number can be changed if required.
  • Compile ADS Definitions. If the flag is set, the ADS definitions will be compiled before building release. This flag can be unset only if all definitions are compiled.
  • Verify Created Release. If the flag is set, the ready release will be checked for building errors. The check procedure can take much time.
  • Generate documentation. If the flag is set, the radixdoc.zip files will be added to the release modules. These files contain the information used to generate the html description of the product API by the RadixWare Manager tools.

If the Release Version parameter contains the invalid version number, the "Incorrect release number" warning displays in the lower part of the dialog box and the OK button is not available.

make-release.png

Clicking the OK button in the Make Release dialog box starts the release creation. If the used SVN server requires the authentication, the system displays the dialog box for entering the user name and password to the SVN repository. Once the release is built, the system displays the dialog box prompting to confirm the release saving to the SVN repository.