Python server creating interactive vue app over WebSocket


Keywords
Python, Vue, js, websocket, VTK, ParaView, Web3D, 3d, paraviewweb, visualization, web
License
BSD-3-Clause
Install
pip install pywebvue==2.11.5

Documentation

py-web-vue

Python package that let you create web based application by just writting a Python file and forget about JavaScript. PyWebVue rely on a pre-built generic web client that let you focus on what matters to you. In order to reduce the burden on both side we took an oppiniated approach that might not fit every needs but should satisfy most of the use cases for building a Vue.js based application relaying on a Python server for heavier computation while offering efficient communication paradigms to enable interactive 3D visualization using VTK or ParaView.

In other words, we are providing a "battery included framework" which allow you to easily leverage either VTK/ParaView/vtk.js library. None of those libraries are a requirement for taking advantage of this framework but it was designed with those libraries in mind.

Getting started

PyWebVue is a Python package that can be installed via pip and will provide all the pieces that you need to create your dynamic web application without touching any JavaScript.

PyWebVue is relaying on a Vue.js stack for its client side and provide access to a Router, widgets via Vuetify, Material Design Icons and methods to edit and update a global state. The web interface will be done by writing a single HTML file using the Vue syntax of its template. Of course you can break that big template into smaller chunks using Python string template but at the end we are expecting a text content that should match some html content using the Vue.js syntax.

What PyWebVue is offering is a simple Python based API for:

  • defining your HTML content
  • synchronize a common state between the server and the client
  • link python methods with pieces of state modification
  • call methods from client to server
  • call methods from server to client
  • serve your own resources (data, js, css, vue libraries, ...)
  • define routes for various HTML content based on URL
  • define favicon and icon shortcuts

HTML templating

Obviously if you plan to create a Web application you will have to write some HTML to some extent. With PyWebVue we've choosen to leverage Vuetify for building the content of your web application. Of course, you don't have to, but we feel that it is a well balanced library to create your UI without requiring to define your own CSS or component and it give you enough freedom to do all of it from a template file.

So the idea behind PyWebVue and HTML templating is to write the HTML section of the app that lives in the <body></body> section of an HTML page using the vue.js/vuetify syntax.

You can find a basic example of an app.py content example below to illustrate what we mean by HTML templating.

from pywebvue import App

app = App('Super cool web app')

app.layout = '''
    <v-app>
        <v-app-bar app>
            <v-icon class="mr-4">mdi-menu</v-icon>
            Welcome
            <v-spacer />
        </v-app-bar>
        <v-main>
            <v-container fluid>
                Hello World, this is my first Web App...
            </v-container>
        </v-main>
    </v-app>
'''

if __name__ == "__main__":
    app.run_server()

As a add-on you can also set a file path relative to your app.py file to app.layout and even have that updated while your application is running. That way you can write something like that:

app.layout = './template-1.html'

def update_page(index=1):
    app.layout = f'./template-{index}.html'

More over if you are loading an external library using app.vue_use = [...] you could replace the runtime compiled template to an existing component by setting app.layout = '#my-component-name'.

State handling

If you want to involve a Python server it is most likely because you want to control the Web UI from some functions at the Python level. A convinient approach that we took was to define a state and let both the client and the server read and write to it. The library will take care of synchronizing both side for you. You just need to use set(key, value) and get(key) along with the annotation @app.change(key1, key2, ...) to automatically bind a method execution when a given value for a key has been modified by either side. You should also define an initial state inside your app.

The example below capture how to use the state synchronisation:

from pywebvue import App

app = App('State synchronization')

app.state = {
    'magicNumber': 3.14159,
    'serverMessage': 'Let start with Pi',
}

@app.change('magicNumber')
def update_message():
    value = app.get('magicNumber')

    if value > 1:
        app.set('serverMessage', 'What a nice positive number')

    if value < 1:
        app.set('serverMessage', 'What a nice negative number')

    if value ** 2 < 1:
        app.set('serverMessage', 'Oh that is a small number')

    if value > 20:
        app.set('magicNumber', 3.14159)
        app.set('serverMessage', 'Sorry I did not like your number, I prefer Pi')


app.layout = '''
    <v-app>
        <v-app-bar app>
            <v-icon class="mr-4">mdi-menu</v-icon>
            Welcome
            <v-spacer />
        </v-app-bar>
        <v-main>
            <v-container fluid>
                {{ magicNumber }} - {{ serverMessage }}
                <v-btn @click="set('magicNumber', 100 * (Math.random() - 0.5))">Random</v-btn>
            </v-container>
        </v-main>
    </v-app>
'''

if __name__ == "__main__":
    app.run_server()

Calling a method

It may happen that relying on the state might not be enough and you are looking to execute a method somewhere.

From HTML to Python

Here is an example on how to do it:

@app.trigger('some.unique.name')
def server_call(*args, **kwargs):
    print('Args', *args)
    print('Kwargs', **kwargs)
<v-btn @click="trigger('some.unique.name', ['arg0', 'arg1'], { a: 1, b: 'str' })">Trigger</v-btn>

From Python to HTML

Here is an example on how to do that:

def call_client_mehod():
    app.update(ref='view', method='resetCamera', args=[])
<vtk-view ref="view" />

Serving your files over HTTP

It is possible that you may want to serve some of your own JavaScript, CSS or else such as data files. To serve several local directory, you will have to set the app.serve field as a dictionary. The key correspond to the URL path while the value will correspond to the local directory content that you would like to serve.

app.serve = {
    'assets': './www/assets',
    'local/css': './www/css',
    'local/js': './www/js',
    'data': './data',
}

Loading CSS

Since you can serve your own CSS files, you can also load them in your web application by referencing them with app.styles = ['/local/css/main.css', '/local/css/add-on.css'].

Loading Scripts

Since you can serve your own JavaScript files, you can also load them in your web application by using the following setup:

app.scripts = ['/local/js/Vuetify.umd.min.js', '/local/js/AddOnWidgets.umd.min.js']
app.vue_use = ['Vuetify', 'AddOnWidgets'] # => Vue.use(window.Vuetify) + Vue.use(window.AddOnWidgets)

Vue.use(...)

PyWebVue comes with vuetify, router and vtk built-in but if you plan to use the bundled ones, you will have to list them in app.vue_use = ['vuetify']. Those 3 lowercase names are reserved to reference the built-in ones. But if you want to build your own Vuetify or else, you can do so by serving your library while triggering the Vue.use() for your plugin/library.

The string provided in your vue_use array will be processed like you will write it in JavaScript. You can see some example below:

app.vue_use = ['Vuetify', 'complex.example.Widget']
# Vue.use(window['Vuetify'])
# Vue.use(window['complex']['example']['Widget'])

Handling routing

Vue Router is part of the bundle and you can enable it by registering it in your app as follow:

app.vue_use = ['vuetify', 'router']

Then you can register your routes as follow:

app.routes = [
  {
    'name': 'home',
    'path': '/',
    'component': {
      'template': '<div>Root path</div>',
    },
  },
  {
    'name': 'foo',
    'path': '/foo',
    'component': {
      'template': '<div>Foo path</div>'
    },
  },
  {
    'name': 'bar',
    'path': '/bar',
    'component': {
      'template': '<div>Bar path</div>',
    },
  },
]

And if you want a full working example, you can look at ./examples/00_getting_started/router/app.py.

Vuetify configuration

When using the built-in vuetify you can customize it by providing the option argument when instanciated inside the root Vue component.

This is done as follow:

app.vuetify = {
    'icons': {
        'iconfont': 'mdi',
        'values': {
          'add': 'mdi-database-plus-outline',
          'remove': 'mdi-database-minus-outline',
          'menu': 'mdi-menu',
        },
    },
    'theme': {
        'themes': {
          'light': {
            'primary': '#3f51b5',
            'secondary': '#b0bec5',
            'accent': '#8c9eff',
            'error': '#b71c1c',
          },
        },
    },
}

FavIcon

You can provide your own favicon by pointing to an image file like below.

app.favicon = './favicon-196x196.png'

Methods available in HTML

Inside your template it might be convinient to call some helper function. The list below show what is available to you inside your HTML code.

  • key read/write variable matching the available state value.
  • get(key) will return the current state value for that key. The key can also be used as a read/write variable.
  • set(key, value) will set the new value for that key in the state. You can also write it like key=value.
  • setAll(changeSet) allow you to update several keys at once like in the following example setAll({a:1, b:2})
  • trigger(name, args, kwargs) allow the JavaScript to call Python methods.
  • dirty(key) allow the client to force push a local state key onto the server. You can provide a single key or provide an Array of keys to send many at once. This is especially useful when mutating sub-section of a value of the state that prevent automatic change detection.
  • wsClient give you access to the communication channel in case a compnent would require to make direct connection to the server.
  • isBusy() will return true/false depending if we have pending server request/update
  • window provide the window namespace.
  • registerDecorator(decorator) allow to dynamically configure decorator to properly handle serializer/deserializer for custom data (i.e: TypedArray/Numpy, File, ...)
  • download(filename, content, type) make the client available to create downloadable file on the client side.

Methods available in Python

The app object let you read or mutate the state using the get/set methods. When you want to execute a method when a piece of the state change, you will decorate your function with @app.change('key1', 'key2') and inside that function you can get the various piece of state you want but also check if a given key was updated before that execution call dirty(*args) or dirty_all(*args) in case you only want to do something if a given value has changed or not.

On top of the state management helper functions we have other utility functions with specific implementation based on the activated backend.

  • url(file_path) return a base64 encoded url string of that given file
  • text(file_path) return the text content of the given file where the relative path is rooted at the app.py file
  • id(obj) return a unique string to identify a given object
  • object(id) return the object based on the string id returned by id(obj). It is a convinient way to reference objects easily across the network.
  • mesh(dataset, field_to_keep=None, point_arrays=None, cell_arrays=None) return a serializable version of a mesh for doing local rendering via a state variable.
  • scene(render_window/pv_view) return a serializable version of a full RenderWindow so it can be mirrored on the client side while still using the state variable.
  • push_image(render_window/pv_view) force image push to client for our remote-rendering component.
  • camera(render_window/pv_view) return a serializable version of our camera
  • set_camera(render_window/pv_view, **kwargs) update our view camera to match the provided arguments

Development tools

How to develop your HTML content fast and easily. Add debug=True when building your app instance. That will make your ./template.html automatically update when changed on the file system.

Running an example from repo

Install Python package in venv

python3 -m venv py-env
source ./py-env/bin/activate
pip install pywebvue

For development you can install the local code

python3 -m venv py-env-dev
source ./py-env-dev/bin/activate
pip install -e ./python/

cd client
npm i
npm run build

If you are using VTK backend

# Only VTK nightly work with PyWebVue until VTK>=9.1 which will be the first compatible release
# PyWebVue>=1.3 require a VTK version newer than 2021-08-11 (Not yet available at the time of writting)
# PyWebVue<1.3 can use the any nightly one like the one below
pip install vtk==9.0.20210717.dev0

If you are using ParaView backend

Only ParaView nightly or 5.10+ support PyWebVue. You can download a nightly binary of ParaView here.

ParaView 5.10 will embed PyWebVue and would not require any additional python package in a virtual environment. This should also be true with nightly after 2021-08-23. But until then, you will need a virtual-environment with pywebvue==1.2.6.

pip install pywebvue==1.2.6

Run demo

source ./py-env/bin/activate
python ./examples/.../app.py

Command lines arguments

A default PyWebVue application support the following set of command line paramenters.

PyWebVue server By Kitware

optional arguments:
  -h, --help            show this help message and exit
  --launcher            Start launcher process rather than single process server
  --deploy DEPLOY       Prepare a deployable directory
  --name NAME           Name to use for that application in the deploy tree
  -d, --debug           log debugging messages to stdout
  -s, --nosignalhandlers
                        Prevent Twisted to install the signal handlers so it can be started inside a thread.
  -i HOST, --host HOST  the interface for the web-server to listen on (default: localhost)
  -p PORT, --port PORT  port number for the web-server to listen on (default: 8080)
  -t TIMEOUT, --timeout TIMEOUT
                        timeout for reaping process on idle in seconds (default: 300s)
  -a AUTHKEY, --authKey AUTHKEY
                        Authentication key for clients to connect to the WebSocket.

In local setup 1-process/1-client, we usually only use --port 8080 and sometime --host 0.0.0.0 when the default localhost value is not enough to allow external connection to connect to the process.

For basic usage of local multi-clients, you can use the --launcher argument that will automatically start a new process per connection while dynamically binding more port on the host.

For real deployment, you can build a directory structure for your app that can be used by our ParaViewWeb docker image using the --deploy and --name paramters. The generated directory will get you 90% setup and a little tune-up might be required to properly support such deploymement.