Skip to content
EN FR

Views and UX

Documentation status: guide — see Maturity and evidence.

This section turns the view and UX material into an implementation-oriented path. A view is a projection of a concept in an interaction context. It should preserve the model boundary: components consume page data surfaces, local events are coordinated by the page, and business changes cross into the Runtime only through explicit actions, posts, processes, services, or conceptual events.

  1. View projections and UXfc
  2. ObjectBehind and PageControler
  3. View data cache
  4. DataSetManager events
  5. Reactive desktop frames
  6. Web reactive components
  7. Dynamic forms, lists and dashboards
  8. View diagnostics and testing

The core boundary is:

conceptual model / collections / actions
              |
              v
       view data cache
DataSet + DataSource + DataCursor
              |
              v
 PageControler + PageModel + ObjectBehind
              |
              v
   functional/UXfc components
              |
              v
       concrete rendering

A developer should be able to change the rendering technology without redefining the business concept, and to change the data provider without rewriting the component contract.