[Suggestion] Relocate `raylib_render_clay.zig` as part of a source instead of a project

[Logickin-Lambda]

Hi mate. While I am exploring and evaluate various gui libraries for my future projects, I have found the clay and I like the idea so much due to the simplicity, and just realized you did a binding which is awesome, and I can't wait to explore how this library work.

Nonetheless, I have some suggestions regarding the renders: The original clay library have a set of renderers located inside the library so that the can pick any backend other than raylib. In this version, seems like raylib_render_clay.zig is the zig version of clay_renderer_raylib.c.

I am wondering: Instead of including the renderer at the application level, I am thinking if putting raylib_render_clay.zig into a renderer folder at the library level (or under the /src folder of the library) a good idea such that users can pick their backend of choice by stating as an option in their build.zig file as shown (which is inspired by zgui):

const zclay_dep = b.dependency("zclay", .{
    .target = target,
    .optimize = optimize,
    .renderer = .raylib
});
compile_step.root_module.addImport("zclay", zclay_dep.module("zclay"));

Because of the lazy evaluation of zig, with the enum for choosing a renderer, we could conditionally compile the application with the chosen backend without including any other unused part of the library. This design would also be more future proof since instead of every user shipping their own renderer, they could contribute their own renderer into your project.

Edit: During waiting for fixes from another library, I am going to explore this idea to see if it is possible.

[Borwe]

Yes please, would be very handy, very much needed.

[Logickin-Lambda]

I managed to get the prototype to work, before submit that as a PR, let's do a UAT here to see if this is a good change:

https://github.com/Logickin-Lambda/clay-zig-bindings

Edit: The upgrade is based on how zgui handles multiple backends, using options from the build system and a switch to conditionally select the correct renderer for the user's requirement. To ensure clarity, dependency will be explicitly specified from your project instead of inside the library as shown:

const raylib_dep = b.dependency("raylib_zig", .{
	.target = target,
	.optimize = optimize,
});
root_module.addImport("raylib", raylib_dep.module("raylib"));
root_module.linkLibrary(raylib_dep.artifact("raylib"));

const zclay_dep = b.dependency("zclay", .{
	.target = target,
	.optimize = optimize,
	.renderer = .raylib,
});

zclay_dep.module("zclay").addImport("raylib", raylib_dep.module("raylib"));
root_module.addImport("zclay", zclay_dep.module("zclay"));

Besides, I also have only changed the raylib-sidebar-container example with the new method for loading renderer, while keeping raylib-clay-official-website example using the original implementation so that to demonstrate users can still using the old method which is good for testing their own renderer.

[johan0A]

Kinda tempted to wait for this: ziglang/zig#14288 before doing this

[Logickin-Lambda]

Sure! Considering that is a really handy feature to resolve the dependencies. I recently also have faced some dependencies problems in other projects, and solving conflicts was quite tricky, so I understand why you would prefer having that.

Thanks for showing that issue with their plan, can't wait to see if they have a good solution for it.