Re: [Development] QtWebKit is coming back (part 2)

07.09.2017, 10:45, "Martin Koller" : >> It also seems that it requires a too new ICU devel package (at least >> for CentOS 7.3), that is I need to deactivate INTL by using >> -DENABLE_INTL=OFF >> >> Can you tell us what I actually disable with that switch, e.g.: what >> does no

Re: [Development] QtWebKit is coming back (part 2)

07.09.2017, 10:45, "Martin Koller" : > On Donnerstag, 27. Juli 2017 16:13:05 CEST Konstantin Tokarev wrote: >>  27.07.2017, 16:41, "Martin Koller" : >>  > On Dienstag, 25. Juli 2017 14:20:28 CEST Konstantin Tokarev wrote: >>  > >>  >> >> You can compile with GCC 4.8

Re: [Development] QtWebKit is coming back (part 2)

On Donnerstag, 27. Juli 2017 16:13:05 CEST Konstantin Tokarev wrote: > > 27.07.2017, 16:41, "Martin Koller" : > > On Dienstag, 25. Juli 2017 14:20:28 CEST Konstantin Tokarev wrote: > > > >> >> You can compile with GCC 4.8 if IndexedDB and FTL JIT are disabled. > >> However this

Re: [Development] QtWebKit is coming back (part 2)

17.08.2017, 18:17, "Thiago Macieira" : > On Thursday, 17 August 2017 08:12:23 PDT Konstantin Tokarev wrote: >>  Altrernatively, you can drop qtwebkit sources on the same level with other >>  Qt modules, however it will break if you customize installation paths, e.g. >>

Re: [Development] QtWebKit is coming back (part 2)

On Thursday, 17 August 2017 08:12:23 PDT Konstantin Tokarev wrote: > Altrernatively, you can drop qtwebkit sources on the same level with other > Qt modules, however it will break if you customize installation paths, e.g. > use custom libdir. Also, cross-compilation is not supported in this way

Re: [Development] QtWebKit is coming back (part 2)

17.08.2017, 18:06, "Thiago Macieira" : > On Thursday, 17 August 2017 07:24:05 PDT Martin Koller wrote: >>  Hi, >> >>  is the 5.212 branch now as integrated in Qt as it was before in Qt 5.5 in >>  the way that I can build Qt with webkit support so that the help system

Re: [Development] QtWebKit is coming back (part 2)

On Thursday, 17 August 2017 07:24:05 PDT Martin Koller wrote: > Hi, > > is the 5.212 branch now as integrated in Qt as it was before in Qt 5.5 in > the way that I can build Qt with webkit support so that the help system and > assistant also use it ? No. You need to use the split-build

Re: [Development] QtWebKit is coming back (part 2)

Hi, is the 5.212 branch now as integrated in Qt as it was before in Qt 5.5 in the way that I can build Qt with webkit support so that the help system and assistant also use it ? What is the recommended way to build Qt and assistant to have webkit support ? -- Best regards/Schöne Grüße Martin

Re: [Development] QtWebKit is coming back (part 2)

27.07.2017, 16:41, "Martin Koller" : > On Dienstag, 25. Juli 2017 14:20:28 CEST Konstantin Tokarev wrote: > >>  >> You can compile with GCC 4.8 if IndexedDB and FTL JIT are disabled. >> However this brings a >>  >> degradation of user experience, especially in case of IndexedDB

Re: [Development] QtWebKit is coming back (part 2)

On Dienstag, 25. Juli 2017 14:20:28 CEST Konstantin Tokarev wrote: > >> You can compile with GCC 4.8 if IndexedDB and FTL JIT are disabled. > >> However this brings a > >> degradation of user experience, especially in case of IndexedDB which was > >> supported > >> in previous versions.

Re: [Development] QtWebKit is coming back (part 2)

24.07.2017, 08:33, "Martin Koller" : > On Sonntag, 23. Juli 2017 23:45:30 CEST Konstantin Tokarev wrote: >>  23.07.2017, 23:49, "Martin Koller" : >>  > On Mittwoch, 3. Mai 2017 17:03:50 CEST Konstantin Tokarev wrote: >>  > >>  >> I'm not sure it would be acceptable,

Re: [Development] QtWebKit is coming back (part 2)

On Sonntag, 23. Juli 2017 23:45:30 CEST Konstantin Tokarev wrote: > > 23.07.2017, 23:49, "Martin Koller" : > > On Mittwoch, 3. Mai 2017 17:03:50 CEST Konstantin Tokarev wrote: > > > >> I'm not sure it would be acceptable, because updated QtWebKit requires > >> full > >> C++11

Re: [Development] QtWebKit is coming back (part 2)

23.07.2017, 23:49, "Martin Koller" : > On Mittwoch, 3. Mai 2017 17:03:50 CEST Konstantin Tokarev wrote: > >>  I'm not sure it would be acceptable, because updated QtWebKit requires full >>  C++11 support in the compiler (gcc >= 4.9, 4.8 possible with disabling some >>  features,

Re: [Development] QtWebKit is coming back (part 2)

On Sunday, 23 July 2017 13:49:18 PDT Martin Koller wrote: > It would be really nice if the current release branch would compile at least > on these major distros Sorry, it's out of our hands. The source code upstream has moved on and is using C++ features not available in GCC 4.8. -- Thiago

Re: [Development] QtWebKit is coming back (part 2)

On Mittwoch, 3. Mai 2017 17:03:50 CEST Konstantin Tokarev wrote: > I'm not sure it would be acceptable, because updated QtWebKit requires full > C++11 support in the compiler (gcc >= 4.9, 4.8 possible with disabling some > features, or with code changes, which were not done yet). I'm trying to

Re: [Development] QtWebKit is coming back (part 2)

11.05.2017, 16:10, "Oswald Buddenhagen" : > On Wed, May 10, 2017 at 09:53:26AM +0200, Edward Welbourne wrote: >> Oswald Buddenhagen (4 May 2017 18:35) >> > i'll say outright that you can't be part of the qt supermodule and yet >> > have independent releases.

Re: [Development] QtWebKit is coming back (part 2)

On Wed, May 10, 2017 at 09:53:26AM +0200, Edward Welbourne wrote: >Oswald Buddenhagen (4 May 2017 18:35) >> i'll say outright that you can't be part of the qt supermodule and yet >> have independent releases. while that was the plan once upon a time, the >> whole release

Re: [Development] QtWebKit is coming back (part 2)

Oswald Buddenhagen (4 May 2017 18:35) > i'll say outright that you can't be part of the qt supermodule and yet > have independent releases. while that was the plan once upon a time, the > whole release infrastructure simply doesn't deliver, and even just > diverging branch names are a pita (proved

Re: [Development] QtWebKit is coming back (part 2)

  08.05.2017, 15:11, "Lars Knoll" : On 5 May 2017, at 13:15, Konstantin Tokarev wrote: 05.05.2017, 10:04, "Tuukka Turunen" :Hi,There has also been some interest also for getting Qt WebEngine to be released much faster cycle than Qt –

Re: [Development] QtWebKit is coming back (part 2)

>>> From: Development [mailto:development-bounces+jani.heikkinen=qt.io@qt- >>> project.org] On Behalf Of Konstantin Tokarev >>> Sent: maanantaina 8. toukokuuta 2017 12.56 >>> To: Tuukka Turunen <tuukka.turu...@qt.io>; Oswald Buddenhagen >>> <oswald.buddenha.

Re: [Development] QtWebKit is coming back (part 2)

g<mailto:development@qt-project.org> Subject: Re: [Development] QtWebKit is coming back (part 2) 05.05.2017, 14:15, "Konstantin Tokarev" <annu...@yandex.ru<mailto:annu...@yandex.ru>>: 05.05.2017, 10:04, "Tuukka Turunen" <tuukka.turu...@qt.io<mailto:tu

Re: [Development] QtWebKit is coming back (part 2)

;; Oswald Buddenhagen > <oswald.buddenha...@qt.io>; development@qt-project.org > Subject: Re: [Development] QtWebKit is coming back (part 2) > > > > 05.05.2017, 14:15, "Konstantin Tokarev" <annu...@yandex.ru>: > > 05.05.2017, 10:04, "Tuukka Turune

Re: [Development] QtWebKit is coming back (part 2)

05.05.2017, 14:15, "Konstantin Tokarev" : > 05.05.2017, 10:04, "Tuukka Turunen" : >>  Hi, >> >>  There has also been some interest also for getting Qt WebEngine to be >> released much faster cycle than Qt – exactly due to the security update >> need.

Re: [Development] QtWebKit is coming back (part 2)

05.05.2017, 10:04, "Tuukka Turunen" : > Hi, > > There has also been some interest also for getting Qt WebEngine to be > released much faster cycle than Qt – exactly due to the security update need. > Even if we succeed in making substantially more frequent Qt patch

Re: [Development] QtWebKit is coming back (part 2)

05.05.2017, 10:04, "Tuukka Turunen" : > Hi, > > There has also been some interest also for getting Qt WebEngine to be > released much faster cycle than Qt – exactly due to the security update need. > Even if we succeed in making substantially more frequent Qt patch

Re: [Development] QtWebKit is coming back (part 2)

Hi, There has also been some interest also for getting Qt WebEngine to be released much faster cycle than Qt – exactly due to the security update need. Even if we succeed in making substantially more frequent Qt patch releases than before, it may still be better if user would have the option

Re: [Development] QtWebKit is coming back (part 2)

04.05.2017, 19:35, "Oswald Buddenhagen" : > On Thu, May 04, 2017 at 04:51:45PM +0300, Konstantin Tokarev wrote: >>  03.05.2017, 17:27, "Sergio Martins" : >>  > On 2017-05-03 15:02, Konstantin Tokarev wrote: >>  >>  Remaining question is

Re: [Development] QtWebKit is coming back (part 2)

On Thu, May 04, 2017 at 04:51:45PM +0300, Konstantin Tokarev wrote: > 03.05.2017, 17:27, "Sergio Martins" : > > On 2017-05-03 15:02, Konstantin Tokarev wrote: > >>  Remaining question is versioning. While it's fine to dub current > >>  release "5.9" (but not 5.0, because

Re: [Development] QtWebKit is coming back (part 2)

Em quinta-feira, 4 de maio de 2017, às 07:21:03 PDT, Konstantin Tokarev escreveu: > Yes. But using 5.$large_number seems wrong too, because there is no hard > upper limit for Qt 5.x series No, but it's highly unlikely we'll get to 5.20 or 5.100. -- Thiago Macieira - thiago.macieira (AT)

Re: [Development] QtWebKit is coming back (part 2)

On 2017-05-04 14:51, Konstantin Tokarev wrote: 03.05.2017, 17:27, "Sergio Martins" : On 2017-05-03 15:02, Konstantin Tokarev wrote:  Remaining question is versioning. While it's fine to dub current  release "5.9" (but not 5.0, because we will have another WebKit

Re: [Development] QtWebKit is coming back (part 2)

04.05.2017, 17:17, "Thiago Macieira" : > Em quinta-feira, 4 de maio de 2017, às 06:51:45 PDT, Konstantin Tokarev > escreveu: >>  I'm leaning towards "6.0.0" number, because it's larger than any 5.x and >>  makes it clear that versioning is different now. Bug fixes will

Re: [Development] QtWebKit is coming back (part 2)

Em quinta-feira, 4 de maio de 2017, às 06:51:45 PDT, Konstantin Tokarev escreveu: > I'm leaning towards "6.0.0" number, because it's larger than any 5.x and > makes it clear that versioning is different now. Bug fixes will increment > patch version (6.0.x), WebKit updates minor version (6.1.x

Re: [Development] QtWebKit is coming back (part 2)

04.05.2017, 16:52, "Thiago Macieira" : > Em quinta-feira, 4 de maio de 2017, às 00:17:30 PDT, Jani Heikkinen escreveu: >>  > I hope for this (if possible, in 5.9 with Technology preview status >> >>  I don't think adding new TP in 5.9 at this point isn't that wise

Re: [Development] QtWebKit is coming back (part 2)

Em quinta-feira, 4 de maio de 2017, às 00:17:30 PDT, Jani Heikkinen escreveu: > > I hope for this (if possible, in 5.9 with Technology preview status > > I don't think adding new TP in 5.9 at this point isn't that wise anymore. We > have agreed to get all these new submodules (also TP ones) in

Re: [Development] QtWebKit is coming back (part 2)

03.05.2017, 17:27, "Sergio Martins" : > On 2017-05-03 15:02, Konstantin Tokarev wrote: >>  Remaining question is versioning. While it's fine to dub current >>  release "5.9" (but not 5.0, because we will have another WebKit update >>  in 5.10 time frame), using Qt

Re: [Development] QtWebKit is coming back (part 2)

; Subject: Re: [Development] QtWebKit is coming back (part 2) > > > > 03.05.2017, 18:05, "Adalid Claure" <acla...@gmail.com>: > > Does this mean that at some point this new QtWebKit would be packaged > with Qt (like in the old days)? > > I hope for thi

Re: [Development] QtWebKit is coming back (part 2)

03.05.2017, 21:25, "Thiago Macieira" : > Em quarta-feira, 3 de maio de 2017, às 10:55:49 PDT, Konstantin Tokarev > escreveu: >>  So, do you think we should update 5.6 branch of QtWebKit with wip/next >>  contents, fix qmake wrapper project to work with Qt 5.6, and

Re: [Development] QtWebKit is coming back (part 2)

Em quarta-feira, 3 de maio de 2017, às 10:55:49 PDT, Konstantin Tokarev escreveu: > So, do you think we should update 5.6 branch of QtWebKit with wip/next > contents, fix qmake wrapper project to work with Qt 5.6, and raise > requirements to whatever it can require with Qt 5.9? That's fine with

Re: [Development] QtWebKit is coming back (part 2)

03.05.2017, 20:44, "Thiago Macieira" : > Em quarta-feira, 3 de maio de 2017, às 08:03:50 PDT, Konstantin Tokarev > escreveu: >>  I'm not sure it would be acceptable, because updated QtWebKit requires full >>  C++11 support in the compiler (gcc >= 4.9, 4.8 possible with

Re: [Development] QtWebKit is coming back (part 2)

Em quarta-feira, 3 de maio de 2017, às 08:03:50 PDT, Konstantin Tokarev escreveu: > I'm not sure it would be acceptable, because updated QtWebKit requires full > C++11 support in the compiler (gcc >= 4.9, 4.8 possible with disabling some > features, or with code changes, which were not done yet).

Re: [Development] QtWebKit is coming back (part 2)

03.05.2017, 18:05, "Adalid Claure" : > Does this mean that at some point this new QtWebKit would be packaged with Qt > (like in the old days)? I hope for this (if possible, in 5.9 with Technology preview status ;) Also note that you can already get binaries compatible with

Re: [Development] QtWebKit is coming back (part 2)

Does this mean that at some point this new QtWebKit would be packaged with Qt (like in the old days)? On Wed, May 3, 2017 at 10:25 AM, Sergio Martins wrote: > On 2017-05-03 15:02, Konstantin Tokarev wrote: > >> Remaining question is versioning. While it's fine to dub

Re: [Development] QtWebKit is coming back (part 2)

03.05.2017, 17:27, "Sergio Martins" : > On 2017-05-03 15:02, Konstantin Tokarev wrote: >>  Remaining question is versioning. While it's fine to dub current >>  release "5.9" (but not 5.0, because we will have another WebKit update >>  in 5.10 time frame), using Qt

Re: [Development] QtWebKit is coming back (part 2)

On 2017-05-03 15:02, Konstantin Tokarev wrote: Remaining question is versioning. While it's fine to dub current release "5.9" (but not 5.0, because we will have another WebKit update in 5.10 time frame), using Qt versions in QtWebKit has downsides: 1. It is not clear if 5.N+1 ships with the

[Development] QtWebKit is coming back (part 2)

Hi all, A lot of time has passed since original thread [1]. Lots of work was done since then, and it took much more time than what I've originally planned, however I think now we can use updated QtWebKit as a full replacement of our previous branch that didn't have updates of WebKit engine