| 1 | = Direct2D WebKit = |
| 2 | |
| 3 | Brent Fulgham, Apple |
| 4 | |
| 5 | - Runs on Windows |
| 6 | - iTunes |
| 7 | - various utilities |
| 8 | - EA |
| 9 | - Sony (kind-of) |
| 10 | |
| 11 | - Uses a proprietary port of CoreGraphics |
| 12 | - off limits to anyone not at Apple |
| 13 | |
| 14 | - Wrote version in the past that uses Cairo instead |
| 15 | - doesn’t get updated as much |
| 16 | - no hardware acceleration |
| 17 | |
| 18 | - MotionMark |
| 19 | - pretty fast on Windows (IE Edge): 284 points |
| 20 | - WinCairo isn’t bad either: 166 points |
| 21 | |
| 22 | - Cairo on Windows |
| 23 | - CPU bound |
| 24 | - barely uses GPU |
| 25 | |
| 26 | - Windows 7+ has Direct2D |
| 27 | - 2D graphics library |
| 28 | - hardware accelerated |
| 29 | - supports custom GPU shaders |
| 30 | - opportunity to provide effects that aren’t easily accessible otherwise |
| 31 | |
| 32 | - Tried replacing Cairo with Direct2D |
| 33 | - only replaced basic calls |
| 34 | - no architecture changes |
| 35 | - much faster: 227 points (with rendering issues) |
| 36 | - still needs work |
| 37 | - SVG has problems (especially with text) |
| 38 | - missing a lot of implementations |
| 39 | |
| 40 | - Good path forward for Windows ports |
| 41 | - Main work is finding the edge cases where rendering has issues |
| 42 | - MotionMark has: |
| 43 | - extra arcs |
| 44 | - font handling issues |
| 45 | - SVG text problems |
| 46 | - Remaining work should be fairly small/focused tasks |
| 47 | - Very few grand architectural changes needed |