Re:Introduction to WebRender
by mozumder on Friday September 22, 2017 @02:18PM
(#15314459)
Not sure how useful any of this will be without a full-fledged GPU-based font renderer.
[ Parent
| on HN ]
Re:Introduction to WebRender
by robin_reala on Friday September 22, 2017 @02:25PM
(#15314515)
You’re in luck: https://pcwalton.github.io/blog/2017/02/14/pathfinder/
As HN resident pcwalton says: “The immediate next step for Pathfinder is to integrate into WebRender as an optional accelerated path for applicable fonts on supported GPUs.”
For normal web pages, rasterization of fonts is not a big deal. This is obviously not the case when projected into VR.
WR rasterizes glyphs into font atlases and uploads those to the GPU. Those atlases are cached for use later and can be selectively updated if need be.
We also are working on path rasterization on the GPU with Pathfinder, so that will handle the other use cases plus things like SVG.
You can get really far without actually doing GPU rasterization of fonts with just a basic glyph texture atlas.
This, for example, is how Android deals with this ( https://medium.com/@romainguy/androids-font-renderer-c368bbd... )
pcwalton is on the ball, as usual: "Pathfinder is a fast, practical GPU-based rasterizer for OpenType fonts" (and written in Rust) https://github.com/pcwalton/pathfinder
Skia isn't GPU-accelerated enough? It's what Chrome uses too right?
Re:Introduction to WebRender
by yazaddaruvala on Saturday September 23, 2017 @01:04AM
(#15318231)
I'm sure the future blog posts will have more details, but it has to do with immediate mode vs retained mode APIs.
Re:Introduction to WebRender
by binarycrusader on Friday September 22, 2017 @03:14PM
(#15314922)
They have one, but there's also Eric Lengyel's http://sluglibrary.com