3 ms·
Windows' file picker is actually an almost fully-featured Explorer instance, and is easily accessible from any application with a single function call. The "loo
by userbinator 6y ago
Windows' file picker is actually an almost fully-featured Explorer instance, and is easily accessible from any application with a single function call. The "loose components" model that a lot of OSS seems to follow means that things like this require more effort, despite the fact that GNOME is supposed to be an integrated environment.
What’s the point of doing a whole upgrade of the GTK toolkit while ignoring this problem?
An unfortunate consequence of the incessant trendchasing that has taken hold of the software industry, closed and open source alike. Frankly, I am as puzzled as the article author how solving existing problems is somehow shunned in favour of ignoring them and making "new things"... which usually tends to just create more new problems instead. No one seems to value stability and the strive toward perfection anymore. This phenomenon has been ascribed to "resume driven development", but I'm not sure if that is completely responsible for it.
- t0astbread 6y agoOr maybe no one who's in the position to implement a feature like that or get it integrated wants it enough to prioritize it over new features. Some aspects of perfection are subjective. Addendum: I'm not arguing icon view is not a great feature though.
- ubercow13 6y ago>The "loose components" model that a lot of OSS seems to follow means that things like this require more effort, despite the fact that GNOME is supposed to be an integrated environment. It seems like the opposite. It's the tight integration of the toolkit with applications that causes this issue. If there was loose integration between the file picker and the application and its toolkit, like with the newer xdg-deskop-portal protocol, it would be simpler for someone to create a better file picker witout risking breaking anything else, and for applications to be made to use it.