|
|
|
|
|
|
|
|
|
|
- Principle
- Implementation required to use an interface with an external language
- Files required to run the program written in external language
- WINDEV libraries (".DLL" files)
- Libraries of the WINDEV application
- Examples provided with WINDEV
Overview of external languages
WINDEV can also be used to create elements that will be supported in programs written in C, C++, Pascal, Visual Basic, Cobol, etc. All you have to do is call the WINDEV elements from the external language. This call can be done from a program (".EXE" file) or from a library (".DLL" or ".OCX" file) compiled in external language. To call a WINDEV element from an external language, use CallWD. Remark: It is also possible to use processes written in an external language (in the form of compiled libraries) in a WINDEV application.. To do so, you must compile a library (".DLL" or ".OCX" file) in external language and call the processes of this library via the WLanguage API or CallDLL32 function.
Warning: WINDEV can only compile WLanguage code.
The available languages are as follows: Implementation required to use an interface with an external language To use the elements developed in WINDEV with an external language, select "External languages" when installing WINDEV. Note: The files required by the "External languages" are automatically installed during a full setup of WINDEV. Attention: Your external language compiler must be installed on the development workstation. Files required to run the program written in external language To run the program written in external language, you must have: - The WINDEV libraries (".DLL" files).
- The libraries specific to the external language used.
- The executable programs written in external language.
- The libraries of the WINDEV application.
- The analysis associated with the WINDEV application. This analysis can be included in the library.
WINDEV libraries (".DLL" files) The program written in external language requires the WINDEV libraries in order to operate (call to the WLanguage functions, use of graphic objects, ...). These libraries are listed when the executable is created in WINDEV. Refer to this list to find out the different libraries used by the WINDEV application ("wdxxx*.DLL") files. The listed libraries as well as the wdxxxle.dll and wdxxxcpl.dll libraries must be copied into the runtime directory of the program written in external language. Remarks: - In Java, you also need to copy the wdXXXIJV.DLL library.
- In C#, you also need to copy the wdXXXICS.DLL library.
- In Fortran and Cobol, you also need to copy the wdXXXFL.DLL library.
Libraries of the WINDEV application The libraries of the WINDEV application contain all the windows, reports, images (and other files) of the WINDEV application. Note: When running the test of the program in the editor of external language, if the libraries (".WDL" file) are not found, the path of the libraries must be specified when they are opened. Special case: In Visual Basic, the following Visual Basic functions must be used to specify the path of the libraries: chDir and chDisk. Examples provided with WINDEV WINDEV includes a full example for each available language. These examples can be found in the "External Languages\EN\<LanguageName>" subdirectory of the WINDEV installation directory. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|