3 | | * WebGL support is code complete but will need a lot of fine-tuning. |
4 | | * WebGL layout tests are enabled but most of them fail. |
5 | | * Is '''not''' included into the release content of QtWebKit 2.0. |
6 | | * Hardware used for testing during development: NVidia 8400GS, Intel GMA 4500HD and N900 |
7 | | * Operating systems used for testing during development: Ubuntu, Windows XP and Maemo 5 |
| 3 | WebGL can be enabled by setting {{{QWebSettings::WebGLEnabled}}} in your application. In addition, {{{QWebSettings::AcceleratedCompositingEnabled}}} needs to be enabled. For performance reasons, at the moment WebGL is scoped to work only together with accelerated compositing. For the best performance, you should use {{{QGraphicsWebView}}} with {{{QGLWidget}}} viewport. With this configuration QtWebKit is able to texture map the WebGL canvas directly. Otherwise, it has to do expensive memory copying into canvas image buffer for each frame. |
17 | | You can try out WebGL with QtTestBrowser by enabling WebGL support from the menu. For optimal performance, enable QGraphicsView with QGLWidget viewport and accelerated compositing. With this configuration, it is possible to create shared OpenGL context and framebuffer object of the WebGL viewport can be rendered with QGLWidget::drawTexture(). |
| 12 | * [Qt] When we render WebGL offscreen, color conversion cost a lot of CPU cycles |
| 13 | * https://bugs.webkit.org/show_bug.cgi?id=40884 |
| 14 | * This is important optimization for render-to-image and printing use cases. |
| 15 | * Create autotest suite Source/WebKit/qt/tests |
| 16 | * Test implementation on Symbian and fix possible defects. |
| 17 | |
| 18 | |