Yesterday I was playing with the threaded compositor again. The major issue form the usability point of view was the lack of scrollbars, but now we have overlay scrollbars implemented. So, the remaining issues are bugs and missing features (if any). Everything works much better now than when I tried during the web engines hackfest, so we are indeed a lot closer. But there are still issues that need to be fixed, some of them as important as the inspector not working at all. I created a meta bug[1] yesterday and made exiting bugs block it and created a few others also blocking the meta bug. Please, make any other bug block the meta and file new bugs blocking the meta for any other issue or feature missing that you know of.
The threaded compositor is only the first step in the global graphics plan we were discussing about during the hackfest. I think we should switch to the threaded compositor (and async scrolling) for 2.14. For that, I think it's important to fix the major issues ASAP and switch to use threaded compositor in trunk as soon as possible after branching for 2.12. That way we have the whole cycle to fix issues and adopt async scrolling as well. The next step would be moving the compositor to the UI process, but we could leave that for the next cycle, unless things go very well after switching to threaded compositor and we have time to do it in the same release cycle. What do you think? Do people involved in threaded compositor have time to work on it? [1] https://bugs.webkit.org/show_bug.cgi?id=154066 -- Carlos Garcia Campos http://pgp.rediris.es:11371/pks/lookup?op=get&search=0xF3D322D0EC4582C3
signature.asc
Description: This is a digitally signed message part
_______________________________________________ webkit-gtk mailing list [email protected] https://lists.webkit.org/mailman/listinfo/webkit-gtk
