Things like that will probably have to be done using a plugin for the web process. We haven't worked on this yet.
It will take time for this to be used as a in place replacement for WebKit1 API's, so most people will probably want to stick to our old API for the time being. Kenneth On Sun, Jul 3, 2011 at 8:32 AM, Andrea Diamantini <[email protected]> wrote: > Hi all, > I checked a bit the API proposal and I'm a bit "disoriented" by the changes > against previous APIs. > For example, in KDE we base our webkit integration on the QWebPage class, in > particular on the methods "setNetworkAccessManager" and > "acceptNavigationRequest". > How can the same be achieved in this new solution? > > Probably (or not) out of contest, the same is true with the actual QML > WebView element. Am I missing something? > > Cheers, > > -- > Andrea Diamantini, adjam > GPG Fingerprint: 57DE 8E32 7D1A 0E16 AA52 59D8 84F9 3ECD DBF9 730F > > rekonq project > WEB: http://rekonq.kde.org > IRC: rekonq@freenode > > _______________________________________________ > webkit-qt mailing list > [email protected] > http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt > > -- Kenneth Rohde Christiansen Senior Engineer Application and Service Frameworks, Nokia Danmark A/S Phone +45 4093 0598 / E-mail kenneth.christiansen at gmail.com http://codeposts.blogspot.com ﹆﹆﹆ _______________________________________________ webkit-qt mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
