| | 1 | - Accelerated Compositing |
| | 2 | - 3D Canvas |
| | 3 | Solutions are currently pretty separate |
| | 4 | |
| | 5 | - Accelerated 2D canvas |
| | 6 | Google's solution upstreamed (Skia/NC), still profiling |
| | 7 | Currently hybrid mode, would work better in full HW mode - not with read-backs. |
| | 8 | should canvas-2d have a "no-readback" mode or other rendering hints? |
| | 9 | Not turned on by default - correctness issues |
| | 10 | |
| | 11 | - How does this jive with WebKit2/multi-process |
| | 12 | Chromium - a 3rd GPU process that handles all the OpenGL commands and embeds a window into the front process |
| | 13 | Qt - marshal the graphics-layer commands; RIM does something similar |
| | 14 | Apple - CA on Mac, shared-textures on Windows (not complete yet) |
| | 15 | |
| | 16 | - Differences between ports |
| | 17 | |
| | 18 | |
| | 19 | - GPU for regular rendering (?) |
| | 20 | |
| | 21 | - SVG acceleration |
| | 22 | Context switching |
| | 23 | relies on GPU for regular rendering? |
| | 24 | |
| | 25 | - 3D CSS without acceleration |
| | 26 | Makes some sense; not a huge traction. |
| | 27 | |
| | 28 | - what's composited |
| | 29 | fixed position? |
| | 30 | should everything be render-layers? |
| | 31 | texture-limit |
| | 32 | |
| | 33 | - is something in the acceleration/animation API layer missing |
| | 34 | animation scrubbing - mostly for authoring tools |
| | 35 | interesting area: requestAnimationFrame |
| | 36 | |
| | 37 | - transitions/animation CSS |
| | 38 | last addition was fill-mode |
| | 39 | |
| | 40 | - let the web developers decide? |
| | 41 | Makes sense on some level since developers do translateZ(0) and other tricks anyway. |
| | 42 | In Qt we sometimes interpret accelerated-compositing as pure software, in memory constrained environments. |
