WebKit Status 2019
-
wrote on 15 May 2019, 10:55 last edited by
Hello everyone,
I would like to know the global status of the Qt WebKit from qt pov. Is anything planned to reintegrate it as an option in qt in the next releases (qt 6 ?) ? Is it dead since 2017 ? What happened ? What is going to happen ? etc.
We work on a 300k+ loc project where a lot of things depend on the QGraphicsWebView class provided by Qt WebKit but not supported by the Qt WebEngine (source). Porting to latest qt releases is a must, but we're not even sure we can maintain our functionnalities with the WebEngine, so we have to embed qt-webkit as a third party at this time (project).
There were some beautiful ideas in this discussion and some use cases where qt WebKit seems to help where qt WebEngine cannot.
Thus, this is hard to find someone to answer these questions, so ... thanks in advance for the one who answers :)
-
Hi,
@Konstantin-Tokarev might be of help here.
-
Hello everyone,
I would like to know the global status of the Qt WebKit from qt pov. Is anything planned to reintegrate it as an option in qt in the next releases (qt 6 ?) ? Is it dead since 2017 ? What happened ? What is going to happen ? etc.
We work on a 300k+ loc project where a lot of things depend on the QGraphicsWebView class provided by Qt WebKit but not supported by the Qt WebEngine (source). Porting to latest qt releases is a must, but we're not even sure we can maintain our functionnalities with the WebEngine, so we have to embed qt-webkit as a third party at this time (project).
There were some beautiful ideas in this discussion and some use cases where qt WebKit seems to help where qt WebEngine cannot.
Thus, this is hard to find someone to answer these questions, so ... thanks in advance for the one who answers :)
wrote on 20 May 2019, 11:10 last edited byI too am very interested to know this, I wasn't even aware of the initiative. I recently picked up work for WebEngine support in Qt Assistant, as QTextBrowser doesn't cut it for us. But if WebKit is going to make a reentry then that won't be needed.
-
wrote on 20 May 2019, 12:40 last edited by
I'm currently working on updating QtWebKit to curreent WebKit. It will take some time before some early preview version can be available. Wait for announcements!
Because of limited resources there are no plans to support any operating systems besides Linux, and it won't be supported as official Qt module. However, if there is substantial community funding, these decisions will be reconsidered.
-
I'm currently working on updating QtWebKit to curreent WebKit. It will take some time before some early preview version can be available. Wait for announcements!
Because of limited resources there are no plans to support any operating systems besides Linux, and it won't be supported as official Qt module. However, if there is substantial community funding, these decisions will be reconsidered.
wrote on 20 May 2019, 14:16 last edited by@Konstantin-Tokarev Thanks for the update. We'd need support on Windows for Assistant, so I guess there is still demand for WebEngine support there. I started this thread: https://lists.qt-project.org/pipermail/development/2019-May/035920.html
-
@Konstantin-Tokarev Thanks for the update. We'd need support on Windows for Assistant, so I guess there is still demand for WebEngine support there. I started this thread: https://lists.qt-project.org/pipermail/development/2019-May/035920.html
wrote on 9 Jun 2019, 20:36 last edited by@bveelo I've managed to collect some funds, and there is backing for Windows. So, at very least functionality required for Assistant and similar applications will be available.
-
wrote on 31 Jul 2019, 08:40 last edited by
Would it be possible to pin this thread instead of the "WebKit Status 2017" ?
-
@kamui said in WebKit Status 2019:
Would it be possible to pin this thread instead of the "WebKit Status 2017" ?
Done