Well, we are really NOT maintaining a fork of webkit. Digia is. My summer project about closed when they decide to continue maintaining for some more time the Qt4/Webkit1 branch.
Regards, 2012/10/3 Alex Fiestas <[email protected]> > On Wednesday 03 October 2012 08:22:32 Lindsay Mathieson wrote: > > On Tue, 2 Oct 2012 11:32:41 PM andrea diamantini wrote: > > > QtWebkit2 is for Qt5. > > > > Also there will be major non compatible API changes. > > > > > Anyway, please consider that it is not a multiprocess solution in the > > > "chrome" sense (one process per tab), but in the "safari" one (2 > processes > > > per instance, one doing the rendering stuffs, the other one for the UI) > > > > Interesting. > > > > I'd prefer to see process per tab solutions be done at the app level > rather > > than at the toolkit. Better control and less compatibility issues that > way. > > Just to be clear, my concern is not about the "rendering out of process" or > the "multi process", my concern is having to maintain a fork of webkit. > > Web evolves super quick and we should be fast enough to be up to date. > > WebGL, html5, etc. > _______________________________________________ > rekonq mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/rekonq > -- Andrea Diamantini WEB: http://www.adjam.org rekonq project WEB: http://rekonq.kde.org IRC: rekonq@freenode
_______________________________________________ rekonq mailing list [email protected] https://mail.kde.org/mailman/listinfo/rekonq
