Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • i've been writing Haskell GUIs for a few years and mostly stick to react-banana or reflex because wiring up gtk-gi signals manually gets messy fast. The Elm architecture pattern here looks clean on paper but I'm curious how you handle async events from the widget tree without ending up in callback hell. Did you end up wrapping all GI callbacks in a channel that feeds into your update loop?
  • > import GI.Awd qualified as Adw

    please tell me that's a typo

    by pluc
  • This seems to rebuild the entire view from scratch on every model update? Or is there some diffing magic that's not shown in the article?

    This loses all non-persistent UI state such as scroll positions, half-entered text etc. etc.

    Not really a workable architecture for a real app. React was invented because of this problem (how to make functional-style view building actually work...)

    by jaen
  • Are people still using gtk?

    I started to learn it back then via ruby-gtk2. It was not the best experience but I learned several key things pertaining to widgets and the UI. Then came gtk3; it was in some ways worse than GTK2, but it also brought a few improvements such as the partial CSS support. I always miss that when I use e. g. wxwidget.

    Then came GTK4 though and things changed. Tons of old things broke or no longer worked. Simple things such as main_window_widget.move(0, 0) for top-left positioning (I added an alias to this, .top_left in ruby and that worked nicely); there are work-arounds to get the old behaviour, but this is just one example of so many more things that were eliminated. GTK4 is a GNOMEy-toolkit and GTK5 will be even worse since it will be wayland-only.

    "Interacting" with the GNOMEy-GTK devs is a total waste of time and I am hardly the only one who had that experience. For GNOMEys it may be a useful platform, but GTK no longer is a general toolkit really, despite claims by the current GTK devs otherwise. Why would we non-GNOMEys want to keep GTK on life support? There really needs to be a toolkit that can work in a much more de-centralized way. Sadly I also don't have a good idea here, since funding is an issue and GUIs seem to have taken a huge hit ever since the world wide web became dominating.

  • Is a widget a monad? Anyway, the examples in this tutorial are another proof that Haskell is the best imperative language!
  • Replace `backdrop-filter` on `.backdrop::after` with `filter` on `.backdrop picture` for a free scrolling performance boost.

Explore Birbla archives