Demo headers and nk_ and design choices, oh my! about nuklear HOT 6 CLOSED

@RobLoach Apologies for not responding earlier. It's fine for the issue to remain closed.

I just wanted to mention that I was not implying that anything was missing, though if I ever do I'll happily make suggestion(s).

I'm not sure how else to explain it other than what I wrote previously.

Oh, and I am happily using the glfw demo as the basis for a current project.

from nuklear.

Hii @bolt-blue 👋
yes, they are meant to be used directly, they are kinda what glue Nuklear together with the chosen backend

You are welcomed to write your own but for the most part they are just drag and drop

Hope that clarifies the matter 👋

from nuklear.

Thanks @quadroli, that's ideal.

Might it then be recommended to not edit a copy?

Again, the main reason I ask is because then it would feel like I'm messing with the library which would generally be a bad idea.

I suppose any parts I wanted to change I would write my own code for and simply substitute those aspects.

from nuklear.

The glue code e.g. nuklear_glfw_gl4 isn't part of the library per se, you can mess with it, heck you can even mess with nuklear.h, but for the most part, it's got you covered so that literally all your messing (if not most) will be on your app, the consumer of the api ...

from nuklear.

Granted we can of course mess with the files locally, but that's asking for trouble if one wants to have an easier time of pulling potential changes.

I feel more free to edit the backend code from the various demo's.

But then, like I said before, it feels odd mainly because of the naming conventions and use of more "library-specific" macros (e.g. NK_API) and such.

Maybe I'm just overthinking, as is my wont.

from nuklear.

IF you have additions you believe are missing, feel free to suggest them. F\or the most part, they should work in your platform of choice.

from nuklear.