Configuration files are used for configuring look and behavior of your programs and applications at different stages of their development and usage.
Besides, configuration files influence the work of certain Lycia components, e.g., LyciaStudio.
Lycia includes a number of configuration files that can be roughly divided into 3 groups:
Files influencing runtime
Files influencing design time
Files influencing compilation time
Some configuration files exist in 3 different variants - user, master, and application:
User files - UserTheme.qxtheme, UserTheme.css, UserActionDefaults.ad2, and UserResources.tr2 are global user-defined files that contain default values for programs and are loaded automatically with the 4gl program.
Master files - Master theme, Master css style, Master action defaults file, and Master resource file - share the name with the 4gl program, are loaded automatically when it is run and are used to secure its unique appearance and behavior as compared to other applications developed for the same company.
Application files - Application theme, Application css style, and Application action defaults file - are user-defined files that are loaded from the 4gl code and are mostly used for changing its runtime appearance and behavior depending on the current tasks and purposes.
Lycia components search for their configuration files in this order:
In the default configuration folder:
The only exception is inet.env – the path to inet.env is searched for and taken from listener.xml (if any). If there is no listener.xml, then Lycia components search for inet.env in the order as any other configuration file.
If the necessary configuration files is not found, Lycia components will used the default configurations.