Files
espurna/code/html/src/panel-rfm69-mapping.html
Maxim Prokhorov 289fea4f3d webui: separate sources per module
* migrate to esbuild from terser, since now js source needs bundling
* (temporary?) hijack inline-source object handling to inline html files
* get rid of legacy removeIf comments in source in favour of explicit
  removal either through bundling tree-shaking and / or manual module-*
  class element removal w/ jsdom
* get rid of multi-layered custom checkboxes in favour of
  `appearance: none` directly styling the `input` elem
  also removes scripting part that was supposed to adjust for=... labels
* update to html-minifier-terser, up-to-date html-minifier fork
* update to iro.js 5.5.x, using npm to manage dependencies
* build script can now update resulting html output
  (called after bundling stage, before minification)
2024-06-22 19:49:59 +03:00

34 lines
1.3 KiB
HTML

<form id="form-rfm69-mapping" class="pure-form form-settings">
<div class="panel" id="panel-rfm69-mapping">
<div class="header">
<h1>MAPPING</h1>
<h2>
Configure the map between nodeID/key and MQTT topic. Messages from the given nodeID with the given key will be forwarded to the specified topic.
You can also configure a default topic using {nodeid} and {key} as placeholders, if the default topic is empty messages without defined map will be discarded.
</h2>
</div>
<div class="page">
<fieldset>
<legend>Default topic</legend>
<div class="pure-control-group">
<input name="rfm69Topic" type="text" value="" size="8">
<span class="pure-form-message">
Default MQTT Topic. Available placeholders: {nodeid} and {key}
</span>
</div>
</fieldset>
<fieldset>
<legend>Specific topics</legend>
<div id="rfm69-mapping" class="settings-group">
</div>
<button type="button" class="pure-button button-add-settings-group" data-settings-group="rfm69-mapping">Add</button>
</fieldset>
</div>
</div>
</form>