Publishing desktop applications

Documentation status: reference — see Maturity and evidence.

A desktop application is one possible rendering target for a logiCells view. The model, actions, rules, services, datasets, and UXfc intentions remain independent from the concrete UI toolkit.

Principle

model
  -> view projection
  -> functional components
  -> page controller / local visual events
  -> desktop renderer

The desktop renderer may provide windows, panels, menus, shortcuts, drag-and-drop, or OS integration. Those details must not become business contracts.

Local events

UI events that only change visual state may remain in local page coordination. When an interaction changes business state, it should invoke a model action, process, or published capability.

Reactive frames

A reactive region is useful when an area of the interface must host dynamic child views, route local events, or switch projections according to context. It remains a presentation construct and does not replace a business workflow.

Portability

The public documentation describes intentions and functional contracts. Native classes or details of a specific renderer are outside this public surface.