PC SOFT

WINDEVWEBDEV AND WINDEV MOBILE
ONLINE HELP

Home | Sign in | English UK
New WEBDEV 24 feature!
  • Overview
  • Creating an internal component
  • The different steps
  • Internal component and analysis: case of total autonomy
  • Sharing the internal components (via SCM)
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
10. Internal component in practice
Previous pageTable of contentsNext page
Overview
An internal component is a group of project elements. This group is used to:
  • Organize a project: the internal components can be used to group the project elements, by feature for example.
  • Share the elements among several projects: The elements found in an internal component can be shared between several projects via the SCM. See Sharing the internal components (via SCM) for more details.
One of the benefits of internal component compared to a standard component is that the internal component can be debugged from the project that is using it.
Difference with a standard component: An internal component allows you to include all the component elements in the interface of the project containing the internal component. All the "public" elements of internal component can be directly handled in the editor.
When using a standard component, the "public" elements of component cannot be handled directly. To modify the standard component, the corresponding project must be opened.
Creating an internal component

The different steps

To create an internal component:
  1. On the "Project" pane, in the "Project configuration" group, expand "New configuration" and select "Internal component". The wizard for creating an internal component starts.
  2. Specify the characteristics of the internal component:
    • its name. The name of internal component will be used for the WCI file corresponding to the description of internal component. This name will also be used to create a sub-directory in your project containing all the elements of internal component.
    • its caption.
    • its description.
  3. Indicate the elements that will be included in the internal component. An internal component can contain all types of elements found in a project: pages, reports, templates, ...
  4. Specify the elements of internal component that will be directly accessible in the code and in the preset actions of project that is hosting the internal component.
    Note: The accessible elements (or "public" elements) will be automatically proposed by the completion. They can be used by the elements found in the project or from another internal component. The inaccessible elements (or "private" elements) can only be used by another element of internal component (the completion will propose these "private" elements only from the elements of an internal component).
  5. Specify the management mode of data and runtime contexts. Three modes are available to manage data and runtime contexts:
    • Use the project analysis or no analysis (full share): The internal component accesses the data files of the project. The internal component and the project use the same runtime contexts.
      This mode corresponds to the default mode if the internal component is using no analysis.
    • Use the project analysis with different runtime context (advanced mode): The internal component accesses the data files of the project. The internal component and the project are using different runtime contexts.
      This mode is reserved to specific cases.
    • Use a specific analysis: The internal component accesses its own data files. The internal component and the project are using different runtime contexts.
      This mode corresponds to the default mode if the component uses an analysis.
      In this case, the analysis used by the internal component must be specified. You also have the ability to create a new analysis directly. This analysis will be associated with the internal component.
  6. Validate the creation of internal component. At any moment, it is possible to:
    • Modify the characteristics of the internal component via the description window of internal component.
    • Handle the internal component and its elements.
    Tip: An internal component contains no code for declaring the global variables. A set of procedures can be used to initialize the internal component.

Internal component and analysis: case of total autonomy

An internal component can be linked to its own analysis. In this case, the project that is hosting the internal component can have several analyses:
  • the analysis of the project.
  • the analysis of internal components. This analysis is defined when creating the internal component. It can also be selected from the description window of the internal component.
The elements generated by RAD for the internal component will be generated in the directory of internal component. If the analysis of the internal component is modified, a new generation by RAD will automatically propose to generate the elements corresponding to the modifications.
Sharing the internal components (via SCM)
The internal components can be shared between projects via the SCM.
To share an internal component via the SCM, the project containing the internal component must be found in the SCM. You can:
  • create the internal component from a project found in SCM. The internal component will be automatically found in the SCM.
  • import a project containing one or more internal components into SCM. The internal components will be automatically included in the SCM.
Previous pageTable of contentsNext page
Minimum version required
  • Version 24
Comments
Click [Add] to post a comment