It's not easy to use third-party or proprietary widgets from multiple sources right now. I suggest using a registry using settings.py as this feels like configuration.

dashboard.html can then consult this registry and use that for the list of html templates to include, perhaps in the form of a templatetag or something.

I'm stuck on something which is maybe trivial... have checked the documentation, source code, and the various examples but no luck.

How can I show a different background color with the Number widget?

Would like to show Green if a number = zero, and Red if number > 0.

Thanks for the cool dashboard by the way :-)

This isn't really an issue, but rather a question. I would like to add links inside a widget, but seems I can't do that. I'm guessing the Widgets are readonly...

I see I can add links on the html page for the dashboard, but is there a way I can do this with a widget?

Like the list widget, put in a clickable link?

(I tried adding href to a key,value in data, but no joy.

Thanks for making this awesome project, but I'm having an issue installing and usage....

I've followed the documentation, and I can pull up the built in "demo" dashboard in my project, however the docs don't really explain how to setup an HTML file/view for my own custom dashboard.

I could modify the default dashboard, but that's not what should be done.

I went ahead and created an HTML file, and served it through a view like this:

from django.http import HttpResponse, StreamingHttpResponse from django.shortcuts import render, render_to_response, redirect, RequestContext

view.py: def test_dashboard(request):

context={ }
return render(request,'dashing/dashing.html',context)      

html file: {% extends 'dashing/base.html' %} {% load staticfiles %}

{% block 'stylesheets' %}

{% endblock %}

When I render this, I still get the default dashboard data, even if my dashing-config.js file is empty.

So, my questions are two fold:

1.) How do I setup my own dashboard (not use the built in dashboard) (I've read the example trelio card app, and still can't figure it out)

2.) Once I am rendering my HTML document, how to I point the JS/HTML to retreive data from the widget classes setup?

this should fix #12 and #11 as described in the issues and should fix the issues from the last pull request. I added additions to the documention as well.

It would be nice if I could write a general widget, for example a github repository commit list (I have written this in my fork but it's pretty messy), to use URL parameters to pass configuration options like the repo to watch and the most recent commits.

I can see a case to be made for REST style URLs here (i.e. /widgets/githubcommits/talpor/django-dashing/) or parameterized requests (i.e. /widgets/githubcommits/?user=talpor&repo=django-dashing)

This project is fantastic and has good velocity and I'd be happy to discuss design and implementation of this feature if you like. Have you considered this yourself?

just curious..

I could place code under my project's app/dashing/static/dashing/dashing-config.js

but from dashing import <something> would cause problems when I start to add python codes under app/dashing/

So where do you suggest to place those files?

Graph and List both update on $.extend( this.scope, scope ), however Knob (specifically, scope.value and scope.data.fgColor) does not. (I want a knob that changes its foreground colour based on the value, in the standard "green/yellow/red" scheme.)

For example, the following will update the numerical value displayed (i.e. the one hidden by scope.data.displayInput), but not the arc itself:

dashboard.addWidget( "MyWidget", "Knob", {
    getData: function() {
        var scope = GetWidgetScope();
        $.extend( this.scope, scope );
    }
});

I've been able to work around this by adding these trigger calls to the end of getData, but I'd rather this was handled by the library itself:

$( ".dashing-knob" ).trigger( "change" );           // updates the value
$( ".dashing-knob" ).trigger( "configure", data );  // updates the colour/etc

Hey,

I'm trying to setup this really cool tool. Unfortunatelly I am not able to create my own widgets. I was trying it with the documentation (created own PyPI package with my custom widgets with no success). Is there somebody who has some experience with creating own widgets? Can you share all steps needed?

Also there is a question when I have own widget with python class, how can I pass parameters from js to the python? I want to have one widget to be used with different data passed to python. Is it possible? I didn't find any reasonable example.

Thanks a lot! :-)

I did not get the map widget to work without adding a Google Maps API key to the JS script loading function, hence this PR.

It's implemented using an additional settings key, WIDGET_CONFIGS, to hold the API key, because as I understand it it's not possible to have it in dashing-config.js since the Google Maps javascript has already been loaded earlier in dashing.js. I added a new template tag, widget_configs, similar to the existing styles and scripts tags, since once again I saw no over simpler way to do it.

If you agree with the way this is implemented I'll go about updating the docs as well to explain how the new settings key must be used (it's basically a widget name -> {key, value} dict that ends pushed down as <script> snippets in base.html).

I am a little confused on how to set up my directory when I am trying to develop and test a widget locally. Based on the documentation I have my directory like this in my project:

project/ -----static/ ----------dashing-config.js ----------widgets/ ---------------custom_widget.js ---------------custom_widget.css ---------------custom_widget/ -------------------- custom_widget.html

When I do this and add my custom widget to my INSTALLED_WIDGETS option in my settings.py, I receive a "custom_widget does not exist" error in my web console.

There are small typos in:

• README.rst
• docs/getting-started.rst

Fixes:

• Should read retrieve rather than retrive.
• Should read necessary rather than neccesary.

Semi-automated pull request generated by https://github.com/timgates42/meticulous/blob/master/docs/NOTE.md

Good morning,

I am quite new working in this area, and I am in a project in which I have inherited a code that works with djago-dashing.

We have a panel with four widgets (2 Number type and 2 List type). My question arises because when I click on a widget and drag the widget it changes position with the rest.

Is there any way to fix these widgets and it is not possible to move them with the mouse.

Thank you very much

Bumps django from 1.10 to 2.2.24.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Hi,

I am setting interval: 20000, but it's not works. and seems it's still random fresh data.

var myDashboard = new Dashboard();
myDashboard.addWidget('customWidget', 'Number', {
    getData: function () {
        var self = this;
        Dashing.utils.get('custom_widget', function(data) {
            $.extend(self.scope, data);
        });
    },
    interval: 20000
});

I tried to use django-dashing but realized it's not updated to work with Django 3. I did try to update django-dashing to Django 3, but noted there are more than a handful of modifications to be had:

It appears Django 3 introduces some breaking changes to django-dashing, such as removal of django.utils.six (used in dashing/settings.py), rename of settings.MIDDLEWARE_CLASSES to settings.MIDDLEWARE (used in test/test_app/test_app/settings.py). It appears some of the middlewares used in the test app do not appear to exist with the same name anymore.

Additionally it appears Python 2.7 support was dropped from Django from ~1.1~ 1.11 onwards.

Is there interest in supporting Django 3? Is django-dashing still supporting Python 2? Thanks in advance.