Sync applets across dashboards with master-running AppletDB class about artiq HOT 2 OPEN

Might be reasonably straightforward to get pyqt/pyqtgraph output into a virtual framebuffer, and forward the framebuffer (possibly with VNC/rdesktop-style compression), and mouse and keyboard events between dashboard and master. Qt used to have something called qvfb that we can look into.

But it would break, at least:

• any applets written for toolkits other than Qt.
• pyqtgraph functionality that opens additional windows, such as the "export to PNG" feature.
• most likely any OpenGL acceleration.

from artiq.

@sbourdeauducq What I was suggesting here was just to have the applet data (name, command) saved in an applet database which is managed by the master so that the list of applets can update automatically in each connected dashboard in the same way the datasets do. It sounds like your solution here is to actually run pyqt from the master? Do you see an added benefit to going that far? I am not 100% sure the mechanics of how the datasets update but I was imagining the list of applets could be updated in a similar way with an AppletDB class and database. This shouldn't change how the applets run within individual dashboards, so it should avoid breaking the things that you mention here.

from artiq.