Transition WebKit to WebEngine

Robert Helling helling at atdotde.de
Wed Aug 10 14:30:48 PDT 2016


Hi,

I started to work on the transition to WebEngine, here is what I got so far: 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 0001-Start-transition-from-QWebKit-to-QWebEngine.txt
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20160810/e651d941/attachment-0001.txt>
-------------- next part --------------


In current master, WebKit is used in three places 1) user manual, 2) Facebook connection, 3) printing

As I understand it, the situation is as follows:

re 1) With this patch, the user manual works.

re 2) FB should also work (at least it compiles, minus one reference to the cookie jar). But at least for me, FB integration is currently also missing in current master (I have no idea why, ccmake says yes to FB), so I could not test.

re 3) This is hard and (at least currently) beyond my powers. In master, to render the page for printing, html elements in the page are accessed to get the page breaks right and then (parts of the) page is rendered to the printer. With WebEngine, according to the transition documents, you cannot access html elements anymore. You are supposed to do this in Javascript and then invoke some callback function from there. Too bad I know virtually nothing about Javascript. And then, the rendering to the printer is probably also different. There is a new functionality to render a QWebEngineView to a pdf file, but I don’t know how that handles page breaks. So, currently, large parts of the printing functionality are commented out and consequently, with this, there is currently no printing.

There is another difference between WebEngine and WebKit: The new approach does not go through the QNetWorkManager anymore but accesses the net directly. This might bring new problems with cookies, proxies etc.

Any help is appreciated.

Best
Robert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20160810/e651d941/attachment-0001.sig>


More information about the subsurface mailing list