Expose plotly dash apps as Django tags. Multiple Dash apps can then be embedded into a single web page, persist and share internal state, and also have access to the current user and session variables.
See the source for this project here: https://github.com/GibbsConsulting/django-plotly-dash
This README file provides a short guide to installing and using the package, and also outlines how to run the demonstration application.
More detailed information can be found in the online documentation at https://readthedocs.org/projects/django-plotly-dash
An online version of the demo can be found at https://djangoplotlydash.com
First, install the package. This will also install plotly and some dash packages if they are not already present.
pip install django_plotly_dash
Then, add django_plotly_dash
to INSTALLED_APPS
in your Django settings.py
file
INSTALLED_APPS = [
...
'django_plotly_dash.apps.DjangoPlotlyDashConfig',
...
]
The application's routes need to be registered within the routing structure by an appropriate include
statement in
a urls.py
file. Note: django_plotly_dash
is not a name of your application, it is referring to the inner namespace of this library. Please do not skip this step:
urlpatterns = [
...
path('django_plotly_dash/', include('django_plotly_dash.urls')),
]
The name within the URL is not important and can be changed.
For the final installation step, a migration is needed to update the database:
./manage.py migrate
The use of frames within
HTML documents has to be enabled by adding to the settings.py
file:
X_FRAME_OPTIONS = 'SAMEORIGIN'
Further configuration, including live updating to share application state, is described in the online documentation.
The source repository contains a demo application. To clone the repo and lauch the demo:
git clone https://github.com/GibbsConsulting/django-plotly-dash.git
cd django-plotly-dash
./make_env # sets up a virtual environment for development
# with direct use of the source code for the package
./prepare_redis # downloads a redis docker container
# and launches it with default settings
# *THIS STEP IS OPTIONAL*
./prepare_demo # prepares and launches the demo
# using the Django debug server at http://localhost:8000
To use existing dash applications, first register them using the DjangoDash
class. This
replaces the Dash
class of the dash
package.
Taking a very simple example inspired by the excellent getting started documentation:
import dash
from dash import dcc, html
from django_plotly_dash import DjangoDash
app = DjangoDash('SimpleExample')
app.layout = html.Div([
dcc.RadioItems(
id='dropdown-color',
options=[{'label': c, 'value': c.lower()} for c in ['Red', 'Green', 'Blue']],
value='red'
),
html.Div(id='output-color'),
dcc.RadioItems(
id='dropdown-size',
options=[{'label': i, 'value': j} for i, j in [('L','large'), ('M','medium'), ('S','small')]],
value='medium'
),
html.Div(id='output-size')
])
@app.callback(
dash.dependencies.Output('output-color', 'children'),
[dash.dependencies.Input('dropdown-color', 'value')])
def callback_color(dropdown_value):
return "The selected color is %s." % dropdown_value
@app.callback(
dash.dependencies.Output('output-size', 'children'),
[dash.dependencies.Input('dropdown-color', 'value'),
dash.dependencies.Input('dropdown-size', 'value')])
def callback_size(dropdown_color, dropdown_size):
return "The chosen T-shirt is a %s %s one." %(dropdown_size,
dropdown_color)
Note that the DjangoDash
constructor requires a name to be specified. This name is then used to identify the dash app in
templates:
{% load plotly_dash %}
{% plotly_app name="SimpleExample" %}
The registration code needs to be in a location
that will be imported into the Django process before any model or template tag attempts to use it. The example Django application
in the demo subdirectory achieves this through an import in the main urls.py
file; any views.py
would also be sufficient.
Whilst this example allows for the direct use of existing Dash
applications, it does not provide for the sharing or updating of
internal state. The online documentation provides details on using these
and other additional features.
The make_env
script sets up the development environment, and pulls in the packages
specified in the dev_requirements.txt
file. The check_code
script invokes the test suite (using pytest
) as well
as invoking pylint
on both the package and the associated demo.