¶ (c) Technocore - All Rights Reserved.
NOTICE: All information contained herein is, and remains
the property of TechnoCore.
The intellectual and technical concepts contained
herein are proprietary to TechnoCore and dissemination of this information or reproduction of this material
is strictly forbidden unless prior written permission is obtained
from TechnoCore.
¶ ObjTextGauge
The ObjTextGauge object is responsible for rendering a client-side gauge chart. It replaces the deprecated Google Image Charts API with the modern, animated JustGage.js library.
The object generates the necessary HTML and JavaScript to create a responsive SVG-based gauge.
¶ Methods
¶ Process(Param1: str, Param2: str, Param3: str, ...)
This method takes the parameters needed to configure and render the gauge.
Parameters:
Param1(str): The numerical value to display on the gauge. Defaults to0.Param2(str): The title or label to display above the gauge. Defaults to an empty string.Param3(str): The maximum value of the gauge. Defaults to100.
Returns:
- (str): A string of HTML and JavaScript code that will render the gauge on the web page.
Example Usage:
gauge = ObjProcessText()
# Create a gauge with a value of 75, a title of "CPU Usage", and a max value of 100
gauge_html = gauge.Process(param1="75", param2="CPU Usage", param3="100")
print(gauge_html)
This will output the necessary code to render a gauge like this:
(Image from justgage.com)
¶ Markup
The container lives in ObjTextGauge.yaml under templates:, the
initialiser under js:, both using %%NAME%% placeholders rather
than .format() fields — the JS body is mostly braces.
The container carries its dimensions inline rather than as a class
because JustGage sizes the dial at construction; a stylesheet
arriving later would not resize it. The two CDN scripts are named as
module constants, and the order is load-bearing: JustGage reads the
Raphael global when it constructs.
¶ Known injection
Carried over verbatim from the inline markup, so that lifting it did
not quietly change rendered output. Tagged FIXME in both the source
and the YAML:
- The title lands inside a single-quoted JS string unescaped, so
a title containing an apostrophe closes the string and anything
after it is executed. - value and max land as bare JS numerics with no cast, so a
non-numeric parameter is a syntax error at best.
Fixing either changes rendered output and belongs in its own change
with its own verification.