[Feature Request] Actionable fields in widgets for basic API controls (i.e., widget 'buttons') #2118
Replies: 4 comments
-
A 'disable' button on PiHole is exactly why I came here. |
Beta Was this translation helpful? Give feedback.
-
linking this here for reference: #3023 |
Beta Was this translation helpful? Give feedback.
-
Im going to close this out because even more explicitly we are now keeping homepage read-only. Thanks all. |
Beta Was this translation helpful? Give feedback.
-
This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details. |
Beta Was this translation helpful? Give feedback.
-
Description
Hello,
I'm starting to make some basic
customapi
widgets, and I'm seeing that some APIs allow for basic controls to be sent to the app/service. I'd be neat if one of the fields within a Homepage widget could be made click-able, to run such a basic action. For example, a 'disable' button for Pi-Hole to temporarily disable blocking.In terms of design,I'm envisioning that a 'clickable' field would look and function like the implementation of 'tabs'. As in, a mouse-over would highlight/distinguish a clickable field, and clicking on it would toggle it to highlight to show that it's 'on' or in its non-default state.
I have zero sense of the feasibility of this, and it would likely have to be widget-by-widget. However, if there's an underlying framework in place for it, I'm sure folks like myself with less experience could contribute.
Thanks all for the great work!
Other
No response
Beta Was this translation helpful? Give feedback.
All reactions