[ozone/wayland] Gardening: move buffer management into own class.
This is a preliminary work before introducing frame and presentation callbacks. Summary: It's too much for WaylandConnection to hold that much functionality. Instead, move the buffer management mechanism to its own WaylandBufferManager class. It's mostly moving code around with no functionality changes except that CreateBuffer, SwapBuffer and DestroyBuffer return the result of their job. On false, an error message is set and WaylandConnection uses it when calling TerminateGpuProcess. In followup CLs, I will make the buffer management easier. That will allow us to use frame callbacks in quite a nice way. Bug: 820047 Change-Id: Ib64d4d5d3e4c64bd7e95154e8d280509bbdac8b6 Reviewed-on: https://chromium-review.googlesource.com/1179835 Commit-Queue: Maksim Sisov <msisov@igalia.com> Reviewed-by:Robert Kroeger <rjkroege@chromium.org> Reviewed-by:
Antonio Gomes <tonikitoo@igalia.com> Cr-Commit-Position: refs/heads/master@{#586201}
Showing
This diff is collapsed.
Please register or sign in to comment