Widget Data Model
Every widget is represented by a server-side context that contains configuration of widget layout, components, bindings, and more.
At the same time, once a widget is launched a separate context tree is created that represents running widget's data model. Each context of widgets's context tree represents a single UI component of the running widget. All component contexts are added to the root of widget context tree, so component context hierarchy doesn't match hierarchy of widget's nested containers and components.
Variables, functions and events of a widget component's context match properties, operations and events of this UI component. Thus, addressing component context entities from widget bindings is effectively a process working with UI component, e.g. configuring them, reacting to their events, etc.
Was this page helpful?