Events

Fore is an event-driven state-engine. It reacts to events and dispatches itself events to reflect it’s state. Each operation in Fore is triggered by some event. You can hook your functionality into the page by defining actions for a given event.

Lifecycle Events

Lifecylce events can be used for initialization tasks. When Fore is loaded into the DOM of a web page it will dispatch the following sequence of events:

For all work that should be done before the first rendering takes place use a ‘model-construct-done’ handler. This is the best place to load additional data and do more complex initialization tasks as all actions triggered by ‘model-construct-done’ will run within a single update cycle.

On ‘ready’ you can rely on the UI being fully rendered. This also means that all ‘init’ events attached to controls have been executed and eventual custom initialization tasks have been run.

General Events

A Fore Action can listen to any event. These might the native ones or custom events.

If events specify a details object this can be accessed with the Fore event('propname') function. See under Functions.

Update Cycle Events

Some actions mutate data and report this to the model by setting a ’needsUpdate’ flag. When an action block is done it will check for the flag and update the model and UI accordingly by:

• optionally fully rebuild the model constraints (usually avoided)
• recalculate changed items
• revalidate changed items
• refresh controls/containers bound to changed items

Control State Events

State events are dispatched whenever the state of a bound element changes.

Instance Events

Submission Events

Repeat Events

Switch events

Dialog Events

Other