How I integrated TinyMCE into my Qt Application
summary
A working WYSIWYG HTML editor sits inside a QWebView using TinyMCE bridged to C++ via the QWebKit JavaScript bridge, with native Qt dialogs replacing TinyMCE popups and a roundtrip where C++ executes JS to insert images and links. Initialization needs 150–200 ms init delay to wait for the editor JS to load. Limitations include dialogs stuck inside the web view, same‑origin asset issues requiring a physical HTML host per base path, high resource overhead, and TinyMCE 4.x incompatible with Qt WebKit.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:10About me
- 1:19KDE Frameworks 5
- 2:29How to get there?
- 3:20TinyMCE Limitations
- 5:44QWebkit
- 6:41Class HTML TextEditor
- 10:28C++ Implementation
- 12:43Current limitations
- 13:17What I also would need...
- 13:43Endresult
related talks
01h 01mAdvanced Qt - A Deep Dive 5/6 - ModelView Part 1
01h 14mAdventures with React and JUCE: Building UI with Typescript in a C++ Application
05mIntroducing Qt Creator: a fast IDE for C++ development
49mWindows, macOS & the Web: Lessons from Cross-platform Development at think-cell
01h 19mBuilding a C++/JS Browser for the Financial Markets
01h 25mAdvanced Qt -A Deep Dive 1/6 Graphics View Part 1
57mC++ on the Web: Let's have some serious fun.
01h 08mWindows, Macos & the Web: Lessons From Cross-Platform Development