QtWebKit?
René J. V. Bertin
rjvbertin at gmail.com
Sat Mar 2 14:24:34 GMT 2019
> As far as I know, the "reboot" has stalled
> already.
There have been no new (pre)releases, but AFAIK work goes on in the actual repo,
and periodic commits are made to the release branch.
QWE is just as stalled if you don't install each and every new release of it
(which will often mean building it from source). And even if you do you probably
don't get the latest WE.
> Personally I would not encourage anyone to use QtWebKit at
> this point, no matter how lighter is compared to WebEngine.
Lighter and typically a lot faster.
I wouldn't encourage anyone either to use QWE if they expect it to be that much
more secure than QWK, but instead use one of the big browser names that push
regular updates.
For my PIM needs I could most likely do with QTextBrowser coupled with an easy
way to open too complex content in my default web browser. I maintain a KDevelop
patch that does the equivalent for its builtin documentation browser.
> AFAICS, not doable. WebEngine handles things async, WebKit does not, or
> vice versa. It's going to be an unmaintainable mess.
Is there at least a central class that provides the interface or are we talking
about direct calls into QWE API in "random" locations?
FWIW, at this point I don't care whether or not "you" will support anything but
QWE (it's been clear long enough you won't, and the notion of "support" in free
software, well, let's say it mostly gives me the giggles).
R.
More information about the kde-pim
mailing list