Changes between Version 9 and Version 10 of QtWebKitForQt5


Ignore:
Timestamp:
Jun 6, 2011, 11:55:18 AM (14 years ago)
Author:
Simon Hausmann
Comment:

Responding to comments

Legend:

Unmodified
Added
Removed
Modified

  • QtWebKitForQt5

    v9 v10  
    8484Chrome'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.
    8585
     86Simon: I agree, C++ modules are tedious compared to script injection. A direct export-QObject-pointer-to-JS API may not make sense anymore, but for compatibility I think
     87we'll have to continue to offer that in the WebKit1 API library. That could still be done through V8 and QtScript-QObject bindings.
     88
    8689=== Discussion ===
    8790noamr: 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?
     91
     92simon: I like the idea of a channel messaging as an API, especially when on the QML side the messages could be received in "onMessageReceived:" alike signal handlers
     93and posted via QML's JavaScript.