|
|
|
|
|
|
|
|
|
|
- Overview
- Modifying a component
- Adding or deleting an element into/from a component
- Modifying a component element
- Regenerating the modified component: managing compatibility between different versions
- The different types of compatibility
- Definition
- Backward compatibility
- Forward compatibility
Modifying an external component
An external component created and generated by WINDEV, WEBDEV or WINDEV Mobile can be modified at any time. This change may correspond to: - add elements into the component,
- delete elements from the component,
- edit rights on the elements of the component,
- make changes to one of the elements of the component.
In all cases, after this modification, the component must be regenerated to take account of the changes made. This help page presents: Note: Reports integrated into a component cannot be modified using Reports & Queries. Adding or deleting an element into/from a component To add or delete an element into/from a component: - Open the component project: under the "Home" pane, in the "General" group, pull down "Open" and select "Open project".
- On the "Project" tab, in the "Project" group, expand "List of elements" and select "List of generated components".
- The component description window appears. This window allows you to perform the following modifications:
- Modify a component ([Modify] button).
The component modification wizard 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.
- Regenerate the component.
Modifying a component element To modify a component element: - Open the component project: under the "Home" pane, in the "General" group, pull down "Open" and select "Open project".
- Open the desired element.
- Make the desired changes.
- Save these changes (
 ). - Regenerate the component: click on the generation icon among the quick access buttons:
Regenerating the modified component: managing compatibility between 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: - Start generating the component:
- click the generation icon in the quick access buttons.
- via the component description window ([Generate]).
- The component generation wizard starts.
- 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:
Phase 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 Compatibility is linked to the versions of the component. If changes are made to the component, the applications that use the component may encounter runtime problems if they are not synchronized with it. The management of compatibility is an important step in the modification of a WINDEV component. There are two types of compatibility: - Backward compatibility: the version of the component (.WDK file) used to compile applications using this component must always be greater than or equal to the version currently in use..
WINDEV manges compatibility automatically. If the version of the component installed with the application is earlier than the version used by the application, the application will not run. - Upward compatibility: use of a new version of a component with projects compiled with an older version may be prohibited. You need to recompile the projects 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:
A project is compiled with a component in version 1.00C.
1.00C is the reference version. This means that the applications that use the component will only run if the component version is greater than or equal to the reference version. The following cases can occur: - First case: Customer applications use the component (.WDK file) in a version lower than 1.00C. An error will occur when loading these applications.
- Second case: Customer applications will work if they use the component in the expected version.
- Third case: Customer applications will also work if the component is of a higher version than the one expected (only if the new version only corrects malfunctions)..
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 sets the reference version from which the applications that use the component will run. Example:
A project that uses a component in version 1.00C has not been recompiled with the new component version (1.00E). Version 1.00E of the component is installed on the deployment computers. The following cases can occur: - First case: the component has been modified only to correct certain malfunctions. When generating the component, the "number of the last compatible version" is not 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 has been modified to add a parameter to a procedure, for example.. When generating the component, the "number of the last compatible version" is modified.
In order for the applications to run properly, the project must be recompiled with the new component version. Otherwise, applications will not run to avoid compatibility errors with the new component version.
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|