@seth350, lots of issues. That is your disadvantage now, when doing pioneer work ...
Ah yes, the widget API is only recently added to dashboard version 2.10.0. Would be good if you could add that to the readme page, in the installation section.
Well seems you have already analysed it very well.
Seems indeed that you need to specify (in your raw html section in your js file) a dynamic id, similar to the gauge node:
<div id="gauge_{{$id}}" ...
Not sure at the moment where the $id is coming from, and if you have to specifiy it somewhere
[EXTRA] Another thing that might be usefull is theming support. When you look e.g. at the gauge-node, they get the settings of the current theme and display the gauge in those colors (if available):
var theme = ui.getTheme();
if (theme === undefined) {
theme = {"group-textColor":{value:"#000"}};
theme["widget-textColor"] = {value:"#000"};
theme["widget-backgroundColor"] = {value:'#1784be'};
}
var gageoptions = {};
gageoptions.lineWidth = {'theme-dark':0.75};
gageoptions.pointerOptions = {'theme-dark':{color:'#8e8e93'}, 'theme-custom':theme["group-textColor"].value};
gageoptions.backgroundColor = {'theme-dark':'#515151', 'theme-custom':theme["widget-textColor"].value };
gageoptions.compassColor = {'theme-dark':'#0b8489', 'theme-light':'#1784be', 'theme-custom':theme["widget-backgroundColor"].value};
@dceejay : I'm not sure whether every widget developer needs to add this kind of code, or whether this will/can be applied automatically for all widget nodes by the dashboard???
