User:Dbrawlins/FPL
 | This is not a Wikipedia article: It is an individual user's work-in-progress page, and may be incomplete and/or unreliable. For guidance on developing this draft, see Wikipedia:So you made a userspace draft. Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
| Developer(s) | Ebase Technology |
|---|---|
| Initial release | 2002 |
| Stable release | V4.1
/ December 13th, 2010 |
| Operating system | Windows, Linux, Unix |
| Available in | English |
| Type | Programming Language |
| License | Proprietary and Free/Community |
| Website | Ebase Technology |
In computing, FPL is an interpreted procedural and scripting language developed by Ebase Technology and distributed with its Ebase Xi software development platform.
Concepts
[edit]FPL is designed to provide Ebase Xi application developers with a simple command syntax that enables run time processing control over data validation, navigation, security, presentation management, printing, workflow process routing, and integration with external data sources.
Run-time Context
[edit]The Ebase Xi event model associates FPL scripts with run-time events. When an event is triggered an associated FPL script executes in the run-time context of the application element that triggered that event, and will legitimately address the properties of any element within that context. For example, an FPL script is associated with the On Change event of a particular Field Control on an Xi Form. When a user changes the screen value of the Field Control the On Change event fires and the FPL script executes. The script then executes its processing logic, addressing, for example, other Xi Form Fields, Resources and Control properties.
The same FPL script may be associated, via the event model, with any number of different Xi application elements. For example, a script that handles payment processing within a financial application may be called in response to events being triggered from many different parts of that application.
FPL scripts are triggered via the execution of Xi application elements, i.e. Forms, Components, Workflow proceses and Web Services. The scripts are not tightly bound to a particular element at design time and cannot therefore be type checked prior to execution. At run time scripts will execute on the assumption that the required application context is provided by the element that triggered their execution, and will generate run time errors if the addressed elements cannot be located. For example, a script may attempt to set a Form Field to a particular value and will error if a Field of that name (and appropriate data type) can be found.
FPL scripts are held as data within the Xi repository and are dynamically interpreted and executed by the Ebase Xi Server when triggered by an application event.
Run-time Functions
[edit]structural: loops, if the else subroutines printing control properties navigation interpret character, date, arithmetic addressing resources calling other forms calling URLs application locking
Error Handling
[edit]Data Types
[edit]scalar tables weak typing
Extensibility
[edit]custom functions
Language Grammar
[edit]URL
Language Reference
[edit]URL