unity-qframework-design

QFramework uses four layers: IController for presentation, ISystem for logic, IModel for shared data, and IUtility for infrastructure. Controllers change state only through Commands, and lower layers notify upward via Events or BindableProperty.

The core IOCContainer is a thin Dictionary<Type,object> wrapper supporting only singleton registration inside Architecture<T>. Toolkits IOCKit is a separate reflection-based container with [Inject] attribute injection, named registrations, and constructor auto-resolution.

Place data in a Model only if it is shared across time (persisted between sessions), shared across space (used by multiple views or scenes), or is configuration table data. Runtime state like enemy health stays in the owning MonoBehaviour.

AudioKit.Settings fields are initialized in OnInit, which only runs via RuntimeInitializeOnLoadMethod when entering Play Mode. Pure edit-mode scripts that never entered Play Mode must read the underlying PlayerPrefs keys instead.

ResKit recommends AssetBundle loading with reference counting, though it supports Resources, network, and local file sources. During development, simulate mode reads directly from the Assets folder to skip repeated bundle builds.

The most common cause is applying the prefab while UIRoot is selected instead of the UIPanel node such as UIBasicPanel. Apply silently fails on the wrong selection, so no Bind fields are written and no compile error appears.