Hello, > So I'd like a timeline like this: > > 1) Remove Qt 4 code from trunk > 2) Branch off Qt 4 port from trunk, revert Qt 4 removal, keep merging > WebKit trunk (this is the key, continue merging trunk!) > 3) Do the QtWebKitWidgets renaming and maybe Caio can also land his font > layout test results?
I agree that this point will be the better one to make the font change for our testing infrastructure. > 4) Remove the QtScript dependency in trunk and replace the WK1 part where > we use the QScriptEngine::Ownership enum with an enum in QWebFrame (this is > source incompatible but discussed a while ago with Lars and relatively minor) Great! > 5) Branch off WebKit trunk for Qt 5.0.x, at that point also stop merging > WebKit trunk into the qt 4 branch, to ensure that both have the same WebKit > feature set. > Does that sound reasonable? Yes. I think is a good plan. Cheers, -- Caio Marcelo de Oliveira Filho openBossa @ INdT - Instituto Nokia de Tecnologia _______________________________________________ webkit-qt mailing list webkit-qt@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
