docs(launcher): align launch profile terminology

This commit is contained in:
Scott Idem
2026-05-13 11:50:13 -04:00
parent 49c6a2351e
commit c79ae92be0
3 changed files with 52 additions and 27 deletions

View File

@@ -311,12 +311,14 @@ The Electron app zero-configs itself:
3. Rename to original filename (e.g., `Abstract_101.pptx`)
4. OS opens the file (Keynote, PowerPoint, Preview, etc.)
**Configurable launch behavior:** The open/launch command in step 4 can be overridden
per file extension via `event_device.data_json.launch_profiles` (device-level config) or
`event.launcher.launch_profiles` (event-level fallback). Templates use `{{path}}` as the
file path placeholder; AppleScript or `shell:` prefixed commands are both supported. No
Electron rebuild required to change how files open — edit config in Aether and it applies
See `PROJECT__AE_Events_Launcher_Native_integration.md` Section 8.
**Configurable launch behavior:** The file-open behavior is driven by a Launch Profile, not
just a command string. Profiles are stored per file extension in
`event_device.data_json.launch_profiles` (device-level config) or
`event.launcher.launch_profiles` (event-level fallback). A profile can choose the app,
display mode, open command, and post-open automation. The resolved native template uses
`{{path}}` as the file path placeholder; AppleScript or `shell:` prefixed commands are both
supported. No Electron rebuild is required to change how files open — edit config in Aether
and it applies immediately. See `PROJECT__AE_Events_Launcher_Native_integration.md` Section 8.
Versioning is handled automatically: when a presenter uploads an updated file, the new
hash is cached separately and the old one remains intact.