[Discussion] Expand Data Source
Closed this issue · 4 comments
To set the stage: I'm currently working on a StreamDeck plugin for Firebot, a Twitch chatbot. Firebot has something called preset effect lists, that can be controlled via API. Effect lists can have variables that you can pass on execution. I'd love to essentially have a group of sdpi-textfields that are controlled by a data source (array of label strings) that output into an object as it would greatly simplify my end of things with the plugin.
@GeekyEggo Would you be okay with having a component like this? If so, I'll have a look at implementing and contributing it.
now that I think about this more with coffee, this is way out of scope for this project.
Hey @dennisrijsdijk, I have similar experiences with coffee, so I empathize, lol. 😄
Even if out of scope, I'd still be interested to know more about your use case if you'd like to elaborate? Specifically it would be good to know the desired data structure of the settings you're trying to produce.
I wanted to also provide a bit more insight into the future of this project; it's very much alive, however it will soon be archived here. Instead, it will have a new home @elgatosf where it will be officially maintained by Elgato. 🎉
Basically, Firebot's API provides an array of argument keys (because arguments are user-defined when creating the preset list), where the value is always of type string
Essentially, datasource is eg. [ "username", "currency", "duration" ] which should generate the following object inside settings:
{
username: "input",
currency: "input",
duration: "input"
}
Then on button press, I can call the Firebot API route with that object so to populate the arguments for running the effects list
I've had this working before by abusing the dom, but would prefer a more integrated solution.
I should mention, if the Node SDK gets a replacement for the PI (eg. defining fields in the onPropertyInspectorDidAppear and subsequent events) that'd also tick the boxes for what I'd need