Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The difference is that its up to you to provide the backend, so presumably you will be using whatever you're application is already using, rather than pulling in a new dependency just for Nuklear to work.

Its still a dependency in my books, but its not the same as saying "this requires DirectX" or whatever: it requires a backend, but you can give it any backend you want, so ideally wouldn't pull in anything you aren't already using.



I would believe you if Nuklear provided several (say, at least 5) different such backends, easily accessible through different makefiles, say

    Makefile.glfw3
    Makefile.freeglut
    Makefile.gtk
    Makefile.x11
    Makefile.cocoa
Since it is just a handful of lines, that should be easy to do :) Also, it would be a great way to learn how to add new backends.

But as it is now, it is presented to be like glfw3 is a hard dependency.


Dear ImGui did that: https://github.com/ocornut/imgui/tree/master/backends, https://github.com/ocornut/imgui/tree/master/examples You can probably borrow some of these code and fit with Nuklear.

For these imgui toolkit, it is just a few lines of code if you know what you are doing. For the library authors, it is quite a bit of work to maintain different environments and CIs to test all these backends though.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: