The Gestalt of Nucleus

Building an application with Nucleus offers many user-interface options using the same rules addressing the data.

Building the ruleset (or screen) using WINMAINT creates a container for the objects - within a 'script' found in the WINSCREENS file. The script, initially deployed in character mode, defines the object 'set'.

Within Nucleus, the objects (file, fields) and their respective properties (attributes, conversions, correlatives, associations, length, justification, pre-field, post-field, special events, etc.) are mapped as a cohesive rule-set that supports multiple user interfaces as well as the data access and update rules.

When selecting (G)ui template from the WINMAINT menu, Nucleus creates a template (table) within GUIAPPS. This template is (initially) specific to the parameter set required by Accuterm. Through the GUI template manager, you can modify the template using Accuterm's designer.

VB objects can be easily incorporated through the Accuterm designer. The Gui template manager merely extends the character mode to create a VB application controlled and/or interpreted by Accuterm through a Nucleus 'wrapper', eliminating the hand-work.

This template stored in GUIAPPS is passed between the Nucleus engine and the Accuterm drivers. Using Accuterm by itself to create an application bypasses most of the opportunities provided by Nucleus and mandates manual coding without the benefit of source code controls, whereas the preferred method, developing a Nucleus screen may involve zero coding beyond the Nucleus script and the fields within it.

NuQL ( offers access and rule-based updates using the rule-set defined within a Nucleus screen.

The goal with Nucleus is simplifying support through the use of a standard framework that easily incorporates multiple interface styles and technologies.

A design requirement of Nucleus, was that the 'framework' could never be so rigid as to preclude innovation by developers.

See also

  • Style and the user interface