AAC UI: Integrate AAC-native MainWindow, StateMachine, and backend adapter #3102
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
….cpp to Client/qtTeamTalk/src/aac/aac_module.cpp
….h to Client/qtTeamTalk/src/aac/aac_module.h
…amTalk/src/aac/ui/aac_ui.cpp
…aac/aac_module.cpp
…lk/aac/state_machine.cpp
…/aac/state_machine.h
…build This commit introduces the first stage of the AAC‑native UI module. It adds the following new components: • aac/state_machine.* – core AAC UI state machine • aac/events.h – event definitions for AAC transitions • aac/ui/aac_ui.* – minimal AAC UI surface • aac/aac_module.* – module entry point and integration layer The new files are added to QTTEAMTALK_SOURCES without modifying any existing build logic, deployment rules, or platform‑specific sections. No behavioural changes are introduced; this commit only provides the structural foundation for future AAC‑native UI work.
…ation testing This commit updates main.cpp to include and instantiate the AAC‑native MainWindow instead of the legacy QtTeamTalk UI. The change is intentionally minimal and fully reversible: only the include path is updated, and the legacy MainWindow remains untouched. This enables end‑to‑end testing of the AAC UI flow (Connect → Connecting → Channel List → In‑Channel) and is required for validating the AAC StateMachine and BackendAdapter integration in PR#8 and PR#9. No behavioural changes are introduced outside the UI entry point, and all platform‑specific event handling, TeamTalk initialization, and application lifecycle logic remain unchanged.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces the first fully functional version of the AAC‑native UI flow and wires it into the Qt client for integration testing. The goal is to validate the AAC StateMachine, BackendAdapter, and UI navigation loop end‑to‑end while keeping all legacy UI code intact and untouched.
Summary of changes
•
Added AAC‑native UI components:
◦
MainWindow
◦
StateMachine
◦
ConnectScreen
◦
ConnectingScreen
◦
ChannelListScreen
◦
InChannelScreen
•
Integrated AAC UI into the application entry point by switching the include in main.cpp
(Legacy MainWindow remains available and unmodified.)
•
Added AAC UI sources and headers to CMakeLists.txt
•
Ensured the AAC StateMachine and BackendAdapter are compiled and ready for PR#9 integration
•
No behavioural changes outside the AAC UI path
Purpose
This PR enables:
•
running the AAC UI from application startup
•
validating the AAC navigation flow (Connect → Connecting → Channel List → In‑Channel)
•
testing the BackendAdapter and StateMachine wiring
•
preparing a stable baseline for the backend integration work in PR#9
Notes
•
The change to main.cpp is intentionally minimal and fully reversible.
•
All legacy UI files remain untouched.
•
This PR does not remove or replace any existing UI functionality.