Skip to main content

Finish Line

Finish Line is a framework for quickly building beautiful customizable dashboards in Plotly Dash. The framework provides utility for developers to easily plugin new interactive visualization components into the dashboard. Components are automatically added to the dashboard using a responsive grid layout.

How to use Finish Line

An example use of the framework is located in the GitHub repo under the example directory. The following shows the minimum code required to start a Finish Line dashboard server.

from finishline import FinishLine
import dash

app = dash.Dash()
data = load_my_data()

fl = FinishLine(app=app, data=data)
fl.load_plugins()
app.layout = fl.generate_layout()

if __name__ == '__main__':
    fl.run_server(debug=True, port=5000, host='0.0.0.0')

Visualization components are loaded from the plugins folder. The default location is in a folder called plugins in the current working directory (directory the web server is started). Individual plugins are located in subfolders under the plugins folder. The entry point to a plugin is in the file __init__.py.

Here is an example component. The code is placed in ./plugins/HelloWorld/__init__.py

import dash_html_components as html
import dash_core_components as dcc

def initialize(app, data, fl):

    fl.register_vis(
        'HelloWorld',
        dcc.Graph(
            id='basic-chart',
            figure={
                'data': [
                    {
                        'x': [1, 2, 3, 4],
                        'y': [4, 1, 3, 5],
                        'text': ['a', 'b', 'c', 'd'],
                        'customdata': ['c.a', 'c.b', 'c.c', 'c.d'],
                        'name': 'Trace 1',
                        'mode': 'markers',
                        'marker': {'size': 12}
                        },
                    {
                        'x': [1, 2, 3, 4],
                        'y': [9, 4, 1, 4],
                        'text': ['w', 'x', 'y', 'z'],
                        'customdata': ['c.w', 'c.x', 'c.y', 'c.z'],
                        'name': 'Trace 2',
                        'mode': 'markers',
                        'marker': {'size': 12}
                        }
                    ]
                },
            config={
                'autosizable': True
                }
            )
    )

def finalize(app, data, fl):
    pass

Installation

Finish Line depends upon dash. Note, we have only tested with python3.

Requirements:

  • dash

  • dash-responsive-grid-layout

Install Options

pip3 install finishline

Build

Create distribution

  • edit setup.py and change version number

python3 setup.py sdist bdist_wheel

Install distribution locally

pip3 uninstall finishline
pip3 install dist/finishline-VERSION-py3-none-any.whl

Push to test pip

twine upload --repository-url https://test.pypi.org/legacy/ dist/*VERSION*
pip3 install -U --index-url https://test.pypi.org/simple/ finishline

Push to production pip

twine upload dist/*VERSION*
pip3 install -U finishline

Features

  • Client and server side data store API

  • Plugin visualization component API

  • Responsive grid layout

  • Customizable grid layout via drag and drop

  • Developer mode

To Do List

  • Save layout

  • Reusable components API

  • Hide/Show components

  • Support multiple pages

  • Better support for resizing plotly charts

Metadata

Release files for finishline 0.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for finishline 0.3.0
File Size Uploaded Provenance Actions
finishline-0.3.0.tar.gz 5.7 kB Without provenance Details for finishline-0.3.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for finishline 0.3.0
File Interpreter ABI Platform Actions
finishline-0.3.0-py3-none-any.whl Python 3 none any Details for finishline-0.3.0-py3-none-any.whl

Total release size: 12.2 kB

Release files / finishline-0.3.0.tar.gz

Download URL finishline-0.3.0.tar.gz
Size 5.7 kB
Tags Source
SHA-256 checksum
How to use checksums
46a5eed4e8576cf40f7fe4acecf6c7e659b16182ad72a0735bfc2aa758e4f8ad
BLAKE2b-256 checksum
How to use checksums
cbb64151709bfaba10813ac140767f9405096fd9cf9ece85a4c9ca5d08280497
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.12.1 pkginfo/1.4.2 requests/2.18.4 setuptools/36.2.7 requests-toolbelt/0.8.0 tqdm/4.25.0 CPython/3.5.1

Release files / finishline-0.3.0-py3-none-any.whl

Download URL finishline-0.3.0-py3-none-any.whl
Size 6.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
5f813dc48497d0adee271b455ea974087b9fb87d3bf54a100fe6ad895f69c973
BLAKE2b-256 checksum
How to use checksums
adcb92df8229e23ad043f26d6262eb6cff337ede4ccf2ddb0d2e9dd5368b48ab
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.12.1 pkginfo/1.4.2 requests/2.18.4 setuptools/36.2.7 requests-toolbelt/0.8.0 tqdm/4.25.0 CPython/3.5.1

Security for finishline 0.3.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page