Qt and the web, where are we today?
summary
Survey of concrete options: use QNetworkAccessManager or QML XMLHttpRequest plus JSON and XML parsing to call REST and WebSocket APIs; use QWebSocketModule and QNetworkAuthorization for secure token auth; host services with the new-but-experimental QHttpServer and QWebSocketServer; render web UIs with Qt WebEngine or Qt WebView; export Qt Quick to browsers via WebGL QPA streaming (low-latency, single-user) or VNC proxy (fixed resolution), or compile to Qt for WebAssembly (20–30 MB downloads, long link times but runs in-browser).
AI-written summary · about
chapters (8)
- 0:00Introduction and context
- 2:00The web's influence
- 5:37Qt as a client
- 11:18Qt as a server
- 14:19Rendering web content
- 19:07Qt in the browser
- 25:01Qt web assembly
- 28:21Conclusion and Q&A
