Refactor dashboard architecture to remove dashboardReady binding

[Brian Lewis]

in the very beginning, dashboardReady was intended to convey that the dashboard had accessed it crossfilter and created all the dimensions and groups etc , as well as other datadriven artefacts, that it could provide.

In future we’ll rely on dashboard binding to do this:

1. each dashboard will have a property public dashboard
2. When the dashboard finishes its setup, instead of setting dashboardReady, it will set dashboard as a refernce to itself:
3. this.dashboard = this;

Child components can then bind like this

<child dashboard=”vm.dashboard”

The point being that when dashboard is available, it is guaranteed to be configured. This may offer the cleanest solution to the asynnc data fetches as in schooldashboard??

‌