Re: Qt 5.6/QtWebkit (got it, now to build it)

2016-03-21 Thread René J . V . Bertin
Antonio Rojas wrote: > Besides generating headers with syncqt.pl, you need to backport a patch to > fix linking to pthread Yeah, that's on Linux, though I got the impression not everyone had to apply the patch. I'm homing in on whatever issue it is that causes my standalone build to fail whe

Re: Qt 5.6/QtWebkit (got it, now to build it)

2016-03-20 Thread Antonio Rojas
René J. V. Bertin wrote: > I presume there must be at least one member on this list who managed to > build QtWebKit 5.6.0 (and remembers how)? See https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/qt5-webkit Besides generating headers with syncqt.pl, you need

Re: Qt 5.6/QtWebkit

2016-03-20 Thread René J . V . Bertin
Aleix Pol wrote: > > https://code.qt.io/cgit/qt/qtwebkit.git/ Right, thanks, I'd seen that one too (there's also a clone on github but it isn't clear how recent/unmodified that one is). What I didn't yet see is if there's a way to do tarball fetches from code.qt.io that correspond to a speci

Re: Qt 5.6/QtWebkit

2016-03-20 Thread Michael Palimaka
On 17/03/16 03:59, René J. V. Bertin wrote: > Aleix Pol wrote: > > >> >> https://code.qt.io/cgit/qt/qtwebkit.git/ > > Right, thanks, I'd seen that one too (there's also a clone on github but it > isn't clear how recent/unmodified that one is). > > What I didn't yet see is if there's a way to d

Re: Qt 5.6/QtWebkit

2016-03-19 Thread René J . V . Bertin
Kevin Funk wrote: > I think qt-developm...@qt-project.org is a better fit for this question. Good call. From Jani Heikkinen: > Webkit packages can be found from here: > http://download.qt.io/community_releases/5.6/5.6.0/ R. ___ Kde-frameworks-deve

Re: Qt 5.6/QtWebkit

2016-03-19 Thread René J . V . Bertin
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

Re: Qt 5.6/QtWebkit

2016-03-19 Thread René J . V . Bertin
On Friday March 18 2016 17:39:18 Milian Wolff wrote: > > If so it seems it should have been possible to reimplement QtWebKit using a > > similar approach with probably far fewer API changes. > > Which WebKit implementation would you have chosen? The GTK one? Huh?? Upstream WebKit is probably jus

Re: Qt 5.6/QtWebkit

2016-03-19 Thread Kevin Funk
On Wednesday, March 16, 2016 5:59:30 PM CET René J. V. Bertin wrote: > Aleix Pol wrote: > > https://code.qt.io/cgit/qt/qtwebkit.git/ > > Right, thanks, I'd seen that one too (there's also a clone on github but it > isn't clear how recent/unmodified that one is). > > What I didn't yet see is if th

Re: Qt 5.6/QtWebkit

2016-03-19 Thread David Edmundson
On Wed, Mar 16, 2016 at 12:52 PM, René J.V. wrote: > Hi, > > Is there a page/site somewhere that outlines the current status of Qt > 5.6/KF5 compatibility, notably as far as QtWebkit is concerned? > > A quick search (KF5 qt5.6 qtwebkit) didn't turn up any particularly useful > hits in the first p

Re: Qt 5.6/QtWebkit

2016-03-19 Thread Aleix Pol
On Thu, Mar 17, 2016 at 10:54 AM, René J. V. wrote: > David Edmundson wrote: > >> There was a thread "Policy regarding QtWebKit and QtScript" on >> kde-core-devel a while ago. >> http://kde.6490.n7.nabble.com/Policy-regarding-QtWebKit-and-QtScript-td1619988.html > > What I'm missing (as in not get

Re: Qt 5.6/QtWebkit (got it, now to build it)

2016-03-19 Thread René J . V . Bertin
René J. V. Bertin wrote: >> Webkit packages can be found from here: >> http://download.qt.io/community_releases/5.6/5.6.0/ I presume there must be at least one member on this list who managed to build QtWebKit 5.6.0 (and remembers how)? Sorry about asking on here, but I'm not getting any answer

Re: Qt 5.6/QtWebkit

2016-03-19 Thread Milian Wolff
On Donnerstag, 17. März 2016 14:52:15 CET René J. V. Bertin wrote: > 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, y

Re: Qt 5.6/QtWebkit

2016-03-19 Thread Aleix Pol
On Wed, Mar 16, 2016 at 2:54 PM, René J. V. wrote: > David Edmundson wrote: > > >> There was a thread "Policy regarding QtWebKit and QtScript" on >> kde-core-devel a while ago. >> http://kde.6490.n7.nabble.com/Policy-regarding-QtWebKit-and-QtScript-td1619988.html > > Indeed there was, a short whil

Re: Qt 5.6/QtWebkit

2016-03-19 Thread René J . V . Bertin
David Edmundson wrote: > There was a thread "Policy regarding QtWebKit and QtScript" on > kde-core-devel a while ago. > http://kde.6490.n7.nabble.com/Policy-regarding-QtWebKit-and-QtScript-td1619988.html What I'm missing (as in not getting) in that discussion is the whole thing about (Qt)WebKit

Re: Qt 5.6/QtWebkit

2016-03-18 Thread René J . V . Bertin
David Edmundson wrote: > There was a thread "Policy regarding QtWebKit and QtScript" on > kde-core-devel a while ago. > http://kde.6490.n7.nabble.com/Policy-regarding-QtWebKit-and-QtScript-td1619988.html Indeed there was, a short while ago even. It mostly argues about the cost of building QtWeb