basis_universal VS canvas_ity

The author of the OP also develops Basis, which is designed to take advantage of GPU texture compression formats. GPU formats have a fixed bitrate which makes them efficient to sample but not the most efficient to transmit, so Basis layers on a second level of compression that unpacks into a GPU texture.

https://github.com/BinomialLLC/basis_universal

You might find https://github.com/BinomialLLC/basis_universal interesting :)

Erm, aren't both WebP and PNG rather useless for games? How do you convert those formats into one of the hardware-compressed texture formats consumed by the GPU (like BCx, ETC or ASTC)? Without those you're wasting a ton of GPU memory bandwidth when sampling textures.

(there are some alternatives, like https://github.com/BinomialLLC/basis_universal, or http://www.radgametools.com/oodletexture.htm)

In addition to this, texture compression is optimized for random access and has to use a fixed amount of bytes per each block, but there is a possibility to further compress this during the delivery. This is called the supercompression and Basis Universal is a good example of this. JPEG XL is also based on tiles for parallel decoding, but those tiles are too large (128x128 minimum, compare with 12x12 maximum of ASTC) so it is not yet suitable for GPU as it stands.

Im interested to see what image format specific compressors go gpu. JpegXL, AVIF, WebP... who wants to show up & throw down? Or even just fastpng?

Meanwhile we dont really hear or regard many of the gpu-oriented compression techs. TIL Basis/KTX2 is itself zstd compressed (formerly LZ apparently?). https://github.com/BinomialLLC/basis_universal

You could check out Binomial's basis_universal. After Google bought them, they open sourced it and allowed use for free.

Another alternative you should consider is https://github.com/BinomialLLC/basis_universal

Simple, open-source, standardized and supports every GPU-oriented format around. And, built-in library support for https://github.com/BinomialLLC/basis_universal

Yep. That lib is great. And, similarly https://github.com/nfrechette/acl and https://github.com/BinomialLLC/basis_universal

I have a small TTF implementation that's in the neighborhood of that size and is open source. It's part of my canvas_ity single-header library [0] that's around 2300 LOC / 36 KB object size and implements a C++ version of most of the 2D HTML5 canvas spec [1].

The core implementation of the TTF parsing and drawing is in L1526-L1846 with another small bit at L3205-L3274 of src/canvas_ity.hpp.

It's something of a toy implementation that only supports western left-to-right text, and doesn't do any hinting at all, nor kerning, nor shaping. But it's enough to draw a basic "Hello world!" using any typical TTF file.

The test suite in test/test.cpp L84-304 embeds a few custom Base64-encoded TTF files. They're small and only have a few glyphs but they do exercise a number of interesting edge cases in the OpenType TTF spec [2]. Have a look at the HTML5 port of the test suite at test/test.html in different browsers to see how their canvas implementations render those fonts.

[0] https://github.com/a-e-k/canvas_ity

[1] https://www.w3.org/TR/2015/REC-2dcontext-20151119/

[2] https://standards.iso.org/ittf/PubliclyAvailableStandards/c0...

Agreed, that sort of documentation is pure gold when done well.

It's something I always try to pay forward by doing in my own code. For example, one of my own solo projects was an STB-style single-header -like rasterizer library for C++. I started the implementation half of the library with a short outline of the rendering pipeline's dataflow and the top-level functions responsible for each stage:

https://github.com/a-e-k/canvas_ity/blob/f32fbb37e2fe7c0fcae...

https://github.com/a-e-k/canvas_ity

This is an STB-style single-header C++ library with no dependencies beyond the standard C++ library. In about 2300 lines of 78-column code (not counting blanks or comments), or 1300 semicolons, it implements an API based on the basic W3C specification to draw 2D vector graphics into an image buffer:

- Strokes and fills (with antialiasing and gamma-correct blending)

- Linear and radial gradients

- Patterns (with repeat modes and bi-cubic resampling)

- Line caps and line joins (handling high curvature)

- Dash patterns and dash offsets

- Transforms

- Lines, quadratic and cubic Beziers, arcs, and rectangles

- Text (very basic, but does its own TTF font file parsing!)

- Raster images (i.e., sprites)

- Clipping (via masking)

- Compositing modes (Porter-Duff)

- Drop shadows with Gaussian blurs

I also uncovered a number of interesting browser quirks along the way with the HTML5 port of my testing suite.

Repository: https://github.com/a-e-k/canvas_ity