[Qtwebengine] Hopeful of a timeline?
flying-sheep at web.de
Tue Jan 6 00:40:56 CET 2015
2015-01-05 19:18 GMT+01:00 Jocelyn Turcotte <jocelyn.turcotte at digia.com>:
> I have to note that QtWebEngine isn't a 1-to-1 replacement of QtWebKit,
> principally because some very advanced features can't be set in stone
> through a public API without risking huge future maintenance efforts as
> Chromium evolves under our feet. It is quite a dragon to ride.
I’m sorry to say that, but that’s awful to hear. I expected QWebEngine to
be *more* powerful than QWebkit.
Things like cookie management and complete control over requests, as well
as access to the devtools are essential features for every more complex
application. and that’s just the obvious puzzlers that i immediately
The public API aims at solving the general use case of embedding web
> contents in Qt applications,
This is already solved by simple stuff like the QML WebView.
> but if you are developping a more powerful
> application I encourage you to look at the code and dig further to get
> access to functionalities that you need, keeping in mind that the
> further you dig, the more likely you'll have to update your code between
> QtWebEngine updates.
So you’re saying that we need to compile our own version of QWebEngine with
I think many people expected it to be QWebkit with API cruft removed and a
new backend. but now we are in the sad position to have a deprecated
QWebkit that can do what we want (except modern HTML5 because it’s frozen)
and a castrated QWebEngine that can’t and possibly won’t ever be able to do
necessary things (if i understood you correctly)
again: i don’t want to descredit the hard work that went into executing the
switch, but i question the research that went into the decision to abandon
something with adequate capabilities for something with less.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the QtWebEngine