Actions
In an EBIF resource, programmatic (procedural) information takes the form of byte code, where each operation and its (optional) operands is referred to as an action. Actions are organized into sequences by means of one or more action tables where each entry points at (1) an encoded action and (2) the action table index of the next action to execute after the current action's execution is completed. An action sequence terminates when the next action table index is a special value (0xFFFF) or in the case of certain flow of control actions. Action sequences effectively represent one or more traditional code blocks with potential internal looping behavior.
Action sequences are executed as a result of firing certain predefined events, such as a page load event, a key press event, a click event, etc. As such, all programmatic execution takes place in the context of event handlers, whose execution is serialized by an ETV User Agent.
The following categories of actions are defined by EBIF:
- Flow of Control Actions
- Predicate Actions
- Variable Store Actions
- Arithmetic Actions
- Boolean Logic Actions
- Mathematic Actions
- String Actions
- Array Actions
- Application and Page Actions
- Widget Actions
- Table Actions
- Miscellaneous Actions
Read more about this topic: Enhanced TV Binary Interchange Format
Famous quotes containing the word actions:
“The principal office of history I take to be this: to prevent virtuous actions from being forgotten, and that evil words and deeds should fear an infamous reputation with posterity.”
—Tacitus (c. 55–c. 120)
“When our actions do not,
Our fears do make us traitors.”
—William Shakespeare (1564–1616)
“They are actions that a man might play,
But I have that within which passes show,
These but the trappings and the suits of woe.”
—William Shakespeare (1564–1616)