Building a GTK Todo App in Haskell with the Elm Architecture

Making a GTK application in Haskell, part 1

Building a GTK Todo App in Haskell with the Elm Architecture

This tutorial walks intermediate Haskellers through creating a todo-list application using Haskell, GTK 4, and the Adwaita library via haskell-gi. It covers setting up an Adwaita application window, modeling state with the Elm Architecture (Model-View-Update), and implementing domain logic for adding and completing tasks. The full project is available on GitHub, and the series continues with more features in part 2.

This approach was broadly popularised by Elm, and lends itself quite well to taming the imperative nature of the GTK toolkit.
  1. Koshkin

    Is a widget a monad? Anyway, the examples in this tutorial are another proof that Haskell is the best imperative language!

  2. seba_dos1

    Replace `backdrop-filter` on `.backdrop::after` with `filter` on `.backdrop picture` for a free scrolling performance boost.

  3. shevy-java

    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.

  4. pluc

    > import GI.Awd qualified as Adw

    please tell me that's a typo

  5. birchcove

    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?

More from this day

2026-10-05