Customising the local dashboard
Posted: Tue 20 Oct 2020 7:27 pm
A couple of questions on customising the local dashboard (index.html) if anyone has played with this:
Is there any simple way of using webtags to access data for the dashboard, even something obvious like the location to put in a header? Or would some extra JS be necessary to make eg an HTTP POST/GET call?
Is there a listing anywhere of the data that's returned from the dashboard's websocket call for the latest live data? Or should I assume that all available data items are maybe already effectively listed in the conversion to realtimeGauges.txt? (Appreciating that the two things are not necessarily the same but just wondering if there's a parallel.)
If anyone's interested, I have a dashboard index.html converted to use CSS Grid for layout of the blocks rather than than Bootstrap/Flexbox - it effectively uses named blocks and makes it easier to use different layouts with different media queries, even changing the order of the blocks or adding/omitting them if you wish at different viewport sizes. But it's just a 'first draft' at present - it does basically work OK but several rough edges as yet I'll keep working.
Finally, one curiosity: CMX seems to use a separate stored version of the dashboard when it starts up AFAICS. Needs a click to another menu page and click back to dashboard before any new index.html is read. What's that all about?
Is there any simple way of using webtags to access data for the dashboard, even something obvious like the location to put in a header? Or would some extra JS be necessary to make eg an HTTP POST/GET call?
Is there a listing anywhere of the data that's returned from the dashboard's websocket call for the latest live data? Or should I assume that all available data items are maybe already effectively listed in the conversion to realtimeGauges.txt? (Appreciating that the two things are not necessarily the same but just wondering if there's a parallel.)
If anyone's interested, I have a dashboard index.html converted to use CSS Grid for layout of the blocks rather than than Bootstrap/Flexbox - it effectively uses named blocks and makes it easier to use different layouts with different media queries, even changing the order of the blocks or adding/omitting them if you wish at different viewport sizes. But it's just a 'first draft' at present - it does basically work OK but several rough edges as yet I'll keep working.
Finally, one curiosity: CMX seems to use a separate stored version of the dashboard when it starts up AFAICS. Needs a click to another menu page and click back to dashboard before any new index.html is read. What's that all about?