3 ms·
Purely out of curiosity, what else is the Gtk team currently working on? People have been complaining about the file chooser for years. I'd be willing to donat
by nerdponx 6y ago
Purely out of curiosity, what else is the Gtk team currently working on? People have been complaining about the file chooser for years.
I'd be willing to donate a good chunk of money just to support "basic UX" improvements to FOSS software and toolkits like Gtk.
Should we start a "Fix the Gtk file chooser" Gofundme?
- ahartmetz 6y agoIt's more like decades, not years, by now. Seems worthwhile.
- turminal 6y ago> Purely out of curiosity, what else is the Gtk team currently working on? Probably redesigning the entire interface. "For your convenience".
- merb 6y agowhich they also do for years.
- TingPing 6y agoThe GTK team is like 3 people. GTK4 worked on improved cross-platform support, effecient gpu rendering, documentation, sandbox integration, etc. UI designers are probably limited and there is just a lot of drama about the filechooser so it's easy to find other things to work on.
- hda2 6y agoThe patches already exist. In fact, PopOs! already has this feature merged.
- superkuh 6y agoI searched PopOs! repos and I couldn't find where they maintained their Gtk-3.0 patches or code. It didn't look to me like they altered Gtk-3.0 itself at all and likely just altered individual applications.
- bjourne 6y agoFixing the GtkFileChooser is not the main problem, it is getting your patches merged. Someone from the Gtk team needs to review them and put their stamp of approval on them. But the Gtk team are RedHat employees and they prioritize whatever the company wants them to prioritize. And if the company doesn't want them to prioritize the GtkFileChooser, your patches will languish on their bug tracker. If you are lucky, you'll get a message two years after you uploaded them asking you to rebase them to HEAD because the code base has changed to much that your patches can't be merged without them being significantly reworked.