Changes between Version 6 and Version 7 of QtWebKitForQt5


Ignore:
Timestamp:
Jun 1, 2011 4:52:44 AM (8 years ago)
Author:
jocelyn.turcotte@nokia.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • QtWebKitForQt5

    v6 v7  
    5959when widgets and QStyle is needed.
    6060
     61----
     62Jocelyn: This is going to be painful. Beside the memory overhead, is there worthy benefits of decoupling the QWidget dependency? If possible I wish we could live with it until the need is felt.
     63
    6164=== WebGL ===
    6265
     
    8386WebProcess should be implemented in either in the QtScript library (based on V8) or another library in Qt that provides equivalent functionality.
    8487
     88----
     89Jocelyn: This is long term stuff, but since we want to have the main interface as QML from a different process than the page's JS runtime, I think we should take the time to re-evaluate the benefits of exposing the engine using the QtScript API. This was a dream we had before WebKit2 was introduced.
     90Chrome's extention are allowed to manipulate pages content using [http://code.google.com/chrome/extensions/content_scripts.html content scripts] and can communicate with the extension's script using [http://code.google.com/chrome/extensions/messaging.html messages]. Doing the same kind of stuff is one way I see how to prevent the developer from having to tediously load a C++ module in the web process.
     91
    8592=== Discussion ===
    8693noamr: I think that this is a good direction. A big question yet to be answered is how much hybrid support we need going forward with WebKit2. If we enable QML with WebKit2, do we enable the javaScriptWindowObjects property? or do we go with something a bit different like allowing communication with the container via channel messaging?