Clear the scene and sub-scene fields in DOM at every render before refill;

Simplify the API with a simpler logic

Start flaskdings as a service

A développer cet été

In development mode, it's lightning fast as hell.

When I switch in production mode with eventlet, the solution just died.

Use a tool to document the endpoints

Add the flask server state in the UI

Just a bad fillename in the service

Hello Stéphane,

nice program! What about adding a LICENSE file to make the license explicit and maybe, if it's FLOSS, attract contributors and packagers? Thank you!

Already in LiveOSC

To fit with node-red-flow-mididings

Add important events and errors in a log file

If there is no internet network, new clients will never receive any js/css files, the layout will be horrible.

Add the Bootstrap files in the static folder instead of CDN

Add a button to disconnect client
Add a button to shutdown mididings

Flaskdings don't really know if Websockets is alive and runnings

Flaskdings don't know if MIDIDINGS is running or has been interrupt.

Flaskding will break change for mididings community maintained version.

To work with the legacy mididings use the TAG version mididings-legacy