Nuklear
Nuklear copied to clipboard
Immediate-Mode-UI
Gallery: post your screenshots, images, showcases, code... here
https://github.com/taiwins/twidgets
It's part of an ambitious project Taiwins (Wayland compositor, window manager, GUI library, etc.).
I started doing an updated backend xcb/cairo based on https://github.com/griebd/nuklear_xcb. I am pretty happy with it (I decoupled xcb and cairo so that both can be used independently, and cpu/mem perfs are very good for a rather desktop app kind of program) but didn't want to suggest a PR before I could implement the missing features (mostly the NK_COMMAND_RECT_MULTI_COLOR). From what I see, they did it.
Thank you for the hint :)
From what I see, they did it.
Feel free to get inspiration there and make a PR here with your backend(s) sooner or later. Thanks!
I started a little project for a ready to use pugl+cairo backend (and optional CMake). It accepts only one font at a time, but I am at the beginning :)
CadZinho - Minimalist computer aided design (CAD) software. Made with Nuklear, SDL and OpenGL (recently).
https://github.com/zecruel/CadZinho
Wow @zecruel - that looks pretty advanced to me!
If you have some blog or want to write something to our wiki, could you share some more insights how it feels to work with Nuklear in such an advanced piece of SW and what obstacles you face there and how you approach them?
Haha. Would love to consolidate a bunch of the different third-party repositories into one wiki page https://github.com/Immediate-Mode-UI/Nuklear/wiki/Awesome-Nuklear
Seems like a great space to highlight some of these
Great, thanks!
Btw. seeing all the wiki changes you did @RobLoach, I'd like to kindly ask you to take a look at https://github.com/vurtun/nuklear/pull/913#issuecomment-558565788 with the goal to identify what (if anything) is still missing and (in a separate issue, not here in this thread) maybe propose ways how to account for the deficits :wink:.
Also, feel free to add the integrations from wiki directly to the readme (I find the list very important to have it in readme and not just in the wiki). Or shall we maintain the list just in readme?
I'd like to kindly ask you to take a look at vurtun/nuklear#913 (comment) with the goal to identify what (if anything) is still missing
It is possible to transfer GitHub issues, but I'm unsure it's possible on archived repositories. An option if we want to capture any of the remaining issues.
Also, feel free to add the integrations from wiki directly to the readme (I find the list very important to have it in readme and not just in the wiki). Or shall we maintain the list just in readme?
Interesting... Maintaining a list directly in a README can slow contributions, as it does require a Pull Request and a commit. Also unsure how up-to-date they all are. But it is nice to have an initial bindings list for examples in the README :thinking:
It is possible to transfer GitHub issues, but I'm unsure it's possible on archived repositories. An option if we want to capture any of the remaining issues.
I didn't want to go that route back then because >50% of them were no more relevant. It's not a big issue any more - just if anyone cares about Nuklear and has some time to spend on it, this is the right place to start :wink:.
Also, feel free to add the integrations from wiki directly to the readme (I find the list very important to have it in readme and not just in the wiki). Or shall we maintain the list just in readme?
Interesting... Maintaining a list directly in a README can slow contributions, as it does require a Pull Request and a commit.
That's true and I agree. On the other hand I really want to have a very welcoming experience for newcomers.
What about moving the list from readme to wiki and just referencing the wiki page from a readme in this way:
Bindings and Integrations
There are 20+ Nuklear bindings for different languages and ecosystems integrations created by other authors.
https://github.com/Immediate-Mode-UI/Nuklear/wiki/Integrations
We cannot attest for their quality though. Furthermore there are no guarantees that all bindings will always be kept up to date.
Anyone is encouraged to list missing bindings and make corrections!
Thanks guy, I really appreciate that my post actually changed some things, I really hope nuklear will be known by everyone soon.
Cool thread, amazing stuff everyone's doing! I'll chip in.
video:
https://user-images.githubusercontent.com/5874861/147888034-3e4c6bf9-68db-43cd-b55c-99bc7f50fd8c.mp4
Ive been using nuklear as an editor frontend for a game engine im building. The past few weeks have been implementing nuklear for the stuff i want to be able to do fast:
- load in models for prototyping
- reload shaders & game code
- manage filesystem
- fly around my world
- debug my scene data
- and other things i really did not need (like an etalage camera) but i got carried away by how easy to use nuklear was.
Nuklear really made my life allot easier so i just want to say thanks to the devs 💯. When the UI evolves in the future ill post an update as i havent even scratched the surface of what i want to do with it.
Hello hello hello, I'm pleased to present pet, its an app to help one keep track of their daily expenses, feel free to tour, examine, contribute and make use of it :)
https://codeberg.org/limisi/pet
https://github.com/Immediate-Mode-UI/Nuklear/assets/58091631/b3d338c7-94dc-42db-b12a-58a4138ede0e
Regards, mela.
Thanks @RobLoach, guess what, its user-changeable :D (5 themes to choose from) straight from style.h :)
Added a few new features that I thought I'd show off :)
Please ignore the text content, it's all just placeholder/for testing purposes.
Using a slightly modified version of Nuklear with a custom text rendering component that handles text selection.
