gotk3 VS sciter

Gotk3 1.3k

gotk3 does the job, and is well documented.

Go gtk3 bindings are very nice https://github.com/gotk3/gotk3

I wanted to try the GTK bindings for Go, so I did all the steps for importing an external module: go mod init "test/gtk" go mod tidy go get "https://github.com/gotk3/gotk3"

So it should be simple as buttons+images+some sounds. The purpose to create this game is fun, but mostly to learn golang better. There are a lot of options now. I suppose it should be https://github.com/gotk3/gotk3 But, well, maybe you know better framework to use?

gotk3 is a good one

gotk3 https://github.com/gotk3/gotk3

There are definitely libraries, such as bindings to GTK: https://github.com/gotk3/gotk3 or Win32: https://github.com/rodrigocfd/windigo

The point remains that it is possible to do these things without async/await, but Go isn’t frequently used to develop native UIs, most likely because the kind of visual UI builder tools used in Visual Studio or Android Studio have never had an equivalent funded for use with Go, due to lack of commercial support for that use case. Beyond that, web gui frameworks are immensely popular these days, further removing motivation to really “make gui happen” in Go, but there are niche use cases out there, as evidenced by the existence of libraries.

I'm trying to use gotk3 (https://github.com/gotk3/gotk3). The first issue I got was with pkg-config not being in the PATH environment variable. Cool, I fixed that. Now, I get errors about gio, glib, and gobject not being found in the pkg-config search path.

I'm trying to build an app using gotk (cgo bindings for GTK), but I'm having trouble compiling it for Windows (I'm on Linux)

> wondering if css and svg could be used as abstraction over graphics and UI libraries

There's another project called Sciter that uses CSS to target native graphics libraries: https://sciter.com

> I wonder how hard it was to implement css. I've heard it can be pretty complex.

It was hard, but the biggest barrier is the obscurity of the knowledge.

Text layout is the hardest, because working with glyphs and iterating them in reverse for RTL is brain-breaking. And line wrapping gets really complicated. It's also the most obscure because nobody has written down everything you need to know in one place. After I finished block layout early on, I had to stop for a couple of years (only working a few hours a week though) and learn all of the ins, outs, dos, and don'ts around shaping and itemizing text. A lot of that I learned by reading Pango's [1] source code, and a lot I pieced together from Google searches.

But other than that, the W3C specifications cover almost everything. The CSS2 standard [2] is one of the most beautiful things I've ever read. It's internally consistent, concise, and obviously the result of years of deliberation, trial and error. (CSS3 is great, but CSS2 is the bedrock for everything).

[1] https://gitlab.gnome.org/GNOME/pango/

otherwise, if we have only retained mode as in browsers, we will need to modify the DOM heavily and create temporary elements for handles.

[1] https://sciter.com

I've still never used it but I've long been curious about Sciter:

https://sciter.com

These bullet points are exactly what I did in Sciter (https://sciter.com)

- Windowing

-- Tabs

-- Menus

-- Painting

-- Animation

-- Text

-The compositor

-Handling input

-- Pointer input

-- Keyboard input

- Accessibility

- Internationalization and localization

- Cross-platform APIs

- The web view

- Native look and feel

On top of that DOM and CSS implementations to achieve declarative UI. And JS as a languuage behind UI - declarative in some sense way of defining UI behavior.

I'm not sure if it can support all the libraries but yes it can be used to make desktop apps. Theres also Sciter.

https://sciter.com/