Teleplot 2

[nesnes]

Limitations of the first naive approach of teleplot are now preventing a wider usage and adoption.

The goals of this rework are multiple and notably:

• Library: Move away from being 'just' a webapp, and offer a teleplot-js.js library anyone could integrate in its own web page.
• Webapp: Rework the existing webapp for usability, features and style, by making use of teleplot-js.js, and with a continuous focus on first-access simplicity.
• Binary: Add binary-protocol input to allow its usage on bigger telemetry sets, and get teleplot-js.js (and webapp) performances in line with this added capability. (Keeping the existing text-based protocol for simplicity needs and compatibility)
• More representations: Along the line, add a wider range of possible representations (2D shapes, better 3D environment), and solidify basic visualisations
• Client libs: Provide more robust, yet simple to use, client librairies in common languages, starting with C++, then python, etc.

It's also the time to see what we can learn from existing issues in this repo.

This effort is ONGOING with a lot of parts missing and architectures that can change from a day to the other if the wind blows in a given direction. However, I could use some help!

I'd love to hear from @trns1997 (and the smart guys around you) suggestions you might have on this new version.

This issue is meant to follow this dev and exchange on everyone contributions.

[nesnes]

On the teleplot2 branch, you can for now test the ongoing dev of teleplot-js.js, build building it with packages/teleplot-js/build.sh, and launching packages/teleplot-js/test.html.

The test.html file is not the web app (obviously), so don't expect a 'teleplot interface' here. It's a debug page to call some functions of the teleplot-js.js library and see how they run/render.

You can also check the last part of the readme, and the doc/binaryProtocol.mdfor any recommendations

[mhaberler]

great you're continuing on this project!

I'd have a few suggestions:

• completely separate the UI from the concept of teleplot wire format - do a generic map of UDP format to JSON and have UI components register handlers of objects with certain names/attributes
• the UI would be super useful in different context like as an MQTT client without any UDP/websocket assumptions wired in
• give some thought how to add in new components without wire format changes
• the usage of commands via UDP is rather unclear (use case?)
• move to Vue3/Typescript/vite

example idea to make teleplot work as a MQTT client:

• subscribe to topic
• associate with a JSONata expression which arranges values into the format expected by a new component (like eg map, cesiumjs 3d etc)
• pass to proper component based on attributes

happy to help a bit from the sidelines, and test

Michael

[mhaberler]

new binary format - makes sense (I guess to reduce serialisation+parsing overhead)

inventing a new binary format: makes zero sense to me

there are several battle-proven serialisation formats with a ton of language bindings

most of google runs on protobuf and every binding under the sun available
msgpack would be schema-free, also lots of bindings
flatbuffers would qualify as well I guess

so - why?