5 ms·
Almost all my Linux work has been via command line for quite a while, so maybe this has changed, but my recollection was the GUI inconsistency had little to do
by tzs 7y ago
Almost all my Linux work has been via command line for quite a while, so maybe this has changed, but my recollection was the GUI inconsistency had little to do with the window manager. It had much more to do with the X libraries that the developer of each app decided to use.
I used to have a screen shot showing me running something like 5 different GUI apps on a Linux system, all of them trying to open a file, each with a completely different file chooser dialog. That's because one app used Motif, one use GTK, one used Qt, and I have no idea what the others used.
- grawprog 7y ago>I used to have a screen shot showing me running something like 5 different GUI apps on a Linux system, all of them trying to open a file, each with a completely different file chooser dialog. That's because one app used Motif, one use GTK, one used Qt, and I have no idea what the others used. But they all perform the same function of choosing a file right? What does it matter if they all look the same? I don't understand why anyone would care so much whether the file choosing windows match eachother visually between different apps. As long as I can pick a file effectively, I wouldn't really care if the app had pink sparkles or something. As long as it does what it's supposed to.
- xboxnolifes 7y agoApparently a lot of people care, but programs not having the same style across a system always seems to be a top 3 issue with electron apps.
- tzs 7y agoIt's not that there are aesthetic difference like pink sparkles on some. It's that some have a file type filter and some don't. Some show all files while others hide dotfiles and provide a checkbox to show them. Some show files and directories in the same pane while others show directories in one pane and files in another. Some show ".." in their directory list and you go up by opening that, others do not show ".." and provide a button for going up.
- grawprog 7y agoI understand this, but modularity is one of the philosophies and benefits behind linux, with modularity unfortunately comes inconsistency. As many of the apps available on linux are open source and open source developers are mostly free to use whatever toolkits they want or are comfortable with, you're not likely to get the consistency you want with linux. With windows you have an API provided by windows for ui programs, there will be more consistency between apps because of this. Linux providing a standardized ui API would go against the core philosophy of it and you're not likely going to be able to convince every developer making gui apps for linux to agree on and use only one graphical toolkit. Like with anything, every os has tradeoffs and downsides, personally I prefer modularity and control over my system to ui consistency.
- michaelmrose 7y agoActual modularity would imply a common way to plug in different file choosers so you could use file mangager A with desktop b with application from desktop c. Inconsistency comes not from modularity but rather from incompetence.
- tzs 7y agoA standard API can provide more modularity and control than the current approach. You do this by having several available implementations of the API as dynamic libraries--one using Motif, one using GTK, one using Qt, and so on. There would be a per user config setting specifying which implementation the user prefers. If a program wants to put up a file chooser, it can read that, then load the right library and use the API. A program might also have per program settings to override that, to handle the case where a user really does prefer, say, GTK file choosers for most programs but Qt file choosers for some specific programs. This gives you more UI consistency, makes things more modular than having every program include file chooser dialog code, and gives more control to the user, and doesn't interfere with the developer choosing whatever toolkit they prefer for things other than standard dialogs.
- grawprog 7y ago
- akiselev 7y agoThe devil is in the implementation details. Are favorites/shortcuts in the same part of the screen? Are they in the same order? Does the dialog remember sort and view configuration between folders? Does the dialog differentiate between mounts, symlinks, and tangible files? Does it display networked machines properly? Are file icons consistent in design if not color scheme? The problem most people have (in my experience) is behavioral. The mismatching visuals is just the most jarring aspect that's easiest to point to.
- michaelmrose 7y agoThe aesthetics are not a completely invalid consideration. People recognize patterns and find choosing behaviors/reactions easier when recognizing a common pattern. It takes more effort to respond to unfamiliar stimulus. Aesthetics aren't the only consideration though. File choosers typically allow one to bookmark commonly used directories unfortunately this is per chooser purely for reasons of lack of coordination. Further despite people asking for it for the last 15 years the gtk version doesn't have a very good way to visually pick out an image in their picker. To date the only good way to pick out an image in a gtk app even GIMP is to open a file manager alongside the application and drag the file into the application or file chooser. I find it unlikely that most people figure this out.
- neycoda 7y agoWindows has this same problem, with 3rd party and its own apps. I don't know why it needs 3 different file open dialogs, and it confuses the crap out of normies. Don't even ask me about people getting upset about not knowing when to click or double-click.
- brokenmachine 7y agoI tell people that if the cursor changes to a hand, then it's a single-click. Everyone doubleclicks anyway though.
- ubercow13 7y agoThis comment reminds me of this meme image that I saved a few years ago: https://i.imgur.com/JG7I2hu.png https://i.imgur.com/JG7I2hu.png Odds that it's even worse since this was created?
- tzs 7y agoI found my screen shot: https://i.imgur.com/Wcwaiwu.jpg https://i.imgur.com/Wcwaiwu.jpg
- ubercow13 7y agoNice. Actually some of these remind me of Windows, too. It's less common on Windows but plenty of applications seem to link against antiquated libraries which provide really unusable and nonstandard file selection dialogs. One thing I remember being annoyed with is old-style ones that are very small and you can't resize. Here are some, but I've seen weirder ones: https://i.imgur.com/jYa3qX8.png https://i.imgur.com/jYa3qX8.png
- nneonneo 7y agoWith sandboxing, macOS is now forcing devs to use their file selection dialog because it will grant access to the selected files - a custom dialog box has no such blessing. It's nice, actually; it's finally making the file selection process feel uniform. Too many Java apps are still using random Swing dialogs though...
- brokenmachine 7y agoHow do the java apps use their own file selection dialogs if they're sandboxed?
- nneonneo 7y agoSandboxed Java apps don’t. Here I’m talking about apps that you can’t get on the App Store, many of which are older Java programs which haven’t been updated to use the newer APIs. The push to force sandboxed apps to use the system dialog had the nice side effect of forcing many GUI APIs to actually use the native file pickers, which meant that a lot of non-app-store apps started to use the native file picker. But Java apps don’t automatically get that upgrade.