FyneDesk, a fresh look at what it means to be a desktop environment

Re:FyneDesk, a fresh look at what it means to be a desktop e... by Taniwha on Thursday September 30, 2021 @02:40PM (#28709603)

I think that requiring all your desktop apps to be rewritten is go is going to be a big ask - equivalent toolkits like KDE/QT have gone out of their way to provide multiple language bindings, or to just support X-apps natively

[ Parent | on HN ]

Re:FyneDesk, a fresh look at what it means to be a desktop e... by chmsky00 on Thursday September 30, 2021 @03:03PM (#28709955)

Like all frameworks, which are barebones libraries wrapped in opinionated organization, KDE/QT can be a lot when you need a simple UI.

I’ve used Nuklear to make simple, portable, UIs: https://github.com/Immediate-Mode-UI/Nuklear

Everything has trade offs; I might need to come up with my own way of handling some bit of state, but my projects aren’t big enough to need the software equivalent of a Costco.

[ Parent | on HN ]

Re:FyneDesk, a fresh look at what it means to be a desktop e... by kevingadd on Thursday September 30, 2021 @03:23PM (#28710232)

Nuklear's lack of accessibility support and poor internationalization support are a real bummer, I ended up transitioning away from it :/

[ Parent | on HN ]

Re:FyneDesk, a fresh look at what it means to be a desktop e... by andydotxyz on Thursday September 30, 2021 @05:34PM (#28711593)

At Fyne we believe that the Go language is just so much easier to build with that following its idioms is a really positive thing. Language bridges and library ports can make it harder to develop. Of course you don't have to rebuild your apps, Qt and KDE and EFL apps will all work just fine inside a FyneDesk setup as we follow FDO specs etc.

[ Parent | on HN ]