graph LR
Posting["Posting"]
MainScreen["MainScreen"]
HelpScreen["HelpScreen"]
JumpOverlay["JumpOverlay"]
Jumper["Jumper"]
Collection["Collection"]
Settings["Settings"]
Posting -- "loads/saves data from" --> Collection
MainScreen -- "loads/saves data from" --> Collection
MainScreen -- "displays/manipulates data from" --> Collection
Posting -- "loads configuration from" --> Settings
MainScreen -- "accesses settings from" --> Settings
JumpOverlay -- "initiates actions handled by" --> Jumper
MainScreen -- "is displayed by" --> Posting
Abstract Components Overview
The root Textual App class, responsible for initializing the application, managing the main event loop, and orchestrating the display of different screens. It serves as the primary controller for the entire application lifecycle.
Related Classes/Methods: None
The default and primary screen displayed to the user, containing the main interactive elements and views of the application. It handles user input for core functionalities and delegates to other components or services as needed.
Related Classes/Methods: None
A dedicated screen for presenting help documentation, keybindings, or contextual information to the user. It provides guidance without disrupting the main application flow.
Related Classes/Methods:
A transient overlay component that provides quick access or navigation capabilities, allowing users to "jump" to specific sections, commands, or data within the application.
Related Classes/Methods:
A service or utility component responsible for the underlying logic of the "jump" functionality, likely managing the targets and execution of quick navigation actions initiated by the JumpOverlay.
Related Classes/Methods:
Manages the collection of requests, including loading, saving, and organizing them. It acts as a data layer for the application's request data.
Related Classes/Methods: None
Handles application-wide configuration and settings, providing access to user preferences and operational parameters.
Related Classes/Methods: None