Qt-contributors-summit-2014-QtCS14QtWebChannel: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
=Agenda= | |||
* What is QtWebChannel | |||
* How to use QWebChannel <span class="caps">API</span> now. | |||
* How should it look like? | |||
* What is needed to make it an official module with Qt 5.4 | |||
==Feedback== | |||
* rename WebChannel.id to WebChannel..remoteId | |||
* don’t put objects into window.* by default | |||
* use “newstyle” javascript (whatever that is, waiting for feedback from Harri Porten) | |||
* remove channel arg from init callback | |||
* supply minified version of qwebchannel.js, maybe only in non-debug | |||
* error handling | |||
* aim for proper integration with QtWebKit (and in the future QtWebEngine) | |||
==Integration with QtWeb{Kit,Engine}== | |||
* make QtWebChannel a dependency of QtWeb{Kit,Engine} | |||
* move integration tests to QtWeb{Kit,Engine}, keep pure auto tests in QtWebChannel | |||
* make it easy to use: <div class="cpp-qt geshi"> | |||
*# <div class="de1">webView.<span class="me1">experimental</span>.<span class="me1">publishObject</span><span class="br0">(</span>...<span class="br0">)</span></div></div> | |||
* no ''other'' experimental features to enable (such as navigator.qt) | |||
* no custom setup required, at least on the <span class="caps">QML</span> side, possibly even on the .html/.js side | |||
==Shipping with Qt 5.4== | |||
* will be done, hopefully | |||
* repo is going to be moved to qt5 from qt-labs, renamed to qtwebchannel | |||
* other people from Digia will make sure tests etc. run. | |||
* audience is asked for review of the documentation, implementation | |||
Revision as of 14:12, 25 February 2015
Agenda
- What is QtWebChannel
- How to use QWebChannel API now.
- How should it look like?
- What is needed to make it an official module with Qt 5.4
Feedback
- rename WebChannel.id to WebChannel..remoteId
- don’t put objects into window.* by default
- use “newstyle” javascript (whatever that is, waiting for feedback from Harri Porten)
- remove channel arg from init callback
- supply minified version of qwebchannel.js, maybe only in non-debug
- error handling
- aim for proper integration with QtWebKit (and in the future QtWebEngine)
Integration with QtWeb{Kit,Engine}
- make QtWebChannel a dependency of QtWeb{Kit,Engine}
- move integration tests to QtWeb{Kit,Engine}, keep pure auto tests in QtWebChannel
- make it easy to use:
- webView.experimental.publishObject(...)
- no other experimental features to enable (such as navigator.qt)
- no custom setup required, at least on the QML side, possibly even on the .html/.js side
Shipping with Qt 5.4
- will be done, hopefully
- repo is going to be moved to qt5 from qt-labs, renamed to qtwebchannel
- other people from Digia will make sure tests etc. run.
- audience is asked for review of the documentation, implementation