On 7/9/20 5:00 AM, René J.V. Bertin wrote:
I have no idea how big the public QtWebKit API really is, but a more
interesting/exciting/cool solution might be to replace Qt4WebKit with smallish
glue library that somehow uses a Qt5-based render process. I notice that the
rebooted QtWebKit can work with an external render process, so I presume that
it should be possible technically to interface with that from Qt4.
Well, according to this documentation link for Qt 4.8
https://doc.qt.io/archives/qt-4.8/qtwebkit-guide.html
and this documentation link for CopperSpice
https://www.copperspice.com/docs/cs_api_1.6/concepts-webkit.html
They have a "slightly" newer version of WebKit.
"CsWebKit is a web content rendering engine based on the open source
WebKit project, featuring broad support for standard web technologies.
CsWebKit is developed as a part of the WebKit community, which enables
every new release of CsWebKit to include the latest developments from
the WebKit project."
You might want to see how much pain would be involved in porting your
applications to CopperSpice which is a fork of Qt 4.8-something sans all
of the nasty QML stuff. They've fixed/changed quite a few other things
too. At some point in the near future they promise what the
medical/industrial device world has been dying for . . . a __stable__ API.
Maybe that quote from the page is a dream they hope to achieve? I don't
know. I just know it is there. I guess you can pick your pain. <Grin>
--
Roland Hughes, President
Logikal Solutions
(630)-205-1593
http://www.theminimumyouneedtoknow.com
http://www.infiniteexposure.net
http://www.johnsmith-book.com
http://www.logikalblog.com
http://www.interestingauthors.com/blog
_______________________________________________
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
