Repository navigation
Should the scripting interface become a small supported API? #1336
philippwallrafen
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Twinkle Tray already exposes useful scripting functionality through the Named Pipe/UDP interface: monitor listing, brightness control, VCP access, refresh commands, etc.
PR #1335 is a small first step toward making that interface a bit more predictable by adding optional versioned responses without changing existing clients.
I wanted to check whether formalizing this interface further would be useful for the project.
My thought is to keep it very incremental:
The main benefit would be making scripting and automation more reliable while also giving the internal monitor-control implementation more freedom to change later.
Would this direction make sense for Twinkle Tray? If so, I could keep follow-up PRs small and focused, starting with documenting and normalizing the existing commands.
All reactions