The ApplinX Framework contains three development methods:
In this development method the Web application is developed in a framework driven manner, which means all activity is performed by the ApplinX Web application and you have the ability to make changes within the framework flow.
The use of this methodology is accomplished when inheriting from GXDefaultLogicContext (JSP)/GXDefaultLogicWebForm (.NET) , which includes host keys' handling, and in general, an automatic workflow with the ability to make changes using user exits.
In this development mode, most host screens remain as Instant HTML pages, meaning they are generated on the fly by ApplinX Framework, without generating specific Web pages (JSP or ASPX) for individual screens. Thus, the development process is quicker and simpler, and maintenance efforts are significantly reduced.
Customization of the instant pages is done using Instant Transformationsand using Screen Groups. Often, there isn't even a need to identify individual screens. Server transformations defined using the Transformation wizard in ApplinX Designer will be displayed in the instant pages. The page used in the kind of development is GXInstantLogicContext (JSP) /GXInstantLogicWebForm (.NET) , which contains Instant Transformations registration.
The ApplinX framework exposes another methodology for development. You may use this methodology by changing inheritances for the project pages to GXBasicContext (JSP)/GXBasicWebForm (.NET). This methodology is accomplished by using server-side buttons and the use of the framework API's as "building blocks" (gx functions).
ApplinX Procedures Development: The ApplinX framework allows you to minimize the logic in the application classes. In this case, the framework's purpose is to serve as a controller/viewer, using Web pages with dynamic tags/controls. Most of the logic development is performed using flow procedures, which accept and return simple parameters/data structures. After developing the flow procedure, the ApplinX Add-in generates procedure client classes (which should not be modified) and a Web page (you can customize to suit your needs), which is bound, bi-directionally into the Web page using the code class, and binding functionality. Refer to Working with Procedures.