Came here to say the same. Please add a few screenshots!
giancarlostoro 7 hours ago [-]
Dear Future architect of some neat new technology to be someday posted on HN please do the following:
If you make anything with a UI, even a GUI stack, always include screenshots. If you make a programming language or programming framework / library, always include code samples!
Really show us nerds the bits we want to see right away, screenshots / code or even a video (fully optional, unless its some type of terminal shell or something where a video would illuminate things!) would sell it better. Many of us are working and don't yet have time to pull down everything to run it locally.
Honestly, even if its not open source, if you're selling a product, SHOW THE PRODUCT not just descriptions of the product.
embedding-shape 55 minutes ago [-]
So, given that this is almost brought up every single time a GUI framework/library is posted on HN, and has been for decades at this point, and given that it apparently doesn't make any difference, what's a better approach for educating the ecosystem at large about this problem? Do we need a website? Nation outreach program? Do we need a arewescreenshottingyet.com landing page with stats to keep track? How can we finally fix this constantly persisting problem of people not adding screenshots for visual things they've built?!
foresto 2 hours ago [-]
Somewhat related (but not declarative): Qt bindings for Go, MIT-licensed.
Looking forward to a Golang declarative framework.
My advice to the author: invest in rich multi-window support early on. It's easy not to, but you always need it in the end, and it's painful to retrofit.
I feel like there's a great cross-platform UI story to be told with Go, since cross compiling is so easy.
someguyornotidk 3 hours ago [-]
How reasonable is it to ask for this to support the WASM target? This would be invaluable for small go projects that can't maintain multiple UIs.
staplung 5 hours ago [-]
Intro code snippet has two buttons ("+" and "-") in an HStack. Expected them to be arranged horizontally but in the accompanying screenshot they're stacked vertically. Is that intentional?
donatj 10 hours ago [-]
This wraps Fyne? As a long time user of Fyne, what does this provide beyond Fyne itself?
red_admiral 9 hours ago [-]
A "mithril" like syntax. Like you could do (wrapped over multiple lines of course)
The repo doesn't say it, but the Author noted on the Gophers Slack #showandtell that the style was inspired by SwiftUI. That VStack example shows it quite well.
rubenvanwyk 10 hours ago [-]
I think styling and ready-made components out of the box?
4ndrewl 3 hours ago [-]
Probably nice, but only 7 commits and over 2 days? Are you in this for the long run?
rubenvanwyk 9 hours ago [-]
Very excited every time I see cross-platform GUI in go.
I think the right mental model is that Gova is to Fyne like DaisyUI is to TailwindCSS??
GuardCalf 10 hours ago [-]
I once built a small utility using the "Fyne" framework; it was reasonably functional and made it very convenient to compile cross-platform executables (including for Android).
I took a look at your recommendation, "gova"; it seems to be just getting started—keep up the good work!
vegancap 10 hours ago [-]
That's a beautifully designed library, bravo! Will have to give it a go
kitd 7 hours ago [-]
Nice work. The hot-reload dev cli looks very cool in a compiled-binary world.
vr46 10 hours ago [-]
Looks quite nice, alternatives to Tauri always welcome although that Tauri is truly fantastic, so much to emulate.
fragmede 8 hours ago [-]
Tauri is basically Electron though. This is a native toolkit, which is another thing entirely.
Apparently a major dependency is "Fyne", which does show some screenshots on their page:
https://fyne.io/
If you make anything with a UI, even a GUI stack, always include screenshots. If you make a programming language or programming framework / library, always include code samples!
Really show us nerds the bits we want to see right away, screenshots / code or even a video (fully optional, unless its some type of terminal shell or something where a video would illuminate things!) would sell it better. Many of us are working and don't yet have time to pull down everything to run it locally.
Honestly, even if its not open source, if you're selling a product, SHOW THE PRODUCT not just descriptions of the product.
https://github.com/mappu/miqt
With the compiler flags I tried, binary size was close to that of Gova:
https://github.com/mappu/miqt/issues/147#issuecomment-280033...
Qt bindings for Zig, using the same approach as MIQT:
https://github.com/rcalixte/libqt6zig
Looking forward to a Golang declarative framework.
My advice to the author: invest in rich multi-window support early on. It's easy not to, but you always need it in the end, and it's painful to retrofit.
I feel like there's a great cross-platform UI story to be told with Go, since cross compiling is so easy.
m.div([m.h1("title"), m.p(["click", m.a({href:"..."}, "me")])])
you can do (taken from the page)
g.VStack(g.Text(...), g.HStack(...).Spacing(g.SpaceMD))
some people will like this style, others not.
I think the right mental model is that Gova is to Fyne like DaisyUI is to TailwindCSS??
I took a look at your recommendation, "gova"; it seems to be just getting started—keep up the good work!