cb767ed115
Split the monolithic MODULE__AE_Events_PressMgmt_Launcher.md into focused, granular modules to improve maintainability and onsite utility. - Created MODULE__AE_Events_Presentation_Management.md (Back-office focus) - Created MODULE__AE_Events_Launcher.md (Podium display focus) - Created GUIDE__AE_Events_Onsite_Runbook.md (SRR and onsite workflows) - Promoted PROJECT__AE_Events_Launcher_Native_integration.md to MODULE__AE_Events_Launcher_Native.md (Permanent technical reference) - Renamed 'Press Mgmt' references to 'Presentation Management' for clarity. - Removed redundant README.md in launcher route. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
3.3 KiB
Aether Events — Launcher (Podium Display)
The Launcher module provides the podium display interface that runs on each session room's kiosk machine. It is designed to work in standard browsers but is optimized for the Aether Desktop (Electron) native shell.
Operational Modes
| Mode | Use Case | File Handling |
|---|---|---|
| Default | Browser on any machine | Files downloaded on demand via browser. |
| Onsite | Browser on event network | Faster polling; browser-managed files. |
| Native | Electron app on podium Mac | Background pre-cache; atomic file handover. |
For production onsite use, Native mode on Mac laptops is the target. The Electron app pre-caches all session files in the background so presentations open instantly without a network round-trip at the moment of launch.
Launcher Display Views
| View | Shown When |
|---|---|
| Session view | Active session with session-level files. |
| Presentation view | Active session with named presentations. |
| Presenter view | Presentation selected; shows presenter bio/photo. |
| Poster/group view | Special layout for poster sessions. |
| Screensaver | No active session; idle state. |
Sync Engine & File Handling
Background Sync (File Warming)
When a user navigates to a session in the Launcher UI, the background engine automatically warms the cache for that specific session by downloading all associated files.
Force Sync Location
To ensure full room readiness (e.g., during SRR setup or overnight), operators can trigger a Force Sync Location via the configuration menu. This performs a recursive fetch of all sessions, presentations, and presenters for the room and queues every file for the day for download.
Download Priority & Room Readiness
To ensure the podium is ready for the day's first sessions, the Launcher sync engine uses a 4-tier chronological sorting priority:
- Global Assets: Event and Location level files (branding, walk-in slides) are cached first.
- Session Schedule: Files for the earliest sessions in the room are prioritized.
- Presentation Order: Within a session block, speakers are prioritized by their scheduled start time.
- First-In Fairness: When times are equal, older uploads are prioritized over late revisions (respecting on-time presenters).
Native File Opening (Safe Handover)
- Verify SHA-256 hash in permanent cache.
- Atomic copy to system
[tmp]directory. - Rename to original filename (e.g.,
Abstract_101.pptx). - OS opens the file via a Launch Profile (AppleScript or Shell command).
Device & Native Integration
Each Launcher kiosk is registered as an event_device record in Aether. The technical specifications for the Electron bridge, hashed cache protocol, and hardware actuators are documented in:
👉 MODULE__AE_Events_Launcher_Native.md
Route Map (Display)
| URL | Purpose |
|---|---|
/events/[id]/launcher |
Launcher home — select location |
/events/[id]/launcher/[location_id] |
Launcher display for a specific room |
Access Levels
| Feature | Minimum Access |
|---|---|
| View Launcher display | authenticated_access |
| Manual session selection | trusted_access |
| Advanced Config / Sync Control | trusted_access (via Configuration Drawer) |