01.06.2012, в 7:18, Balazs Kelemen написал(а): >> This is of course something non-Qt developers have to worry about, see e.g. >> <https://bugs.webkit.org/show_bug.cgi?id=87783#c14>. > > This one could be avoided with the shim (in > https://bugs.webkit.org/show_bug.cgi?id=87872). We could introduce a file > called WebKitTestSupportQt.cpp that implements > injectInternalsObject(JSContextRef). It would unbox the v8 context from the > wrapper and call the v8 version of WebCoreTestSupport::injectInternalsObject. > So it's a bit complicated but at least there would be no ifdef needed in > WebKitTestRunner.
My point is that WebKit2/v8 integration is causing trouble even before it officially started to happen. That's not a good sign. Lack of support for non-webkit.org JavaScriptCore substitutes is not a weakness of WebKit2, it's a strength. The code is more hackable, tests are easier to maintain etc. - WBR, Alexey Proskuryakov
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
