[FEATURE]I will pay you $200 USD to integrate GLFW and $200USD NUKLEAR GLFW

[DaemonDave]

Is your feature request related to a problem? Please describe.
I will pay you $200 USD to integrate a new windows system GLFW
https://github.com/glfw/glfw into your sui / GUI for Linux compilation
AND
I will pay you $200 USD to integrate the nuklear - glfw
https://github.com/m0ppers/nuklear-glfw-vulkan
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
The solution is that you know exactly where to insert the code from the GLFW into the XCB code AND
The solution is that you can know exactly where to insert the NUKLEAR shaders (or not) and shader to NUKLEAR

(BTW I have looked into 1000's of open source tarballs and your DIY makefile recipes worked out of the box on a random Linux/kubuntu and that's impressive!)

You need to prove it by making a GUI target (in Windows parlance executable) in your binaries / demo that I can understand (within reason) and where I can insert my widget codes.
You need to provide enough documentation where I would include my code to work with the nuklear main in a .c main file or an overlay.c file

My original design idea was separate frag and vertex shader as a separate pipeline but I cede to your Vulkan expertise. I don't plan on expanding or improving the SUI/GUI just exploit the NUKLEAR widget IM GUI code.

You don't need to keep any C++ code that's the stuff I tried to get rid of, I need to get away with bloated C++ code.

I would be totally OK with not using moppers texture atlas and shaders (and so on like just using yours) and just use the same ones. Please explain where you put things because I will extend the GUI code for joysticks and so on ( that work with the GLFW windows/interface) from my old code into your code.

Describe alternatives you've considered
This is my alternative to fixing it myself so I can run headless and headed servers versions on remote systems (robots) with the same libraries and same interrupts.

Additional context
I just appreciate how well you lay out your code I want to add to it but quickly rather than struggling to convert.

Please contact me by github email and I will add further if you are interested and need more. Thank you.
@DaemonDave