dave14305
Part of the Furniture
With the upcoming breaking changes for addons with Web UI pages using Chart.js, some choices need to be made.
I've opted for an "almost-do-nothing" approach. For FlexQoS, I will no longer rely on the chart.min.js provided by the firmware, but will instead load chart.min.js from one of the CDNs (e.g. jsDelivr).
This will let me keep supporting the same addon code across 3 different firmware branches (386, 388, 102). And since FlexQoS works the best on 386, so-so on 388, and not at all on 102 (A.QoS currently broken), I'm not in a rush to abandon the users on older models.
Jack Yaz was smart and bundled his own chart.js into his addons from the start. And did the same for Adam’s Skynet GUI.
Thoughts, comments, advice welcome.
I've opted for an "almost-do-nothing" approach. For FlexQoS, I will no longer rely on the chart.min.js provided by the firmware, but will instead load chart.min.js from one of the CDNs (e.g. jsDelivr).
Git:
-<script type="text/javascript" src="/js/chart.min.js"></script>
+<script type="text/javascript" src="https://cdn.jsdelivr.net/npm/chart.js@2.9.4/dist/Chart.min.js" integrity="sha256-t9UJPrESBeG2ojKTIcFLPGF7nHi2vEc7f5A2KpH/UBU=" crossorigin="anonymous"></script>
This will let me keep supporting the same addon code across 3 different firmware branches (386, 388, 102). And since FlexQoS works the best on 386, so-so on 388, and not at all on 102 (A.QoS currently broken), I'm not in a rush to abandon the users on older models.
Jack Yaz was smart and bundled his own chart.js into his addons from the start. And did the same for Adam’s Skynet GUI.
Thoughts, comments, advice welcome.
Last edited: