[webkit-qt] Ceasing development of current QtWebKit API's
sunny.cpp at gmail.com
Tue Jul 5 03:30:38 PDT 2011
Will this break QtWebkit-Bridge? If yes, then what will be the new way to
expose QObject to Java-Script, I mean what will be the alternative method of
QtWebkit-Bridge or Hybrid application development?
On Tue, Jul 5, 2011 at 1:51 AM, Andreas Kling <kling at webkit.org> wrote:
> Hello QtWebKit users and contributors!
> Now that the Nokia N9 has finally been announced, many of you probably know
> it ships with a WebKit2-based browser. Following this we've started
> discussing where to go with WebKit in Qt5, and it has become quite clear
> that the future of QtWebKit is with WebKit2.
> We at Nokia are planning to cease work on the WebKit1-based API (QWebView,
> QGraphicsWebView and friends.) We know there are many people using this API,
> and would therefore like to know if someone is interested in stepping up and
> taking over the maintenance.
> This task would include hosting a buildbot instance for build.webkit.org,
> and the responsibility for keeping unit tests (Qt/WebKit1 API tests) and
> layout tests passing.
> The rough plan is to ship the last version of our WebKit1 API's with Qt
> 5.0. We don't intend to update the code after this initial release, as its
> sole purpose is to ease migration, similarly to Qt3Support in Qt4. This will
> possibly be a forward-ported version QtWebKit 2.2 (as opposed to a snapshot
> of WebKit trunk at the time of Qt 5.0 branching.)
> If a new maintainer can be found, it's our hope that they could keep
> delivering new versions of the Qt/WebKit1 API's to the Qt 5.x series.
> -Kling (on behalf of the Nokia QtWebKit teams)
> webkit-qt mailing list
> webkit-qt at lists.webkit.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-qt