Hybrid Development: Bridging the Gap Between Web and Native
summary
Shows a working hybrid pattern: a desktop Qt app embeds WebKit, exposes a C++ QObject called TextAnalyzer to JavaScript via addToJavaScriptWindowObject, and uses QTimer plus signals, slots and a progress property to simulate a heavy background task. Demonstrates type conversion and returning structured data with QVariantMap (JSON-like), the UI polls progress and receives a done callback (demo returns 10 characters). Notes Qt 4.4–4.7 compatibility, when to prefer native widgets or Qt Quick, and threading caveats.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 1:40Who am I
- 2:28The point of web applications
- 4:13The point of native applications
- 6:13Combining Web and Native
- 8:44How does it work
- 10:20Regular application
- 11:00Hygiene
- 12:28Load HTML
- 14:05Test
- 14:46Analyzing Text
- 15:38Text Analyzer
- 16:42Monitor Progress
- 19:57Analyze Next Ring
- 22:52Make Everything Hybrid
- 24:03Web Security
- 28:29Hybrid Text Analyzer
- 32:11Testing
- 33:57Query Selector
- 38:15Unfortch
- 39:14Progress
- 45:22Questions
- 45:33Qt Quick
- 46:12Portability
- 48:26Avoid it
- 50:03Qt Documentation
- 51:08Qt MultiThreading
- 55:40Should you use Qt Quick
related talks
58mHybrid development with QtWebKit
32mQt and the web, where are we today?
01h 02mAnatomy of real world apps, Qt Quick and C++
44mWebKit 2 - Looking Forward
28mA Desktop UI with Qt Quick
24mQt's Web Offering- An Overview
24mHow Qt WebEngine can help support modern web technologies for your app
09mHow I integrated TinyMCE into my QtApplication