Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MicroUI – A tiny, portable, immediate-mode UI library written in ANSI C

github.com

Post reply on HN
Print view View original

71–80 of 91 posts

Re: MicroUI – A tiny, portable, immediate-mode UI library written in ANSI C

#71

Post by onsclom »

Narishma wrote: post #69
onsclom wrote: post #68

Earlier quoted context omitted.

I made my own WASM demo @ https://microui-wasm.vercel.app/ and it's only 14.6 kB compressed! Will share source code if someone is interested, but key bits: - had a small JS glue layer using CanvasRenderingContext2D to render - made a `wasm32-freestanding` build to lower the wasm bundle size, which meant shimming the bits of the libc microui uses

Your demo seems to constantly consume 100% CPU at all times.

Ooh interesting. What is your machine and browser? On chrome with my m1 macbook it takes less than 1ms to compute and render each frame, but I am noticing some things I can optimize from the performance flame graph! I will say, I find chrome to be way more efficient for ctx2d things than firefox or safari.

Re: MicroUI – A tiny, portable, immediate-mode UI library written in ANSI C

#72

Post by 0x0203 »

Narishma wrote: post #70
0x0203 wrote: post #63

For a slightly larger, cross-platform, retained mode GUI written in C, there's libagar [0]. Different use case than MicroUI, but still a neat project. [0] https://libagar.org/

If that's your project, the Arabic text rendering is broken in this screenshot: https://libagar.org/screenshots/agar171.png

It's not mine; just a project I've toyed with a few times in my search for GUI toolkits over the years. Issues and/or PRs can be filed on the github page though.

Re: MicroUI – A tiny, portable, immediate-mode UI library written in ANSI C

#73

Post by pstuart »

packetlost wrote: post #27
kartoffelsaft wrote: post #15

This has been my goto for personal toy projects for a while now. Trivial to slot in to basically anything that can display text and takes mouse input. I will mention, however, it's kinda abandonware at this point. There is some bug with the draw call iterator which does a misaligned pointer access, which, if your environment is set up to catch that, can get annoying (Zig for example panics on it). There's a github is…

> it's kinda abandonware at this point That's sad. I'm a fan of rxi's work, including this one.

It's MIT and these days handing it off to Claude to tart it up as needed should be viable.

Re: MicroUI – A tiny, portable, immediate-mode UI library written in ANSI C

#74

Post by starik36 »

flohofwoe wrote: post #29

I wrote a little demo to run microui on top of the sokol headers here, it's really interesting in how minimal it is. WASM demo: https://floooh.github.io/sokol-html5/sgl-microui-sapp.html Source code: https://github.com/floooh/sokol-samples/blob/master/sapp/sgl... The renderer backend is just a bunch of C functions you need to provide: https://github.com/floooh/sokol-samples/blob/3f4185a8578cd2b... It's also interesti…

Why is the WASM demo so fuzzy? I am on Windows/Firefox.

https://imgur.com/uy78t52

Re: MicroUI – A tiny, portable, immediate-mode UI library written in ANSI C

#75

Post by Narishma »

onsclom wrote: post #71
Narishma wrote: post #69

Earlier quoted context omitted.

Your demo seems to constantly consume 100% CPU at all times.

Ooh interesting. What is your machine and browser? On chrome with my m1 macbook it takes less than 1ms to compute and render each frame, but I am noticing some things I can optimize from the performance flame graph! I will say, I find chrome to be way more efficient for ctx2d things than firefox or safari.

Firefox on Linux.

Re: MicroUI – A tiny, portable, immediate-mode UI library written in ANSI C

#76

Post by Intralexical »

starik36 wrote: post #74
flohofwoe wrote: post #29

I wrote a little demo to run microui on top of the sokol headers here, it's really interesting in how minimal it is. WASM demo: https://floooh.github.io/sokol-html5/sgl-microui-sapp.html Source code: https://github.com/floooh/sokol-samples/blob/master/sapp/sgl... The renderer backend is just a bunch of C functions you need to provide: https://github.com/floooh/sokol-samples/blob/3f4185a8578cd2b... It's also interesti…

Why is the WASM demo so fuzzy? I am on Windows/Firefox. https://imgur.com/uy78t52

Looks like the rendering functions used in the demo are doing antialiasing without font hinting?

Re: MicroUI – A tiny, portable, immediate-mode UI library written in ANSI C

#77

Post by pkolchanov »

ur-whale wrote: post #4

Nice, except the hard part seems to be missing: interfacing with an actual window system (X11, TUI, WIN32, whatever ...)

I've worked on a minimal application layer (Cocoa, X11, win32) that you might find interesting. It includes a microui example.

https://github.com/pkolchanov/brr

Re: MicroUI – A tiny, portable, immediate-mode UI library written in ANSI C

#78

Post by socalgal2 »

flohofwoe wrote: post #29

I wrote a little demo to run microui on top of the sokol headers here, it's really interesting in how minimal it is. WASM demo: https://floooh.github.io/sokol-html5/sgl-microui-sapp.html Source code: https://github.com/floooh/sokol-samples/blob/master/sapp/sgl... The renderer backend is just a bunch of C functions you need to provide: https://github.com/floooh/sokol-samples/blob/3f4185a8578cd2b... It's also interesti…

I asked Claude to write one from scratch. A few minutes later it was done with exactly the features I needed. I started with some existing one, but when it couldn't handle multiple pointers (2 hands in VR/AR each with a pointer) without major mods I end up asking Claude if it could replace it with a custom one.

It first said "that's a ton of work" to which I said, "Really? A basic IMGUI needs a texture with glyphs. The abiltiy to draw textured rectangles with vertex colors. Scissor support for clipping. Some hit testing." and it was like, "yea, you're right", and a few mins later it wrote what I needed.

I'm not saying you shouldn't use this library.

Re: MicroUI – A tiny, portable, immediate-mode UI library written in ANSI C

#79

Post by SwellJoe »

Intralexical wrote: post #65
SwellJoe wrote: post #47

Earlier quoted context omitted.

OK, if "toy project" isn't the right word, then perhaps, "unethical" or "exclusionary" would be better words to use. I judge software harshly that could be useful to folks with accessibility needs that don't try to address it (within bounds of their resources and capabilities, obviously lots of OSS just doesn't have the ability to deliver an accessible experience for tiny little throwaway apps). I definitely choose t…

> I guess a lot of folks consider games exclusively for folks without those accessibility needs, so maybe that's why something like Dear ImGui can live for years in thousands of projects without anyone complaining about accessibility. But, I wouldn't consider it for anything that isn't specifically about graphics and I don't think anyone else should either. (No one has to listen to me, but I think less of them.) Imme…

Literally none of the examples of large companies using it in the comment I replied to are game companies or using it for game debug menus.

You made up a guy and pretended I was yelling at them.

Re: MicroUI – A tiny, portable, immediate-mode UI library written in ANSI C

#80

Post by flohofwoe »

starik36 wrote: post #74
flohofwoe wrote: post #29

I wrote a little demo to run microui on top of the sokol headers here, it's really interesting in how minimal it is. WASM demo: https://floooh.github.io/sokol-html5/sgl-microui-sapp.html Source code: https://github.com/floooh/sokol-samples/blob/master/sapp/sgl... The renderer backend is just a bunch of C functions you need to provide: https://github.com/floooh/sokol-samples/blob/3f4185a8578cd2b... It's also interesti…

Why is the WASM demo so fuzzy? I am on Windows/Firefox. https://imgur.com/uy78t52

TL;DR: it can be all sorts of things, from 'half-pixel' positioning problems, to upscaling issues, to poor source data. I didn't put too much effort into getting the text rendering look good (and text rendering is hard).

More details:

The demo is using half-resolution on high-dpi displays (currently that's sokol-app's default setting, but not sure if that still makes sense in this day and age tbh), this half resolution amplifies all sorts of text rendering issues, and it gets especially bad when there's a fractional system-dpi-scale like 125% or 150%.

PS: another problem (maybe the main problem, even if everything else is correct) is that the demo's pre-baked font atlas texture isn't all that great since it has 'anti-aliasing' baked into the glyph pixels, and the font atlas texture has a very low resolution (glyph height is 10 pixels, which would be ok for a 'crisp' hand-drawn bitmap font, but not when the font atlas has been created from a regular TTF font, which this one seems to be).

Does this Dear ImGui demo look better on your setup? This is using the native display DPI and uses a TTF font instead of a bitmap font:

https://floooh.github.io/sokol-html5/imgui-highdpi-sapp.html

Post reply on HN