Companion apps and more second screen options with Qt
summary
Motivation, concrete options and working demos for adding a second screen: state sync via Qt Remote Objects to avoid mismatched UI state; remote display with the built‑in VNC platform plugin that streams damaged pixels and injects events; rendering to browser with a WebGL platform (single active client) and full-portable binaries using WebAssembly via Emscripten (builds to .wasm and serves over HTTP). Also covered are WebSockets for live data, H.264/frame capture pipelines (GammaRay uses glReadPixels + compression), limits: latency, no multi‑seat, and desire for a raw frame ABI.
AI-written summary · about
chapters (11)
- 0:00Introduction to second screens
- 1:47Reasons for remote screens
- 5:41Existing remote options
- 7:47VNC platform plugin demo
- 11:19WebGL streaming demo
- 12:48WebAssembly deployment
- 17:31Syncing data with remote apps
- 18:16Screenshot streaming methods
- 20:17Current challenges in Qt
- 22:49Future wishes for Qt
- 24:17Q&A session
related talks
49mScaling Qt from Desktop to Servers and Micro-controllers
39mQtinUse - Developing the Netflix TV/Movie Streaming Service with Qt
45mQt, multimedia, and computer vision – a great match for Embedded Linux
40mHow to Develop with Qt for Multiple Screen Resolutions and Increase
48mBuilding Desktop and Embedded Uis with Qt 3D
58mHybrid development with QtWebKit
44mWebKit 2 - Looking Forward
24mQt's Web Offering- An Overview