Qt 5.6/QtWebkit
René J. V. Bertin
rjvbertin at gmail.com
Thu Mar 17 13:52:15 UTC 2016
Aleix Pol wrote:
> WebKit integration was done through forking then integrating. It was
> awkward because merging upstream changes meant rebasing our work on
> theirs.
> That's why it's Chromium is better in this regard, you get to interact
> the upstream component without forking it, AFAIU.
You mean Chromium is used as a sort of external library with a more or less thin
wrapper on top/around it?
If so it seems it should have been possible to reimplement QtWebKit using a
similar approach with probably far fewer API changes.
Not that that matters now ... for those of us who are on (readily) supported
platforms.
R.
More information about the Kde-frameworks-devel
mailing list