The purpose of this package is to provide various extensions to the Plotly Dash framework. It can be divided into five main blocks,
- The
snippetsmodule, which contains a collection of utility functions - The
javascriptmodule, which contains functionality to ease the interplay between Dash and JavaScript - The
enrichmodule, which contains various enriched versions of Dash components - The
multipagemodule, which contains utilities for multi page apps - A number of custom components, e.g. the
Downloadcomponent
While the snippets module documentation will be limited to source code comments, the javascript module, the enrich module, the multipage module, and the custom components are documented below.
In Dash, component properties must be JSON serializable. However, many React components take JavaScript functions (or objects) as inputs, which can make it tedious to write Dash wrappers. To ease the process, dash-extensions implements a simple bridge for passing function handles (and other variables) as component properties. The javascript module is the Python side of the bridge, while the dash-extensions package on npm forms the JavaScript side.
In the examples below, we will consider the GeoJSON component in dash-leaflet==0.1.10. The complete example apps are available in the dash-leaflet documentation.
Any JavaScript variable defined in the (global) window object can passed as a component property. Hence, if we create a .js file in the assets folder with the following content,
window.myNamespace = Object.assign({}, window.myNamespace, {
mySubNamespace: {
pointToLayer: function(feature, latlng, context) {
return L.circleMarker(latlng)
}
}
});
the pointToLayer function of the myNamespace.mySubNamespace namespace can now be used as a component property,
import dash_leaflet as dl
from dash_extensions.javascript import Namespace
...
ns = Namespace("myNamespace", "mySubNamespace")
geojson = dl.GeoJSON(data=data, options=dict(pointToLayer=ns("pointToLayer")))
Note that this approach is not limited to function handles, but can be applied for any data type.
The assign function of the javascript module provides a more compact syntax where the JavaScript code is written as a string directly in the Python file. The previous example is thus reduced to,
import dash_leaflet as dl
from dash_extensions.javascript import assign
...
point_to_layer = assign("function(feature, latlng, context) {return L.circleMarker(latlng);}")
geojson = dl.GeoJSON(data=data, options=dict(pointToLayer=point_to_layer))
without the need for creating any .js files manually. The syntax is particularly well suited for small JavaScript code snippets and/or examples. Note that under the hood, the inline functions are transpiled into a .js file, which is written to the assets folder.
In some cases, it might be sufficient to wrap an object as an arrow function, i.e. a function that just returns the (constant) object. This behaviour can be achieved with the following syntax,
import dash_leaflet as dl
from dash_extensions.javascript import arrow_function
...
geojson = dl.GeoJSON(hoverStyle=arrow_function(dict(weight=5, color='#666', dashArray='')), ...)
The enrich module provides a number of enrichments of the Dash object that can be enabled in a modular fashion. To get started, replace the Dash object by a DashProxy object and pass the desired transformations via the transforms keyword argument,
from enrich import DashProxy, TriggerTransform, MultiplexerTransform, ServersideOutputTransform, NoOutputTransform
app = DashProxy(transforms=[
TriggerTransform(), # enable use of Trigger objects
MultiplexerTransform(), # makes it possible to target an output multiple times in callbacks
ServersideOutputTransform(), # enable use of ServersideOutput objects
NoOutputTransform(), # enable callbacks without output
])
The enrich module also exposes a Dash object, which is a DashProxy object with all transformations loaded, i.e. a batteries included approach. However, it is recommended to load only the transforms are that actually used.
Makes it possible to use the Trigger component. Like an Input, it can trigger callbacks, but its value is not passed on to the callback,
@app.callback(Output("output_id", "output_prop"), Trigger("button", "n_clicks"))
def func(): # note that "n_clicks" is not included as an argument
Makes it possible to target an output by multiple callbacks, i.e enabling code like
@app.callback(Output("log", "children"), Input("left", "n_clicks"))
def left(_):
return "left"
@app.callback(Output("log", "children"), Input("right", "n_clicks"))
def right(_):
return "right"
Under the hood, when n > 1 callbacks target the same element as output, n Store elements are created, and the callbacks are redirect to target these intermediate outputs. Finally, a callback is added with the intermediate outputs as inputs and the original output as output. The strategy was contributed by dwelch91.
Since the MultiplexerTransform modifies the original callback to target a proxy component, wrappers (such as the Loading component) targeting the original output will not work as intended. If the output is static (i.e. not recreated by callbacks), the issue can avoided by injecting the proxy component next to the original output in the component tree,
app = DashProxy(transforms=[MultiplexerTransform(proxy_location="inplace")])
If the output is not static, the recommended mitigation strategy is not to wrap to original ouput object, but to instead pass the wrapper(s) as proxy component wrappers,
proxy_wrapper_map = {Output("log0", "children"): lambda proxy: dcc.Loading(proxy, type="dot")}
app = DashProxy(transforms=[MultiplexerTransform(proxy_wrapper_map)])
The MultiplexerTransform does not support the MATCH and ALLSMALLER wildcards.
Makes it possible to use the ServersideOutput component. It works like a normal Output, but keeps the data on the server. By skipping the data transfer between server/client, the network overhead is reduced drastically, and the serialization to JSON can be avoided. Hence, you can now return complex objects, such as a pandas data frame, directly,
@app.callback(ServersideOutput("store", "data"), Input("left", "n_clicks"))
def query(_):
return pd.DataFrame(data=list(range(10)), columns=["value"])
@app.callback(Output("log", "children"), Input("store", "data"))
def right(df):
return df["value"].mean()
The reduced network overhead along with the avoided serialization to/from JSON can yield significant performance improvements, in particular for large data. Note that content of a ServersideOutput cannot be accessed by clientside callbacks.
In addition, a new memoize keyword makes it possible to memoize the output of a callback. That is, the callback output is cached, and the cached result is returned when the same inputs occur again.
@app.callback(ServersideOutput("store", "data"), Input("left", "n_clicks"), memoize=True)
def query(_):
return pd.DataFrame(data=list(range(10)), columns=["value"])
Used with a normal Output, this keyword is essentially equivalent to the @flask_caching.memoize decorator. For a ServersideOutput, the backend to do server side storage will also be used for memoization. Hence, you avoid saving each object two times, which would happen if the @flask_caching.memoize decorator was used with a ServersideOutput.
Makes it possible to write callbacks without an Output,
@app.callback(Input("button", "n_clicks")) # note that the callback has no output
Under the hood, a (hidden) dummy Output element is assigned and added to the app layout.
The multipage module makes it easy to create multipage apps. Pages can be constructed explicitly with the following syntax,
page = Page(id="page", label="A page", layout=layout, callbacks=callbacks)
where the layout function returns the page layout and the callbacks function registers any callbacks. Per default, all component ids are prefixed by the page id to avoid id collisions. It is also possible to construct a page from a module,
page = module_to_page(module, id="module", label="A module")
if the module implements the layout and callbacks functions. Finally, any app constructed using a DashProxy object can be turned into a page,
page = app_to_page(app, id="app", label="An app")
Once the pages have been constructed, they can be passed to a PageCollection object, which takes care of navigation. Hence a multipage app with a simple menu would be something like,
# Create pages.
pc = PageCollection(pages=[
Page(id="page", label="A page", layout=layout, callbacks=callbacks),
...
])
# Create app.
app = DashProxy(suppress_callback_exceptions=True)
app.layout = html.Div(simple_menu(pc) + [html.Div(id=CONTENT_ID), dcc.Location(id=URL_ID)])
# Register callbacks.
pc.navigation(app)
pc.callbacks(app)
The complete example is available in the examples folder.
The dataiku module provides a few utility functions to ease the integration of Dash apps in dataiku 8.x (from 9.0, an official Dash integration is provided). To get started, create a standard web app. Make sure that the selected code environment (can be configured in the Settings tab) has the following packages installed,
dash==1.18.1
dash-extensions==0.0.44
Replace the content of the HTML tab with
<head>
<script type="text/javascript" src="https://cdn.jsdelivr.net/gh/thedirtyfew/[email protected]/snippets/dataiku.js"></script>
</head>
and clear the JS and CSS tabs (unless you the JS/CSS code). Finally, go to the Python tab and replace the content with
import dash
import dash_html_components as html
from dash_extensions.dataiku import setup_dataiku
# Path for storing app configuration (must be writeable).
config_path = os.path.join(os.path.dirname(os.path.realpath(__file__)), "config.json")
# Create a small example app.
dash_app = dash.Dash(__name__, **setup_dataiku(app, config_path))
dash_app.layout = html.Div("Hello from Dash!")
After clicking save, you should see the text Hello from Dash! in the preview window (a backend restart might be required). Congratulations! You have created you first Dash app in dataiku.
The components listed here can be used in the layout of your Dash app.
The WebSocket component enables communication via websockets in Dash. Simply add the WebSocket component to the layout and set the url property to the websocket endpoint. Messages can be send by writing to the send property, and received messages are written to the message property. Here is a small example,
import dash_core_components as dcc
import dash_html_components as html
from dash import Dash
from dash.dependencies import Input, Output
from dash_extensions import WebSocket
# Create example app.
app = Dash(prevent_initial_callbacks=True)
app.layout = html.Div([
dcc.Input(id="input", autoComplete="off"), html.Div(id="message"),
WebSocket(url="wss://echo.websocket.org", id="ws")
])
@app.callback(Output("ws", "send"), [Input("input", "value")])
def send(value):
return value
@app.callback(Output("message", "children"), [Input("ws", "message")])
def message(e):
return f"Response from websocket: {e['data']}"
if __name__ == '__main__':
app.run_server()
Websockets make it possible to solve a number of cases, which can otherwise be challenging in Dash, e.g.
- Updating client content without server interaction
- Pushing updates from the server to the client(s)
- Running long processes asynchronously
Examples can be found in the examples folder.
The Download component provides an easy way to download data from a Dash application. Simply add the Download component to the app layout, and add a callback which targets its data property. Here is a small example,
import dash
import dash_html_components as html
from dash.dependencies import Output, Input
from dash_extensions import Download
app = dash.Dash(prevent_initial_callbacks=True)
app.layout = html.Div([html.Button("Download", id="btn"), Download(id="download")])
@app.callback(Output("download", "data"), [Input("btn", "n_clicks")])
def func(n_clicks):
return dict(content="Hello world!", filename="hello.txt")
if __name__ == '__main__':
app.run_server()
To ease downloading files, a send_file utility method is included,
import dash
import dash_html_components as html
from dash.dependencies import Output, Input
from dash_extensions import Download
from dash_extensions.snippets import send_file
app = dash.Dash(prevent_initial_callbacks=True)
app.layout = html.Div([html.Button("Download", id="btn"), Download(id="download")])
@app.callback(Output("download", "data"), [Input("btn", "n_clicks")])
def func(n_clicks):
return send_file("/home/emher/Documents/Untitled.png")
if __name__ == '__main__':
app.run_server()
To ease downloading data frames (which seems to be a common use case for Dash users), a send_data_frame utility method is also included,
import dash
import pandas as pd
import dash_html_components as html
from dash.dependencies import Output, Input
from dash_extensions import Download
from dash_extensions.snippets import send_data_frame
# Example data.
df = pd.DataFrame({'a': [1, 2, 3, 4], 'b': [2, 1, 5, 6], 'c': ['x', 'x', 'y', 'y']})
# Create example app.
app = dash.Dash(prevent_initial_callbacks=True)
app.layout = html.Div([html.Button("Download", id="btn"), Download(id="download")])
@app.callback(Output("download", "data"), [Input("btn", "n_clicks")])
def func(n_nlicks):
return send_data_frame(df.to_excel, "mydf.xls")
if __name__ == '__main__':
app.run_server()
Finally, a send_bytes utility method is included to make it easy to download in-memory objects that support writing to BytesIO. Typical use cases are excel files,
import dash
import dash_html_components as html
import numpy as np
import pandas as pd
from dash.dependencies import Output, Input
from dash_extensions import Download
from dash_extensions.snippets import send_bytes
# Example data.
data = np.column_stack((np.arange(10), np.arange(10) * 2))
df = pd.DataFrame(columns=["a column", "another column"], data=data)
# Create example app.
app = dash.Dash(prevent_initial_callbacks=True)
app.layout = html.Div([html.Button("Download xlsx", id="btn"), Download(id="download")])
@app.callback(Output("download", "data"), [Input("btn", "n_clicks")])
def generate_xlsx(n_nlicks):
def to_xlsx(bytes_io):
xslx_writer = pd.ExcelWriter(bytes_io, engine="xlsxwriter")
df.to_excel(xslx_writer, index=False, sheet_name="sheet1")
xslx_writer.save()
return send_bytes(to_xlsx, "some_name.xlsx")
if __name__ == '__main__':
app.run_server()
and figure objects,
import dash
import dash_html_components as html
import plotly.graph_objects as go
from dash.dependencies import Input, Output
from dash_extensions import Download
from dash_extensions.snippets import send_bytes
app = dash.Dash()
app.layout = html.Div([html.Button("Download", id="btn"), Download(id="download")])
@app.callback(Output("download", "data"), [Input("btn", "n_clicks")])
def download(n_clicks):
f = go.Figure()
return send_bytes(f.write_image, "figure.png")
if __name__ == '__main__':
app.run_server()
The BeforeAfter component is a light wrapper of react-before-after-slider, which makes it possible to highlight differences between two images. Here is a small example,
import dash_html_components as html
from dash import Dash
from dash_extensions import BeforeAfter
app = Dash()
app.layout = html.Div([
BeforeAfter(before="assets/lena_bw.png", after="assets/lena_color.png", width=512, height=512)
])
if __name__ == '__main__':
app.run_server()
The Ticker component is a light wrapper of react-ticker, which makes it easy to show moving text. Here is a small example,
import dash
import dash_html_components as html
from dash_extensions import Ticker
app = dash.Dash(__name__)
app.layout = html.Div(Ticker([html.Div("Some text")], direction="toRight"))
if __name__ == '__main__':
app.run_server()
The Lottie component makes it possible to run Lottie animations in Dash. Here is a small example,
import dash
import dash_html_components as html
import dash_extensions as de
# Setup options.
url = "https://assets9.lottiefiles.com/packages/lf20_YXD37q.json"
options = dict(loop=True, autoplay=True, rendererSettings=dict(preserveAspectRatio='xMidYMid slice'))
# Create example app.
app = dash.Dash(__name__)
app.layout = html.Div(de.Lottie(options=options, width="25%", height="25%", url=url))
if __name__ == '__main__':
app.run_server()
The Burger component is a light wrapper of react-burger-menu, which enables cool interactive burger menus. Here is a small example,
import dash_html_components as html
from dash import Dash
from dash_extensions import Burger
def link_element(icon, text):
return html.A(children=[html.I(className=icon), html.Span(text)], href=f"/{text}",
className="bm-item", style={"display": "block"})
# Example CSS from the original demo.
external_css = [
"https://negomi.github.io/react-burger-menu/example.css",
"https://negomi.github.io/react-burger-menu/normalize.css",
"https://negomi.github.io/react-burger-menu/fonts/font-awesome-4.2.0/css/font-awesome.min.css"
]
# Create example app.
app = Dash(external_stylesheets=external_css)
app.layout = html.Div([
Burger(children=[
html.Nav(children=[
link_element("fa fa-fw fa-star-o", "Favorites"),
link_element("fa fa-fw fa-bell-o", "Alerts"),
link_element("fa fa-fw fa-envelope-o", "Messages"),
link_element("fa fa-fw fa-comment-o", "Comments"),
link_element("fa fa-fw fa-bar-chart-o", "Analytics"),
link_element("fa fa-fw fa-newspaper-o", "Reading List")
], className="bm-item-list", style={"height": "100%"})
], id="slide"),
html.Main("Hello world!", style={"width": "100%", "height": "100vh"}, id="main")
], id="outer-container", style={"height": "100%"})
if __name__ == '__main__':
app.run_server()
The Keyboard component makes it possible to capture keyboard events at the document level. Here is a small example,
import dash
import dash_html_components as html
import json
from dash.dependencies import Output, Input
from dash_extensions import Keyboard
app = dash.Dash()
app.layout = html.Div([Keyboard(id="keyboard"), html.Div(id="output")])
@app.callback(
Output("output", "children"),
[Input("keyboard", "n_keydowns")],
[State("keyboard", "keydown")],
)
def keydown(n_keydowns, event):
return json.dumps(event)
if __name__ == '__main__':
app.run_server()
The Monitor component makes it possible to monitor the state of child components. The most typical use case for this component is bi-directional synchronization of component properties. Here is a small example,
import dash_core_components as dcc
import dash_html_components as html
from dash import Dash, no_update
from dash.dependencies import Input, Output
from dash.exceptions import PreventUpdate
from dash_extensions import Monitor
app = Dash()
app.layout = html.Div(Monitor([
dcc.Input(id="deg-fahrenheit", autoComplete="off", type="number"),
dcc.Input(id="deg-celsius", autoComplete="off", type="number")],
probes=dict(deg=[dict(id="deg-fahrenheit", prop="value"),
dict(id="deg-celsius", prop="value")]), id="monitor")
)
@app.callback([Output("deg-fahrenheit", "value"), Output("deg-celsius", "value")],
[Input("monitor", "data")])
def sync_inputs(data):
# Get value and trigger id from monitor.
try:
probe = data["deg"]
trigger_id, value = probe["trigger"]["id"], float(probe["value"])
except (TypeError, KeyError):
raise PreventUpdate
# Do the appropriate update.
if trigger_id == "deg-fahrenheit":
return no_update, (value - 32) * 5 / 9
elif trigger_id == "deg-celsius":
return value * 9 / 5 + 32, no_update
if __name__ == '__main__':
app.run_server(debug=False)