[sheriff-o-matic]: Basic trooper display for sheriff-o-matic.

Tools/GardeningServer/sheriff-o-matic.html

Index: Tools/GardeningServer/sheriff-o-matic.html
diff --git a/Tools/GardeningServer/sheriff-o-matic.html b/Tools/GardeningServer/sheriff-o-matic.html
index 08bf1a39520793a960166d02dd21264c6c4db998..f3a090d4924b02f5f3ca60ef4cf4ee74775c6a8d 100644
--- a/Tools/GardeningServer/sheriff-o-matic.html
+++ b/Tools/GardeningServer/sheriff-o-matic.html
@@ -22,6 +22,10 @@ body {
   margin: 0px;
 }
 </style>
+<script src='//www.google.com/jsapi'></script>

[ojan, 2014/09/04 02:58:43]

I'd rather we not include script tags at all. We use html imports everywhere so
that the component that actually draws the chart imports it and we can use
include-what-you-use style importing.

Also, if we're going to include a charting library, I'd rather we include
something more modern and maintained like http://www.chartjs.org/. But, I don't
want to block you landing this patch on that...so, if you don't want to do that,
can you make a ct-chart component and use that? Then the ct-chart component can
have a FIXME to move to chartjs and nothing outside the component would know
about this library. I just don't want us building a whole set of other charts
and stuff on this library, so hopefully a FIXME will be enough to dissuade
people.

[shans, 2014/09/05 00:08:19]

I actually tried that initially, but it seems that the google loading mechanism
doesn't play very nicely with HTML Imports and Polymer elements.
OK, switched to chartjsnew (which is chartjs enhanced with some of the extra
features that google charts provides).

+<script>
+google.load("visualization", "1", {packages: ["corechart"]});
+</script>
 <script src="bower_components/platform/platform.js"></script>
 <link rel="import" href="bower_components/polymer/polymer.html">
 <link rel="import" href="ui/ct-sheriff-o-matic.html">