| Version 1 (modified by , 11 years ago) (diff) |
|---|
WebKit Coordinated Graphics System
Qt, TextureMapper, TiledBackingStore, UI_SIDE_COMPOSITING and friends.
Background
A good reading before reading this is the following from Chromium: http://www.chromium.org/developers/design-documents/gpu-accelerated-compositing-in-chrome/
This explains in detail the difference between standard rendering in WebCore and the accelerated compositing code path. Without understanding of the difference, the rest of this document might not be very useful.
Other blog posts that can help: Qt scenegraph: http://labs.qt.nokia.com/2010/05/18/a-qt-scenegraph/ Reasons for going with TextureMapper rather than QGraphicsView etc., and could help understand our progress on the subject in the last 2.5 years: http://labs.qt.nokia.com/2010/05/17/qtwebkit-now-accelerates-css-animations-3d-transforms/ http://qtwebkit.blogspot.com/2010/10/texture-mapper-accelerated-compositing.html http://labs.qt.nokia.com/2011/11/10/qtwebkit-accelerated-compositing-report/
Attachments (2)
- Qt, TextureMapper and Coordinated Compositing.png (70.6 KB) - added by 11 years ago.
- CoordinatedGraphicsSystem.svg (293.4 KB) - added by 11 years ago.
Download all attachments as: .zip
