Nuklear

I'm working on better UI for my app AutoPTT [1]. It's probably going to look somewhat similar to Discord's settings, except I won't be using Electron. I refuse to use bloated stuff like that, so I'm going to keep using a pure C UI library [2]. Obviously this is going to take a bit more work but at least the resource usage will stay low, which I consider quite important. Especially since gamers are a large portion of the user base. [1] https://autoptt.com/ [2] https://github.com/Immediate-Mode-UI/Nuklear

I've created a similar (minimal, lightweight, ANSI C) UI library, which is even easier to use. https://gitlab.com/bztsrc/smgui I don't like immediate-mode, because you must handle everything in the same thread, so mine is a state-mode GUI. For immediate-mode and ANSI C, there's also Nuklear: https://github.com/Immediate-Mode-UI/Nuklear This latter has all the bells and whistles.

Immediate mode UI toolkits are designed for pluggable backends, some even can discover the appropriate backend at runtime. If you're writing a game, you're expected to (and actually, you must) build your own integration. ImGUI and Nuklear each have 20+ backends in their repos: <https://github.com/ocornut/imgui/tree/master/backends> <https://github.com/Immediate-Mode-UI/Nuklear/tree/master/dem...>

The one big downside I see is that if you want to actually work on the library itself, it's a pain to have to re-compile the entire thing every time you change something. Nuklear (https://github.com/Immediate-Mode-UI/Nuklear) uses separate files with a deploy script that combines them all into a single header; I think that approach is quicker for iterating on the code.

What about Nuklear? https://github.com/Immediate-Mode-UI/Nuklear

> And for the right project, especially those where a predefined engine structure does not not fit, it can still be the most productive choice. Right on. While interning at an oil refinery, I developed an application in LÖVE that processes and displays data from spectrometers. In hindsight it may not have been the wisest choice, but hand rolling all the GUI elements I couldnt force out of the Nuklear[0] bindings for LÖVE gave me a strange sense of satisfaction. [0]: https://github.com/Immediate-Mode-UI/Nuklear

As others have pointed out, you don't need to write extra .c files, and you won't bloat the obj files. This paradigm is fairly common, see, e.g.: https://github.com/lieff/minimp3 https://github.com/Immediate-Mode-UI/Nuklear https://github.com/mattiasgustavsson/libs/blob/main/docs/htt...

Hello HN. I made this Windows desktop app that allows using voice activation with games or apps that only support push-to-talk. The initial version was written years ago, without any UI or configuration options. It was just for my personal use. I had told a few friends about it, though, and then one of them asked if he could get a copy to use with Discord priority speaker, since for years, it has only worked with push-to-talk. So I spent some time making a more user-friendly version. It's written almost exclusively in C and uses Nuklear [1] for the UI. It has an auto updater. The releases are hashed with BLAKE3 and signed with ECC. I also recently made an open source USB device [2] that the app can use to send input from a "real" keyboard because, it turns out, there are some games (CSGO) that ignore simulated input for activating the mic

Hello HN, author here. I wrote a command line version of this app several years ago but it was only recently that I decided to make a more user-friendly version when a friend grumbled about how the priority speaker function in Discord would be really useful if it supported voice activation. So I said I could probably help with that, and a few weekends later, this was the result. It's written in C11 with just a sprinkle of C++. The UI uses Nuklear [1] with a DirectX 11 renderer. [1] https://github.com/Immediate-Mode-UI/Nuklear

Everyone is in the mood to write about text rendering today for some reason, love it. Great to see so many points paralleled like this article talking [1] about sub-pixel offsets being a challange and Nuklear's Wiki article talking [2] about snapping glyphs to an interger offset. [1] https://gankra.github.io/blah/text-hates-you/#subpixel-offse... [2] https://github.com/Immediate-Mode-UI/Nuklear/wiki/Complete-f...

Like all frameworks, which are barebones libraries wrapped in opinionated organization, KDE/QT can be a lot when you need a simple UI. I’ve used Nuklear to make simple, portable, UIs: https://github.com/Immediate-Mode-UI/Nuklear Everything has trade offs; I might need to come up with my own way of handling some bit of state, but my projects aren’t big enough to need the software equivalent of a Costco.