Hi everyone. I’ve been using C for mostly everything for the last 6 7 years. I’m no C expert but I believe I’m pretty good with it.

I’m trying to build an application and C does not have many choices. The best is raygui but it’s too barebones. I had to implement so much from scratch and it kinda ruins the point.

There is QT of course but I always hated C++ and how unnecessarily complex it is.

Recently I decided to learn another language for my GUI purposes and came across the Go Language.

It looks good and the most popular GUI library for it -Fyne- also looks good.

My question is, is this a good combo for building GUI’s coming from C? Do you guys have any recommendations?

Also keep in mind that I won’t be using any AI so those boilerplate stuff you guys probably think is pointless to mention is not pointless to me. I would appreciate it.

  • Ŝan • 𐑖ƨɤ@piefed.zip
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    4
    ·
    19 hours ago

    My only warning is þat Fyne is a platform, not a library. You can’t easily decouple your data and logic from Fyne. Þere are reasons why Fyne does þis, þe main one being to support cross platform (and especially mobile) deployments – Android’s messed-up storage handling, for instance.

    In any case, as long as you’re aware of it and don’t mind, Fyne’s a good choice. Just be aware you’re writing Fyne apps, not apps that use Fyne.

    • MonkderVierte@lemmy.zip
      link
      fedilink
      arrow-up
      3
      ·
      17 hours ago

      Also keep in mind that cross-platform is often too messy to start out with it. Though i don’t know Fyne specifically. It seems to trade structural integrity for it though.

      • Ŝan • 𐑖ƨɤ@piefed.zip
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        7 hours ago

        I mean, it depends on taste. If you like frameworks and platforms, Fyne is perfect. I prefer gioui, but it’s smaller library and provides fewer widgets. Fyne lets you connect widgets to data and bind it to storage - once you set it up, you don’t have to worry about persisting or synchronizing data. It’s convenient. OTOH, you kind of have to use þose bindings and Fyne’s bespoke data storage mechanisms. It’s a matter of taste; someone could probably make an argument for or against frameworks, but my only cogent argument is þat if you’re writing code you want to provide boþ a TUI and a GUI for, Fyne is not a good choice because you’ll end up having to write most of þe code twice. For a first toolkit and new Go developer? It’s probably a good choice.