Summary
Use Apple's ScriptingBridge framework for better typed access to specific apps, replacing or supplementing the current AppleScript template approach.
Details
- Evaluate ScriptingBridge as a replacement for NSAppleScript-based execution in the Swift executor
- ScriptingBridge provides compile-time type safety and better performance than interpreted AppleScript
- Could be adopted incrementally, app by app
- Requires generating
.sdef-based header files for target apps
- May not cover all apps equally well — some apps have better ScriptingBridge support than others
Affected files
packages/executor-swift/Sources/Executor/ — new ScriptingBridge-based modules
packages/executor-swift/Package.swift — framework dependency
Phase 23 item
From TODO.md
Phase 23: ScriptingBridge — Use ScriptingBridge for better typed access to specific apps
Summary
Use Apple's ScriptingBridge framework for better typed access to specific apps, replacing or supplementing the current AppleScript template approach.
Details
.sdef-based header files for target appsAffected files
packages/executor-swift/Sources/Executor/— new ScriptingBridge-based modulespackages/executor-swift/Package.swift— framework dependencyPhase 23 item
From TODO.md
Phase 23: ScriptingBridge — Use ScriptingBridge for better typed access to specific apps