Earlier quoted context omitted.
License issues aside the typical use case is that you want to integrate the UI with an existing 3D renderer (e.g. you have a 3D engine, and want an UI overlay for tooling and debugging). 'Bring your own renderer' UI frameworks like Nuklear or Dear ImGui are perfect for this use case. With 'traditional' UI frameworks like Qt, WPF, GTK... this is a massive PITA and even if it's possible would add an incredible amount o…
will immediate mode keep the cpu active thus not power saving friendly?
Nuklear – A single-header ANSI C immediate mode cross-platform GUI library
51–60 of 103 posts
Re: Nuklear – A single-header ANSI C immediate mode cross-platform GUI library
#52I tend to use ImGui for testbed projects. It's flexible and quick to get up and running. I only have two minor complaints about it. 1. It would be nice to have some built in image handling functions, i.e. to be able to allocate and draw images on the screen. 2. Skinning is currently rather limited. (I know this has been a long requested feature). Other than those minor gripes, I like it a lot.
Re: Nuklear – A single-header ANSI C immediate mode cross-platform GUI library
#53Re: Nuklear – A single-header ANSI C immediate mode cross-platform GUI library
#54Does this support writing to a linear frame buffer? Would be interesting to port to run on my OS if so.
Nuklear returns a bunch of vertices, vertex-indices and draw commands, so it plugs best into a 3D API (like GL, D3D, Metal, Vulkan...). To render into a frame buffer you'd need to implement a simple software rasterizer with texturing support.
Re: Nuklear – A single-header ANSI C immediate mode cross-platform GUI library
#55Does this support writing to a linear frame buffer? Would be interesting to port to run on my OS if so.
Re: Nuklear – A single-header ANSI C immediate mode cross-platform GUI library
#56Earlier quoted context omitted.
License issues aside the typical use case is that you want to integrate the UI with an existing 3D renderer (e.g. you have a 3D engine, and want an UI overlay for tooling and debugging). 'Bring your own renderer' UI frameworks like Nuklear or Dear ImGui are perfect for this use case. With 'traditional' UI frameworks like Qt, WPF, GTK... this is a massive PITA and even if it's possible would add an incredible amount o…
will immediate mode keep the cpu active thus not power saving friendly?
Re: Nuklear – A single-header ANSI C immediate mode cross-platform GUI library
#57Interesting, this seems more resource efficient than even fltk, which is the lightest usable cross-platform GUI library. And it's pure C unlike fltk. It's great to see such projects in an era of unabashed resource consumption.
Re: Nuklear – A single-header ANSI C immediate mode cross-platform GUI library
#58Re: Nuklear – A single-header ANSI C immediate mode cross-platform GUI library
#59Nuklear is great. I’ve spent countless hours hacking around with it. I’ve also built a customized version for classic Macintosh systems (down to System 2.0 or so) and built some simple Macintosh software for it. I put it on GitHub here: https://github.com/CamHenlin/nuklear-quickdraw
Now that's just awesome - I'll definitely have to play with this! What's the performance like on low-powered CPUs?
Re: Nuklear – A single-header ANSI C immediate mode cross-platform GUI library
#60EDIT: this was flippant of me, but I was trying to make a real point.
I'm simply too used, as a front-end dev, to the flexibility I get from CSS and HTML and SVG and React, and React-Three-Fibre for fancy stuff. Put it in Electron and boom.
Yes, it's a horrible, horrible mess. Yes, it's ungainly. Yes, it's twenty layers of abstraction.
But Electron apps have come an enormous way. My favourite apps are now all Electron. While non-Electron apps make a strong start, they simply cannot keep up with the innovation made possible by here-you-go-ing the last 30 years of web progress.
Yeah, I know that's not the use case for something like this. Opposite! Opposite! But you know what? For most medium-sized 2022 front-end workloads, widgeting is a thoroughly solved problem.
By 2030, most apps will include an entire web browser, just as insurance for future market-competitive growth rate.
This is why adopting MAUI, Blazor, etc, is folly, and even this kit -- aside from it obvious hacker-cool minimalist street cred -- is the sort of 'meme dependency' (rhymes with meme stock) that HN adores despite the fact that it will see almost no non-toy use cases.
Get yourself a web browser. HTML is the VT220 of 2030.