I had some free time during the weekend to make progress on the desktop version of flowvi.be :catjam:
I'm starting to get into the GTK/libadwaita mindset of things. Also realized if I keep a tidy project structure I can easily switch to Qt or something else later on so that's nice.
Big things have small beginnings ;)
#IndieDev #GTK #Qt #KDE #Gnome #Flowvibe #Music #PlaylistMaker
@iamkonstantin I noticed that many of the apps I prefer are actually GTK apps while I do enjoy KDE as a desktop environment more. It's weird. Good thing we can mix and match.
@renef They both have their own design system, but I think a lot of work has gone into making it so they feel okay regardless of which desktop you use. I really love that aspect of “digital cooperation” between gnome and KDE. Same for when you’re actually coding an app, I find myself pleasantly surprised when I can just do things, the UI framework doesn’t impose rules outside UI stuff etc. Some things are harder but others are “clearly many uses have contributed to make this better”
@iamkonstantin What did you write that in? I'm a little intimidated by QT, it has been at least 20 years since I've last written something in C++.
@renef Currently, I'm exporting Rust + GTK. Rust + Qt (with QML e.g. Qt Quick) would be the alternative.
@iamkonstantin I should look into that, Rust would be doable.
@renef I followed https://gtk-rs.org/gtk4-rs/stable/latest/book/introduction.html to get started. To use the GNOME design system, you can check https://world.pages.gitlab.gnome.org/Health/libadwaita/index.html
Same for Qt stuff, the KDE developer portal has excellent resources to get you started with Kirigami https://develop.kde.org/docs/getting-started/rust/
Whichever you choose, you can look at the source of all system apps to see how they work. Gnome Builder will even let you clone and run the Gnome ones right from the start screen. Same for the kde-builder CLI tool.
