2024 Jul 11, 07:39 PM
Here's a screenshot of what I've got now: https://photos.app.goo.gl/U5b5yFgVt1Lw6rFeA
The reason for inserting into a table row instead of the footer is so that the graph naturally lines up with the timeline, despite what kind of width changes the first couple of table rows go through.
Here are some other interesting scenarios that would require full control to modify the interface:
- a "federated view" plugin that displays activity (adds table rows) from other systems in the timeline (display only, no effect on execution.) I have three systems running off a single pump, I have to switch tabs a lot to ensure the programs are mutually exclusive.
- illustrating sunrise/sunset or hourly temperature readings as timeline background colors
- adding new menu items, e.g. a "test mode" interface that provides simpler on-off control and bigger buttons for mobile experiences in the field. This avoids scrolling with wet hands and accidentally leaving the system in manual mode after testing. New feature like this could be developed, tested, and evaluated prior to becoming part of the main program.
- restricting certain features, e.g. disabling manual mode or putting an automatic timeout on it. I've trained myself over the years through losing plants that manual mode is a dangerous way to test stations - now I have other people using the interfaces and starting the same brutal training process.
Are there any existing plugins that could benefit from improve UIs using this feature?
The reason for inserting into a table row instead of the footer is so that the graph naturally lines up with the timeline, despite what kind of width changes the first couple of table rows go through.
Here are some other interesting scenarios that would require full control to modify the interface:
- a "federated view" plugin that displays activity (adds table rows) from other systems in the timeline (display only, no effect on execution.) I have three systems running off a single pump, I have to switch tabs a lot to ensure the programs are mutually exclusive.
- illustrating sunrise/sunset or hourly temperature readings as timeline background colors
- adding new menu items, e.g. a "test mode" interface that provides simpler on-off control and bigger buttons for mobile experiences in the field. This avoids scrolling with wet hands and accidentally leaving the system in manual mode after testing. New feature like this could be developed, tested, and evaluated prior to becoming part of the main program.
- restricting certain features, e.g. disabling manual mode or putting an automatic timeout on it. I've trained myself over the years through losing plants that manual mode is a dangerous way to test stations - now I have other people using the interfaces and starting the same brutal training process.
Are there any existing plugins that could benefit from improve UIs using this feature?