Developing in Development Environment

To design, create, run and debug custom applications, and to develop macros, use the Development Environment tool:

To work in the development environment, install Foresight Analytics Platform development tools.

The Fore language implementation allows for creating a code that can use some functions of the development environment in user application. For details, see description of commands that are used to work with development environment objects.

All classes, interfaces, enumerations and other code blocks in the Fore language are described in the Description of System Assemblies article.

To get description of standard problems encountered by application developers, see the knowledge base.

Development environment allows for creating and using the objects that can contain a code in the Python and Java languages. Such objects are: Python module and Java module.

Python macros cam be edited in the development environment and started for execution. Debugging of a code in the Python language is not supported. Macros can be started both from the development environment and from an application code. For details about creating a loading a code in the Python language see in the description of Python modules.

Java is partially supported, and all the work is executed only from an application code. For details about creating and loading a code in the Java language see in the description of Java modules.

At the level of an application code and in the Modeling and Forecasting, Time Series Analysis and cross-functional expression editor one can use statistic R package methods.

NOTE. Work with Python, Java, and R may require installation and setup of an additional software. For details see the Connecting External Modules to Foresight Analytics Platform article.

Work with external libraries (DLL) or Python units may involve the use of the Comimport/Pyimport respectively.

To create an application visual interface in the desktop application, the development environment provides a number of various components that can be divided into the following groups:

Standard components. Basic components that execute general functions for creating an application graphical interface.
Additional components. Components that provide various possibilities for setting up visual interface and developed taking into account platform object specifics.
Data access components. Special components to access repository objects and to display their data.
Platform components. Components styled to look like the Foresight Analytics Platform interface.

To use a component, add it to the form and set up its properties in the object inspector. For components that are used for data entry, the support of right-to-left writing mode is implemented that can be required, for example, in case of the Arabic language use.

Development of application forms in the desktop application has a restriction concerning possible hierarchy of components position inside component containers. The restriction is related to the restrictions of operating system system functions that recursively send and process Windows messages for each embedded component. In different Windows versions the number of embedded components in the hierarchy, that can be exceeded and the system stops message sending, may differ. Generally, it is not recommended to create a hierarchy of components where the number of embedded element levels is greater than six.

IMPORTANT. Development should only be executed in the test repository version. To synchronize test and production repositories, use the update manager.