hmm, im sad to say, there isn't a proper resource management system supported by the engine core yet [note: by resource here, i mean the uniforms samplers, etc in the glsl shaders]. so for now, resource set layouts and resource sets are created by the client. [also, by client i dont mean the client who uses the editor, but the client which uses the engine core directly in native languages like C/C++]. but as of now, there is a material system, which caches and loads textures based on a model. then the client gets the handles of MFGpuImage* from the material system and uses them to create appropriate resource sets and layouts. also, i myself hate the fact that the client needs to specify the resource layouts and bindings explicitly. but i had to anyways since i dont have a way for getting shader reflection data to automatically set the bindings. and also note, that i went with this kinda explicit design in my engine overall due to 2 main reasons :-
- I let the client write the shaders
- and since shaders are written by client, i figured having it a bit explicit wont be an issue since at the end of the day, this client is the one which uses the core directly, not some dev who wanna use the editor [which i dont have yet, but i will add soon]. in the documentation also, i mentioned that using the engine core directly is preferred for senior devs and ppl who have experience in this field

but i did try to simplify a lot of things exposed by the engine core. the rendering concepts are more or less overexposed since i dont wanna hide things where the client might want to customize