[webkit-qt] Webkit and webkit2

[Jocelyn Turcotte]

Hi Sylvain,

This might take some time, but we will eventually need some way to exchange data between wrapping applications and the web content.
It might not be as powerful as QWebElement was, but it should cover most use cases for those distributing and controlling both the web content and the wrapping C++/QML application.

See also No'am's post about the subject: http://labs.qt.nokia.com/2011/08/31/an-oldnew-approach-to-qtwebkit-hybrid/

I think that WebKit1 offers few advantages over WebKit2 as a platform web view, especially from a user experience and stability point of view. Of course there will always be cases where WebKit1 will feel more adapted, but we'd like to see the list of those cases to shrink over time as WebKit2's advantages start weighting more (especially with the Qt5 scene graph).

Having multi processes should bring only a reasonable overhead and, if this becomes a problem, we keep the possibility of working on getting the web "process" spawned in a thread instead.

I hope this clears it a bit,
Jocelyn


On Tue, 24 Jan 2012 18:09:10 +0100
ext Sylvain Pointeau <sylvain.pointeau at gmail.com> wrote:

> Dear webkit team,
> 
> I know that you are moving from single thread webkit1 to multi-processes
> webkit2.
> I also know that starting from webkit2 it will not be possible to query the
> dom (like with QWebElement) etc
> Also I know you are working hard to re-design those possibilities.
> 
> I understood that you are moving for a better user experience.
> 
> but recently using cocoa and objective-C, I also used their web view
> component.
> and it is based on webkit1. (but safari is based on webkit2)
> 
> I was wondering if it make sense to embed a multi-process webkit component
> into an application that is not a browser?
> will it be not too much resource demanding?
> also clearly we loose the easy way it was to modify/query/etc the dom/others
> 
> Is webkit1 (not QtWebkit but webkit1) becoming deprecated soon?
> 
> I am not sure I understand the move to webkit2.... neither webkit2 in
> general (for me much more for the browser implementers)
> 
> Best regards,
> Sylvain