[][src]Module meli::state

The application's state.

The UI crate has an Box-Component-System design. The System part, is also the application's state, so they're both merged in the State struct.

State owns all the Components of the UI. In the application's main event loop, input is handed to the state in the form of UIEvent objects which traverse the component graph. Components decide to handle each input or not.

Input is received in the main loop from threads which listen on the stdin for user input, observe folders for file changes etc. The relevant struct is ThreadEvent.



A context container for loaded settings, accounts, UI changes, etc.


A State object to manage and own components and components of the UI. State is responsible for managing the terminal and interfacing with melib

Type Definitions