Hi, >I should mention, though, that we require support for hardware that only >supports OpenGL ES 2.0. >If FastUIDraw can't handle this, then we would need to keep a fallback >codepath that uses Cairo, which would be unfortunate.
FastUIDraw requires features beyond what OpenGL ES 2.0 offers. With that in mind, the fall back is needed. I cannot stress how unfortunate it is to have the burden of needing to support hardware that only satisfies a specification that is nearly 10 years old and whose feature set corresponds to far more ancient times (essentially first generation DX9 cards, over 11 years ago). The jump in flexibility in handling data between ES2.0 and ES3.0/3.1 is massive. One question, what happens with WebGL 2.0 support on WebKit? I ask because WebGL 2.0 is essentially OpenGL ES 3.x for JavaScript. Best Regards, -Kevin _______________________________________________ webkit-dev mailing list [email protected] https://lists.webkit.org/mailman/listinfo/webkit-dev
