Features of X/E Files
Here are some of the features of X/E Files tool developed by Javra Software, (http://www.javra.com).
The X/E Files is written in pure Progress 4GL. No other components are needed. Programs that were created in the first version of the X/E files are still running today without changes; and those programs are running with the most modern user interfaces. As we upgrade X/E files to employ the latest user interface technologies your existing applications can make use of these user interfaces effortlessly.
Repository based development
- The X/E Files derives its power from its fully repository based approach. When new programs are developed with the X/E Files the program logic is stored in a Progress Database.Since the program logic is stored in the repository as data, the X/E file is able to render the same program logic across different user interfaces. Additionally since the program logic is in the repository changes can be made dynamically.
Some of the program logic that is stored in the database repository is:
• Menu structure
• Screen layout (e.g. widget placement and properties, icons, tool bars)
• Browser configuration (including dynamic queries)
• Security settings (Program and Widget security, as well as record Create, Update and Delete security)
• Data validation rules
• Multi-languages
• Event mappings
Dynamic Runtime
The X/E Files "master files" generates at run time all the on-screen program objects based on the properties stored in the repository tables. The master files are a configurable set of programs maintained by Javra Software that enable runtime changes in programs, as well as enabling existing programs to be run through different user interface technologies. The master files give the following benefits:
• Program logic is written once and can be run on different interfaces/platforms. Currently supporting:
• Windows GUI, HTML and Microsoft XAML.
• Program properties are maintained centrally.
• Fully personalized user interface.
• Enables runtime multi-language support.
• Program changes can be made without recompiling.
Triggers, Events and the Application Servers
X/E Files enables integration of custom business logic through triggers and events; i.e. developers can hook in their own custom Progress 4GL/ABL code. Fifteen event types are supported operating on both the widget and program level.
Custom Business logic executed through events and triggers may be run through the Progress Client or on a Progress OpenEdge Application Server. The choice to use of Application Servers is part of the dynamic runtime configuration in X/E Files.
More of the features will be on next post at http://www.oehive.org/node/1332