-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Widget and job package manager #18
Comments
I totally agree we should make it easier for the user to quickly populate dashboards with ready-made widgets/jobs. Dashing already does something similar to what you propose (see: https://github.com/Shopify/dashing/blob/master/lib/dashing/cli.rb#L92). Why do you suggest to have different tasks for widget, job installation? |
I suppose there's no need to have different tasks. In theory the implementation would just be to pull a Gist. Group sass and js files into a widget and exs files into a job. If neither a widget, nor a job are found, fail with an exception saying as such. |
Dashing plugin system works fine for widgets / jobs without external dependencies. |
I'm doing some research on how we could incorporate a mechanism like http://docs.operable.io/docs/bundle-configs so that we can have a registry for to showcase their dashboards/widgets and a simple config for someone to declare kitto plugin dependencies. |
I was going to start doing some research tonight on building something out On November 16, 2016 at 1:55:12 PM, Dimitrios Zorbas ( I'm doing some research on how we could incorporate a mechanism like — |
Meanwhile I added a script to help updating the core widgets.
|
Building a package manager to install widgets and jobs would help the process of building a dashboard and get people from idea to app even faster.
The idea is to that someone can create a package which includes both the widget javascript and stylesheet as a Gist or some other package form. Then we could add a Mix task for installing the widget with:
Creating a job would be just as simple:
The text was updated successfully, but these errors were encountered: