This allows developers to easily expose new JavaScript APIs to WebKit, without having to change WebKit or to use a NPAPI plugin. For example, bindings to an existing C++ library could be made available in WebKit.
The high-level requirements are tracked at http://bugreports.qt.nokia.com/browse/QTWEBKIT-2
*** Bug 29877 has been marked as a duplicate of this bug. ***
*** Bug 23250 has been marked as a duplicate of this bug. ***
It is time to start, as it was discussed on dev mailing list (https://lists.webkit.org/pipermail/webkit-dev/2009-August/009610.html), it would be really great to have Qtish API over JSC. We considered all hints and suggestions and we decided to create a new QtScript like API on top of JSC's __public__ C API. We would like to start developing in the WebKit repository from the very beginning to avoid any confusion and make our development process transparent. I would like to keep the bug (31863) as a meta-bug. All other development bugs should be connected to this one as a blockers. Roadmap: 1. Create a small QJavaScript API. a) The API should provide enough functionality to be useful (run scripts, call functions, convert basic data...) b) The API implementation should be simple, all optimization work should be started after the API review 2. Change the building system - QtJavaScript and JSC should be build as a shared library (bug 27551) 3. Connect the new API to the QtWebkit API 4. Add new features
(In reply to comment #4) Previous comment is a bit outdated. We decided to not create a new API, but instead move the QtScript implementation over JSC C API. The current roadmap can be found here: http://bugreports.qt.nokia.com/browse/QTBUG-11464
This work is "paused" and we are exploring other options, more details in http://developer.qt.nokia.com/wiki/Category:Developing_Qt::Qt_Script
Porting QtScript API over JSC C API will not be continued. Bug numeber for code cleanup related work: 64088