5 ms·

Nuklear doesn't have any dependency, but you must provide it a backend so it can do its drawing. The examples use a glfw3 backend, but you can provide any other

Nuklear doesn't have any dependency, but you must provide it a backend so it can do its drawing. The examples use a glfw3 backend, but you can provide any other backend, it's just a handful of functions to implement and is usually not too hard. See https://immediate-mode-ui.github.io/Nuklear/doc/nuklear.html#nuklear/api/drawing https://immediate-mode-ui.github.io/Nuklear/doc/nuklear.html...

crazypython 6y ago
Interesting. It seems like it would be fairly easy to write a WASM/Canvas2D port of it.
symlinkk 6y ago
That’s called a dependency.
enriquto 6y ago
> Nuklear doesn't have any dependency, but you must provide it a backend so it can do its drawing. The examples use a glfw3 backend, but you can provide any other backend, it's just a handful of functions to implement and is usually not too hard. The text editor gcc doesn't have any dependency, but you must provide it a backend so it can do its text editing. The example uses a nano backend written in C, but you can provide any other backend like vim or emacs, it's just a handful of functions to implement and is usually not too hard.
- dkersten 6y ago
  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.
  - enriquto 6y ago
    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.
    - liuliu 6y ago
      Dear ImGui did that: https://github.com/ocornut/imgui/tree/master/backends https://github.com/ocornut/imgui/tree/master/backends, https://github.com/ocornut/imgui/tree/master/examples 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.

crazypython 6y ago

Interesting. It seems like it would be fairly easy to write a WASM/Canvas2D port of it.

symlinkk 6y ago

That’s called a dependency.

enriquto 6y ago

> Nuklear doesn't have any dependency, but you must provide it a backend so it can do its drawing. The examples use a glfw3 backend, but you can provide any other backend, it's just a handful of functions to implement and is usually not too hard. The text editor gcc doesn't have any dependency, but you must provide it a backend so it can do its text editing. The example uses a nano backend written in C, but you can provide any other backend like vim or emacs, it's just a handful of functions to implement and is usually not too hard.

dkersten 6y ago
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.
- enriquto 6y ago
  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.
  - liuliu 6y ago
    Dear ImGui did that: https://github.com/ocornut/imgui/tree/master/backends https://github.com/ocornut/imgui/tree/master/backends, https://github.com/ocornut/imgui/tree/master/examples 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.