Hey folks!
Version 0.10.0 has been released. This is a small release before the new year, and includes hairline support, in addition to some very small API changes.
You can check out the changelog at: https://github.com/vancluever/z2d/blob/v0.10.0/CHANGELOG.md
Thanks!
Does anyone have advice on using z2d with SDL3? Getting a bit lost in the details since I’m new to Zig, z2d and SDL.
I’m trying using the 7Games/zig-sdl3 wrapper but an example using another wrapper, calls to the SDL C functions or even just a description would be helpful.
It seems like the general gist is:
Am I on the right track?
@g4b3 you have the right approach! If you know you’re always going to be working with said surface/texture memory exclusively, you might want to look into how you can just map the memory directly, and then use Surface.initBuffer so you can just render directly to it, and save yourself some copying.
Happy to answer any other questions!
Hey folks, 0.11.0 was released last week.
Release notes can be found at https://github.com/vancluever/z2d/blob/v0.11.0/CHANGELOG.md
This was mainly released to support Zig 0.16.0. 0.12.0 will probably follow soon for Zig 0.17.0, after it’s released.
Thanks!
Hey folks, 0.12.1 was released yesterday!
This was another small release, but with a novel feature, path effects!
Path effects is the informal term I’m giving to ungrouped functions in in z2d.Path that all have one thing in common: they all mutate the supplied path, returning a new one with a particular effect applied.
The first two functions of this type are complementary of each other: Path.simplify and Path.offset.
Path.simplify takes a path and returns non-intersecting outlines. An easy way to illustrate this would be a 5-point self-intersecting star, and simplifying that to just be the outline:
This will also split self-sealing paths up into separate closed paths (think something along the lines of creating two triangles with a single closed path).
Path.offset allows one to create a new path with an inset (negative offset) or outset (positive offset). This allows for easy effects off of a single path:
This can also be used to apply offsets to an open path, which is used in Ghostty to ensure certain stroked glyphs can fit in a cell while still being aligned to the cell bounds.
The only requirement for offset is that the path is not self-intersecting (for which you can use Path.simplify to get a simplified path).
Context path effectsLike most other functionality in z2d, both path effect functions have corresponding functions in Context, those functions being Context.simplifyPath and Context.offsetPath. These functions replace the current context-managed path with the result of the operation.
You can get more details on how to apply Path.simplify and Path.offset in the acceptance test from which the above images were taken! This acceptance test uses the Context variants, demonstrating the higher-level, managed versions of these functions.
Full release notes are here, including a couple of additional bug fixes: https://github.com/vancluever/z2d/blob/v0.12.1/CHANGELOG.md
Just wanted to say that I’m a happy user of z2d. I use it extensively for the CPU renderer of a linux desktop app framework I work on in my spare time. I really like your build.zig.zon’s .dependencies field, which is… nothing. 
I made some local modifications (as I always vendor my dependencies) to text rendering, mostly consisting of introducing a glyph cache to improve performance on text heavy workloads. The well structured code really helped with that.
Just for your information, I can’t wait for you to tackle Surface patterns! This will unlock a lot of features, especially if you implement a nice set of image scaling algorithms.
Thank you for maintaining this library and for keeping it pure zig and dependency free.