~aleteoryx/muditaos

ref: cbe1ed63e541777a46109bcb1240a45e678fb2ec muditaos/module-apps/apps-common/notifications/README.md -rw-r--r-- 1.1 KiB
cbe1ed63 — Maciej Gibowicz [BH-1801] Fix incorrect calculation of requested CPU frequency 2 years ago

#Home Screen Notifications

#General structure

The general structure is based on the Model-View pattern on the front-end, supplied with a Provider's back-end notifications as follows:

#Provider structure

On the provider's end, Notifications are managed by NotificationProvider and sent as an NotificationsChanged action with NotificationsChangedParams via ApplicationManger's Controller.

The NotificationProvider is responsible for creating and managing Notifications. Each Notification represents a unique event and thus at most single object (of a respective type) can be stored in the provider. The provider's structure is shown on following diagram:

#Model-View structure

NotificationsModel is responsible for creating and decorating NotificationListItems based on NotificationsChangedParams received. The model serves also as a local provider for gui::ListView.