This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |
| indigo_2022.1_documentation:plugin_guide [2025/04/14 20:10] – external edit 127.0.0.1 | indigo_2022.1_documentation:plugin_guide [2025/10/23 23:09] (current) – [Custom HTML Config Dialogs] davel17 |
|---|
| === Custom HTML Config Dialogs === | === Custom HTML Config Dialogs === |
| |
| You can also implement your own custom configuration in HTML if you prefer. Rather than adding lots of //''<Field>''// definitions, you simply specify a //''<URL>''// element. The URL specified can either be a fully specified URL (%%protocol://host/path%%) or it may be a relative URL (/some/relative/path). If it's the later then Indigo will attempt to guess the [[indigo_2022.1_documentation:server_commands&#get_web_server_url|best base URL]]. You would then handle those form requests using [[#processing_http_requests_in_your_plugin|the built-in request handling mechanism discussed below]]. See the **Example HTTP Responder** plugin in the [[https://github.com/IndigoDomotics/IndigoSDK/releases/tag/v2022.1|SDK]] for an example. | You can also implement your own custom configuration in HTML if you prefer. Rather than adding lots of //''<Field>''// definitions, you simply specify a //''<URL>''// element. The URL specified can either be a fully specified URL <nowiki>(%%protocol://host/path%%)</nowiki> or it may be a relative URL (/some/relative/path). If it's the later then Indigo will attempt to guess the [[indigo_2022.1_documentation:server_commands&#get_web_server_url|best base URL]]. You would then handle those form requests using [[#processing_http_requests_in_your_plugin|the built-in request handling mechanism discussed below]]. See the **Example HTTP Responder** plugin in the [[https://github.com/IndigoDomotics/IndigoSDK/releases/tag/v2022.1|SDK]] for an example. |
| ==== Devices.xml ==== | ==== Devices.xml ==== |
| |