Form Composition: Subscript

Subscript is the code used to program all functionality in OmegaForms. Snippets are provided via the menu to allow copying common commands into subscript. The Name of the subscript can be attached to component events: when triggered, the subscript will execute. Use the Sort and Tags to organize and focus your coding efforts. Details about the options for Slipstream Subscript are below; more information is available at: www.slipstreamsubscript.com

Slipstream Subscript

The Slipstream specifies what compiler and/or interpreter is applied to the subscript. The following slipstreams are available in OmegaForms:

Anecdotal: Runs a low level, low impact, diagnostics on the subscript during execution. This option is designer for troubleshooting large, form-wide issues.
Classical: The name of the subscript is just an identifier to the collection of subscript and variables used as instructions for OmegaForms. This option should only be used by advanced programmers.

Disfunctional: Creates a Functional subscript where no instructions are executed. This is useful when wanting to turn off a subscript without causing errors from breaking references to a subscript.

Elemental: This option discourages the use of strings, in favor of using variables, and emphasizes the use of simplified keywords to represent common operators and other functionality. This slipstream is designer for beginner programmers.

Functional: Uses the name of the subscript as the name for a function that contains the subscript as instructions. This is the default selection for new subscript.

Methodical: Runs a high level, high impact, diagnostics on the subscript during execution. This option is designer for troubleshooting issues within a subscript.

Organizational: Processes subscript in a manner that is designed to be unique to your organization. This option is useful for companies wishing to invest in preventing code theft.

The Subscript specifies the type of instructions that will be inputted; OmegaForms uses the scope of the overall platform when designating subscripts. The following subscripts are available in OmegaForms:

Client Based: Subscript is expected to be executed on the user’s device. As the processing resources are decentralized, this type of processing allows for more concurrent users accessing the platform. This is the default selection for new subscript.

Report Based: Subscript is expected to be executed on various scopes, ranging from the client’s device to remote databases and servers.

Server Based: Subscript is expected to be executed on a host: not on the client’s device. This is useful for processing sensitive information that will not be exposed to a user.

System Based: Subscript is expected to be executed on a device, with possible elevated privileges, with expanded functionally. This scope addresses processing on machines that may not have users actively accessing hardware.

Web Based: Subscript is expected to be executed on webpages or other public devices that are not controlled by your organization.