PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

  • Overview
  • Modifying a component
  • Adding or deleting an element into/from a component
  • Modifying a component element
  • Regenerating the modified component: managing the compatibility between the different versions
  • The different types of compatibility
  • Definition
  • Backward compatibility
  • Forward compatibility
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
An external component created and generated by WINDEV, WEBDEV or WINDEV Mobile can be modified at any time. This modification can correspond to:
  • the addition of elements into the component,
  • the deletion of elements from the component,
  • the modification of rights on the component elements,
  • the modification of one of the component elements.
In any case, after this modification, the component must be regenerated in order to take the modifications into account.
This help page presents:
Note: The reports included in a component cannot be modified by Reports & Queries.
Modifying a component

Adding or deleting an element into/from a component

To add or delete an element into/from a component:
  1. Open the component project ("File .. Open a project").Open the component project: on the "Home" pane, in the "General" group, expand "Open" and select "Open a project".
  2. Select "Workshop .. External component .. List of components generated from this project".On the "Project" pane, in the "Project" group, expand "List of elements" and select "List of generated components".
  3. The description window of components is displayed. This window allows you to perform the following modifications:
    • Modify a component ([Modify] button).
      The wizard for component modification starts with the options of the selected component. The different options of the component can be modified (add elements, modify the visibility of elements, ...).
    • Find out and modify the elements included in the component.
    • Make visible (or not) the elements included in the component.
    • Modify the access rights of the component on the client project.
  4. Regenerate the component.

Modifying a component element

To modify a component element:
  1. Open the component project ("File .. Open a project").Open the component project: on the "Home" pane, in the "General" group, expand "Open" and select "Open a project".
  2. Open the requested element.
  3. Perform the necessary modifications.
  4. Save these modifications ( ).
  5. Regenerate the component ("Workshop .. External component .. Generate a component").Regenerate the component: click the generation icon among the quick access buttons:
Regenerating the modified component: managing the compatibility between the different versions
Whenever a modification is performed, the component must be regenerated in order to take the modifications into account (change the interface of a window for example).
To regenerate the modified component:
  1. Start generating the component:
    • via "Workshop .. External component .. Generate a component", click the generation icon among the quick access buttons.
    • via the description window of components ([Generate]).
  2. The wizard for generating the component starts.
  3. In the "Compatibility of component in deployment" screen, a check is performed on the modifications made:
    • If the modifications make the component incompatible with the earlier versions, the following screen is displayed:
      Synchronize the version numbers ( button).
      Go to the next step to continue generating the component.
    • If the detected modifications do not make the component incompatible with the earlier versions, no specific action is required. Click "Next" to continue generating the component.
The different types of compatibility

Definition

The management of compatibility is linked to the versions of a component. Indeed, if modifications have been made to the component, the applications that use the component in deployment may encounter runtime problems if they are not synchronized with this component.
The management of compatibility is an important step in the modification of a WINDEV component. Two types of compatibility are available:
  • The backward compatibility: the component version (.WDK file) used to compile the applications that use this component must always be greater than or equal to the version currently used in deployment.
    This compatibility is automatically managed by WINDEV. If the version of the component installed with the application is less than the version used by the application, the application will not operate.
  • The forward compatibility: using a new version of a component with the projects compiled with an earlier version can be forbidden. Therefore, the projects must be recompiled in order to use the new version of the component.

Backward compatibility

The version number of components is automatically checked to make sure that the component version used in the deployed application is greater than or equal to the one used when developing the application.
Example:
The project was compiled with the version 1.00C of a component.
The version 1.00C is the reference version. Which means that the applications that use this component will operate only if the component version is greater than or equal to the reference version.
The following cases can occur:
  • First case: The applications deployed on the end-user computers use a version of the component (.WDK file) less than version 1.00C. An error will occur when loading these applications.
  • Second case: The applications deployed on the end-user computers will operate if they use the expected component version.
  • Third case: The applications deployed on the end-user computer will operate if the version of the component is greater than the expected one (only if the new version is used to fix bugs).

Forward compatibility

The incompatibilities between two versions of the same component are automatically detected when generating this component. If differences are found, you have the ability to modify the "number of the last compatible version". This number is the version number from which the applications that use the component will be allowed to operate.
Example:
A project that used the version 1.00C of the component has not been recompiled with the new version 1.00E of this component.
Version 1.00E of the component is installed on the deployment computers.
The following cases can occur:
  • First case: the component was modified to fix bugs only. When generating the component, the "number of the last compatible version" has not been modified.
    In order for the applications to operate properly, there is no need to recompile the projects with the new version of the component. The component (.WDK file) can be distributed to the end users directly.
  • Second case: the component was modified in order to add a parameter to a procedure for instance. When generating the component, the "number of last compatible version" was modified.
    In order for the applications to operate properly, the projects must be recompiled with the new component version. Otherwise, the applications will refuse to operate in order to avoid problems due to potential incompatibility with the new component version.
Minimum required version
  • Version 9
This page is also available for…
Comments
Click [Add] to post a comment