Name |
Last commit
|
Last Update |
---|---|---|
sample | ||
src | ||
tasks | ||
.gitignore | ||
.jshintrc | ||
.travis.yml | ||
CHANGELOG.md | ||
CONTRIBUTING.md | ||
Gruntfile.js | ||
LICENSE.md | ||
NOTICE.md | ||
README.md | ||
grafana.sublime-project | ||
latest.json | ||
package.json |
The goal is to split up the situation between the dashboard controller and the current dashboard service. I want to be able to use the routing in order to select various dashboard controllers, so I can extend the current scripting mechanism by implementing new dashboard controllers. However, to do this in a non-insane way, I need to move as much functionality as possible into services, so the individual controllers just need to throw the right set of services together and add a bit of loading logic.
Name |
Last commit
|
Last Update |
---|---|---|
sample | Loading commit data... | |
src | Loading commit data... | |
tasks | Loading commit data... | |
.gitignore | Loading commit data... | |
.jshintrc | Loading commit data... | |
.travis.yml | Loading commit data... | |
CHANGELOG.md | Loading commit data... | |
CONTRIBUTING.md | Loading commit data... | |
Gruntfile.js | Loading commit data... | |
LICENSE.md | Loading commit data... | |
NOTICE.md | Loading commit data... | |
README.md | Loading commit data... | |
grafana.sublime-project | Loading commit data... | |
latest.json | Loading commit data... | |
package.json | Loading commit data... |