QtWebEngine is not yet enabled (hooked up) but this version works for the most use-cases. Google maps, Youtube stream with sound, nextcloud... I have not tested video conferences, this is not the main use case either. Most applications do not use QtWebEngine to implement a browser but to interact with certain HTTPS services/websites or for showing HTML docs. Next tasks: - Slowly switch and test some KDE5 applications from qtwebkit to qtwebengine - py-qtwebengine FYI: We're not going to switch otter-browser to QtWebEngine. Otter is the only browser really working on macppc. To be honest, this would never be possible without the incredible chromium patches collection of robert@ and his input. So a lot of patches come from www/chromium/patches and some form FreeBSD.
9 lines
478 B
Plaintext
9 lines
478 B
Plaintext
The Qt WebEngine module provides a web browser engine that makes it easy to
|
|
embed content from the World Wide Web into your Qt application on platforms
|
|
that do not have a native web engine.
|
|
|
|
Qt WebEngine provides C++ classes and QML types for rendering HTML, XHTML, and
|
|
SVG documents, styled using Cascading Style Sheets (CSS) and scripted with
|
|
JavaScript. HTML documents can be made fully editable by the user through the
|
|
use of the contenteditable attribute on HTML elements.
|