lovr.data.compress/decompress

[bjornbytes]

Expose deflate since that is already used all over the place. Unsure if compression should be exposed though -- it's a lot more complicated and is currently not used for anything. Would be nice for doing project exports maybe, but in a way those are kinda better off uncompressed.

[shakesoda]

compression is really useful, strongly support exposing it. over in my voxel project compression is the difference between <100mb and gigabytes of ram usage for the same data set.

[bjornbytes]

I quite like the implementations here, stb_image can probably be told to use it and the filesystem module can also use it.

[bjornbytes]

Darn, stb_image doesn't have a built-in way of switching out its zlib implementation (only stb_image_write does)

[jimmyking2004]

I'm looking forward to this

[bjornbytes]

Do you need compression or just decompression?

[jmiskovic]

I would personally like to have both. For example, for networking.

For reading ZIPs, you can already mount them and read out the files inside.

[bjornbytes]

We already have DEFLATE decompressors for zips/pngs/etc., so those would be easy to expose. Compression would need to be added. It would be cool if lovr could create zip archives though, because then there could be a --package CLI option to create a fused build