WINDEV Concepts

78 Part 2: Development environment • Right-click to open the context menu and select "Description". • In the "Details" tab, you can get the details of the generated documentation. The documentation specific to an element of the component (window, etc.) can be viewed: • by double-clicking the desired element in the Project explorer pane or by pressing F2 in the code of the element. • from the "Project explorer" pane: • Select the "External components" folder. • Right-click to open the context menu. • Select "List of external components imported into the project". 7.2 Component element visibility When you create a component, you can define which elements of the component will be accessible to end users. • If an element is accessible, the user will see it in the list of project elements. Users will be able to handle these elements programmatically (like any other element in the project). Remark : The code of this element is not visible. • If the element is not accessible, the user will not even know that it exists. Caution : Depending on how the project elements are declared (classes, sets of procedures, etc.), the elements that are accessible may change. 7.3 WDO file When generating the external component, multiple files are automatically created in the EXE directory of the current project: <Component name>.WDK Contains all the WINDEV elements to be redistributed with the component (windows, reports, etc.). <Component name>.WDI Component interface. This file contains: • a help text on how to use the component when it is reintegrated, • the elements required to use the component in the project (compilation information, etc.). <Component name>.WDZ File with the dependencies of theWDK file (only for WEBDEV and WINDEV Mobile components) File containing the dependencies of the WDK file. This information is extracted in the project in which the component is integrated. • For a WEBDEV component, this file contains the generated WEBDEV pages, images, etc. • For a Mobile component (iOS or Android), this file contains the Android generation files, for example. These files must be distributed along with the component. If the external component uses additional elements (data files, for example), the following files must be added in the project EXE directory: • a <Component name>.WDO file: This file contains the list of external files (data files, text files, etc.) used by the external component. These files must be provided and installed with the external component. • the files that must be distributed with the external component. These files can be in a specific subtree. In this case, the code of the external component must manage the access to these files based on this tree structure. What is a WDO file? The <Component name>.WDO file is a TXT file that can be created and edited at any time. This file can be created and edited with Notepad, the Windows standard text editor. This file contains the list of external files (data files, text files, etc.) used by the external component. These are also the files that must be provided and installed with the external component. These files must be copied to the EXE directory of the projects that use the external component. This ".WDO" file can contain: • the full name of the file. For example: C:\ComponentsWD\ PickerComponent\InitialStatus.INI • the file name. This file will be searched in the current directory of the external component. For example: InitialStatus.INI