A look at pathfinder
nical.github.io
A look at pathfinder
1–10 of 13 posts
Re: A look at pathfinder
#2Main author of Pathfinder here--feel free to ask any questions. :)
Thanks to Nical for the excellent writeup!
Re: A look at pathfinder
#3So if I read this correctly, it's an algorithm that Firefox could use when it handles the HTML canvas tag. For instance to draw SVG or text. Is that correct? And the good thing here, is that it uses GPU instructions to determine occlusion, and thus speed up the drawing process.
What I don't get: if that's the case, shouldn't it be integrated at a lower level, i.e. not just for drawing SVG or text, but the whole of the canvas tag? Because that's where occlusion also could take place?
Re: A look at pathfinder
#4So if I read this correctly, it's an algorithm that Firefox could use when it handles the HTML canvas tag. For instance to draw SVG or text. Is that correct? And the good thing here, is that it uses GPU instructions to determine occlusion, and thus speed up the drawing process. What I don't get: if that's the case, shouldn't it be integrated at a lower level, i.e. not just for drawing SVG or text, but the whole of th…
Yes, it would make sense to use Pathfinder for canvas as well. Some care is necessary to avoid regressing apps that read canvas data back from GPU to CPU frequently, to avoid thrashing the I/O bus, but in general it should be doable.
In fact, Pathfinder offers a subset of the HTML canvas API which you can use in your Rust apps right now. Here's an example: https://github.com/pcwalton/pathfinder/blob/master/examples/...
Re: A look at pathfinder
#5Main author of Pathfinder here--feel free to ask any questions. :) Thanks to Nical for the excellent writeup!
My previous (rather limited) understanding of Pathfinder was that it was just a text renderer, I didn't realize that it was a more general vector graphics package. Is the idea for Pathfinder that it should be integrated into Firefox for all its vector rendering needs (SVG and so forth)?
Re: A look at pathfinder
#6Main author of Pathfinder here--feel free to ask any questions. :) Thanks to Nical for the excellent writeup!
Is there still a need to cache results in a texture or is it practical to render from scratch each frame?
Re: A look at pathfinder
#7crowded namespace
Re: A look at pathfinder
#8Main author of Pathfinder here--feel free to ask any questions. :) Thanks to Nical for the excellent writeup!
Is there still a need to cache results in a texture or is it practical to render from scratch each frame?
If you know that the result will not change over frames, blitting a cached image will always be faster than re-rendering.
It's not necessarily a need, just an improvement. That said pathfinder is fast enough already that it can deal with rendering interesting workloads every frames at 60fps, and will keep getting better at it, I think that there is room for improvement in the tiling phase.
Re: A look at pathfinder
#9Main author of Pathfinder here--feel free to ask any questions. :) Thanks to Nical for the excellent writeup!
[deleted]
Re: A look at pathfinder
#10Main author of Pathfinder here--feel free to ask any questions. :) Thanks to Nical for the excellent writeup!
Does this do proper linear (rather than gamma-encoded) compositing / anti-aliasing?
If so, do people get mad that their fonts look a bit lighter than existing rasterization tools which (incorrectly) work in gammma-encoded color space?