Switch to full chart API Add workaround required to used typed JS interop in 1.13 It could be cool …

Switch to full chart API Add workaround required to used typed JS interop in 1.13 It could be cool to show more of the API in the sample now that there is a pretty full definition of it.

BUG=

[jacobr, 2015-11-18 07:23:43]

Kevin, if this looks good please

git cl patch
and commit.

This is the autogenerated api for charted. With a stupid workaround for the JS
interop crasher that took me way too long to figure out.
Sra, any idea why this workaround works and what we can do to avoid it?
The workaround is ugly but I think it is ok for 1.13 but I'll buy a beer for
someone who figures out a simple fix so the workaround can go away.

https://codereview.appspot.com/276070043/diff/1/example/example.dart
File example/example.dart (right):

https://codereview.appspot.com/276070043/diff/1/example/example.dart#newcode23
example/example.dart:23: // state.
siggi, sra, why is this required? We get really strange resolution queue related
crashes in dart2js without this line. Perhaps without a JS API referencing
something with type dynamic, we never resolve enough types early enough?
In all my tests I think I got lazy and had something be dynamic and so it was
fine. The issue only triggers when you have methods in your API that return
List<SomeSpecificType>... odd.

https://codereview.appspot.com/276070043/diff/1/example/example.dart#newcode75
example/example.dart:75: new Chart(ctx).Line(data, new
LineChartOptions(pointDotRadius: 10));
responsive doesn't seem like it is a valid option... at least according to the
d.ts file... or maybe I have a bug.

[kevmoo (at google), 2015-12-17 18:30:20]

I repackaged this w/ the recent fixes - https://github.com/google/chartjs.dart/

Cool!