Rendered at 20:21:59 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
ecshafer 3 minutes ago [-]
This looks good. But the thing that always lets me down on UI frameworks is how much freaking work it is to get something on the screen. My first language was Borland Turbo C++. It was so comparatively simple to do stuff. If I want to write a circle on the screen its just this:
Making some shapes and forms wasn't that much work either.
If I think back to VB and Windows (whatever it was then) making a basic window, form and some buttons was so simple and easy, they even made GUI builders because they were so good.
Somewhere along the lines GUIs became overly complex to implement.
noelwelsh 2 hours ago [-]
Interesting project, but needs documentation. In particular, what's the model it uses? I.e. how are events, state, etc. handled? Normally I'd just work it out from the code examples, but the example in the README is over 200 lines which is too long for me.
(Don't tell me here. Make your docs better, so everyone benefits!)
kristoff_it 30 seconds ago [-]
[delayed]
WD-42 1 hours ago [-]
This is great, we need more of this. It's high time we began to escape the dark ages of rule-by-Electron. See Bitwarden's recent fumble of a redesign.
vova_hn2 2 hours ago [-]
> Inspiration
> GPUI - Zed's GPU UI framework
Cool, but a comparison would also be very helpful.
If I decide to make a GUI app with Zig, how do I choose between Gooey and GPUI?
So far, all I know that GPUI is more mature and has at least one successful project built with it, so...
Also:
> Gooey: Turn (almost) any Python 3 Console Program into a GUI application with one line
GPUI is written in Rust, so in this specific case the decision is already somewhat made for you.
torginus 54 minutes ago [-]
If I remember correctly, Zed's framework didn't set the goal of being able to draw arbitrary graphics/UI and by constraining that, it basically managed to represent everything with quads and distance fields in shaders, which reduced draw calls and GPU state management to a minimum.
ssernikk 1 hours ago [-]
> how do I choose between Gooey and GPUI?
GPUI is for rust, not zig
mgrandl 1 hours ago [-]
I mean GPUI is rust and Gooey is Zig so if you wanna do a project in Zig you probably wouldn’t choose GPUI.
LouisvilleGeek 1 hours ago [-]
Call it Ziggy
amelius 13 minutes ago [-]
Nice work but honestly I haven't seen convincing arguments for writing medium to large GUI applications in a language that has no automatic GC.
cookiengineer 23 minutes ago [-]
Sadface :-(
(Author of Gooey [1], a GUI framework for WebASM in Go)
#include <graphics.h> #include <conio.h>
int main() { int gd = DETECT, gm;
}Making some shapes and forms wasn't that much work either.
If I think back to VB and Windows (whatever it was then) making a basic window, form and some buttons was so simple and easy, they even made GUI builders because they were so good.
Somewhere along the lines GUIs became overly complex to implement.
(Don't tell me here. Make your docs better, so everyone benefits!)
> GPUI - Zed's GPU UI framework
Cool, but a comparison would also be very helpful.
If I decide to make a GUI app with Zig, how do I choose between Gooey and GPUI?
So far, all I know that GPUI is more mature and has at least one successful project built with it, so...
Also:
> Gooey: Turn (almost) any Python 3 Console Program into a GUI application with one line
> https://github.com/chriskiehl/Gooey
GPUI is for rust, not zig
(Author of Gooey [1], a GUI framework for WebASM in Go)
[1] https://github.com/cookiengineer/gooey