The other reply to my post, that is developer-oriented, (and my reply to that post as it was addressed to me) should be ignored by you and other readers.
NeilThomas wrote: ↑Sun 16 Oct 2022 10:21 am
If I miss changes to other aspects of the js files then the changes should be able to be simply copied across. I am not a developer, have never been one however, if you find bits I have missed then just let me know.
It is because I appreciate you are not a developer that I included those few introductory words indicating tracking MX development was not always easy. The rest of my earlier post was indeed simply indicating a few bits that you had missed, where the changes can indeed be simply copied across as mentioned in the quote from you included above.
The two posts I linked to previously, simply contain zips that have the files that have changed, and nothing more.
I suspect a good proportion of those who use your alternative interface, could look at the JavaScript files that are part of standard interface in the first linked post, could find the files with same names within your alternative interface, see which lines do match, and easily add the additional "editable" lines. These additional lines vary their content between the different script files, but in the
thisyearrecseditor.js file, the 2 extra lines have the simplest content:
Code: Select all
$('#highRain24hVal').editable();
$('#highRain24hTime').editable();
In the case of the second post I linked to, it is again a simple case of making two bits of code match in two locations, but Mark embedded that bit of script in his HTML, you have (as mentioned in your "Readme" file) moved the embedded code out into a separate file. There is one block of several lines of code to replace in this case, it starts with the line that mentions "ajax".
There is another bit missing in the alarm section of the alternative dashboard. I deliberately did not mention it before because adding this missing bit is not a simple copy of code from one file to another. Anybody who wants to add this extra alarm to your dashboard
index.html file, does not need to be a developer, does not even need to understand HTML coding, but does have to appreciate that the various "div" clauses in the standard and alternative interfaces are formatted differently, and that in the alternative interface file, all the subsequent alarms need order renumbering.
The 3.19.3 rewrite of MX added this one line of code to
index.html in the standard interface:
Code: Select all
<div style="display:inline-block"><span class="indicator" id="AlarmIsRaining"></span> Is raining</div>
Next comes part of code needed in alternative interface (here I have used a different shape for the extra alarm indicator), I have not included the subsequent lines that will also need renumbering:
Code: Select all
<div class="led-block" style="order:4;"><div class="led obelisk" id="AlarmRain"></div>High Rainfall</div>
<div class="led-block" style="order:5;"><div class="led lozenge" id="AlarmIsRaining"></div>Non-zero rainfall rate</div>
<div class="led-block" style="order:6;"><div class="led obelisk" id="AlarmRainRate"></div>High Rain Rate</div>
