On 12/06/2012 03:07 PM, Jocelyn Turcotte wrote:
Ok, I'm not aware of this kind of use case being on the roadmap. The only way I could see this being possible in the near future would be that you allow only one WebView to load at a time, and that we add some WKCookieManager* alike API to reset the cookies each time you want to show a different account.
That could be done, yes.
The backend of WebKit2 is still moving a lot. For example with Apple currently doing work to have all the networking done in a separate NetworkProcess, to allow multiple WebProcesses. It's difficult to see a way to expose the QNetworkAccessManager in the public API the same way that it is with WebKit1.
The only way I can see to achieve what I need (actually our current implementation can do even more, like executing javascript code to prefill form fields and press the submit button) is to make WebProcess a simple tiny binary and move all its functionality into a library (maybe having an API as close as possible to WebKit1); then one could make one's own WebProcess implementation, if the WebView had an API which allowed selecting the WebProcess binary to execute.
Do you think that the above might make sense, or am I missing some important details?
Ciao, Alberto _______________________________________________ webkit-qt mailing list webkit-qt@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-qt
