This is great news, although I really wish it would have come sooner as we have spent a significant amount of time getting Chromium Embedded Framework (CEF) to play nice with our Qt application in the past months. One thing that I wonder though: Does this mean that the Qt WebEngine will stay more up to date? Because the old QtWebkit was lagging pretty far behind and for instance didn't get HTML5 support until very re…
Introducing the Qt WebEngine
11–20 of 37 posts
Re: Introducing the Qt WebEngine
#12Re: Introducing the Qt WebEngine
#13What's going to happen to wkhtmltopdf and phantomjs ?
Re: Introducing the Qt WebEngine
#14This is really interesting, because whilst Qt Webkit was a fantastic effort it had some quirks. Last project I was working on used Qt Webkit to provide a basic browser, so there was lots of fun with flash player integration, Javascript going awry and so on, if they're relying on Chromium to act as the core it should remove a lot of those headaches for developers and allow them to build on top of it much easier. Defin…
The worst part (at least for where I work) of using Flash in QtWebView was the non-availability of a license to just include the flash .dll in our application distribution.
Re: Introducing the Qt WebEngine
#15This is really interesting, because whilst Qt Webkit was a fantastic effort it had some quirks. Last project I was working on used Qt Webkit to provide a basic browser, so there was lots of fun with flash player integration, Javascript going awry and so on, if they're relying on Chromium to act as the core it should remove a lot of those headaches for developers and allow them to build on top of it much easier. Defin…
Since Chromium doesn't support flash (that is one of the closed source bits added to Chrome), I suspect that while QTWebKit had fun with flash integration, Qt WebEngine will probably make Flash integration impossible. The worst part (at least for where I work) of using Flash in QtWebView was the non-availability of a license to just include the flash .dll in our application distribution.
Re: Introducing the Qt WebEngine
#16Can someone provide a simplified summary?
There were various other reason for following Blink and honestly the day Blink came out I would be shocked if there hadn't been meetings in every company contributing to WebKit putting together a mini-project to decide if they should follow Google. There were a lot of little pain points in the WebKit project and Google in one swoop cleaned up a ton of them. If anything I see WebKit as an example of failing to steward an open source project on the part of Apple or the community as a whole. Everyone was working on their own problems that it was hard to get movement to fix bigger problems that applied to all ports. Even very visible things like letting each port have their own build system sounded good originally, but was one of the things holding the project back. I was on the edge of the community (worked on the qtwebkit port, helped port chrome to linux, ce port, blackberry port, etc) so I know only so much, but it would be interesting to hear from someone closer in the community not about what was bad technically in the project, but how as an project we (socially?) didn't fix them. Why didn't the WebKit meetings fix this? Did Apple have too much say because they owned the svn server to the detriment of themselves?
Re: Introducing the Qt WebEngine
#17This is really interesting, because whilst Qt Webkit was a fantastic effort it had some quirks. Last project I was working on used Qt Webkit to provide a basic browser, so there was lots of fun with flash player integration, Javascript going awry and so on, if they're relying on Chromium to act as the core it should remove a lot of those headaches for developers and allow them to build on top of it much easier. Defin…
Since Chromium doesn't support flash (that is one of the closed source bits added to Chrome), I suspect that while QTWebKit had fun with flash integration, Qt WebEngine will probably make Flash integration impossible. The worst part (at least for where I work) of using Flash in QtWebView was the non-availability of a license to just include the flash .dll in our application distribution.
The Chrome PPAPI Flash Player works perfectly on Chromium and the binary can be shipped separately.
Re: Introducing the Qt WebEngine
#18Re: Introducing the Qt WebEngine
#19Re: Introducing the Qt WebEngine
#20A little bit off topic, but I'm glad Qt didn't end up at Microsoft.