Fix some further issues with the Files pane UX
See original GitHub issueProblem Description
After testing the new changes proposed in #13179 and executed in #13209 as part of reviewing spyder-ide/spyder-docs#146 , I found a few remaining issues that should be resolved. The changes should be simple and the implementation very straightforward, closely following that already reviewed #13209 , so I can have a PR ready as soon as we agree on them, which can hopefully be discussed, reviewed and merged in short order.
They are:
-
Rename the optionSimply remove the option, have filters always on if any are present, and clear the filter list by default.Show all files
, enabled by default, to beShow only files matching patterns
, disabled by default, making it much clearer what this option does and what files wouldn’t be shown. This was very confusing to me as a user, and that was before I tested the latest changes with theShow hidden files
option, which makes whatShow all files
does even more befuddling. I would also move this option to be directly above the option to edit filename filters, so its more clearly connected with that. - Rename the option
Show filenames with these extensions...
toEdit filename filters...
to avoid misleading users that only the extensions are matched, since the patterns can match anywhere in the name, and in fact a third of the default patterns don’t involve extensions at all. It also links it more clearly with the option that enables/disables the filter. - Make the window title of the filename filter dialog match the options menu text (it currently is stuck with the old name) and add a clearer description, e.g.
Enter the glob patterns, separated by commas, at least one of which a filename must match to be shown if any have been entered.
- Modify the preferences accordingly and add a section around it
- Change
Python script
toPython file
in theNew
submenu, since the file can be either a script, a module or both.
@ccordoba12 , am I good to go ahead with a PR with these changes? Thanks!
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Treat UX Problems Like the Bugs They Are - FullStory
With a UX bug, you need to go further to classify the problem, triage the work, and discover the solution. That's where FullStory...
Read more >7 common Figma design problems (and how to fix them)
Practical ways to overcome 7 common Figma design issues, caused by auto layout, constraints, groups, frames, components, and duplicates.
Read more >Designing Better Error Messages UX - Smashing Magazine
Short answer? Start without auto-scrolling and display just an error summary with links. If it's too slow, or doesn't work as expected, consider ......
Read more >Top 10 Application-Design Mistakes - Nielsen Norman Group
Design iteratively, and test each change with a small number of users. The more iterations, the better your application will be. Despite the ......
Read more >Best 10 Examples And Guidelines For Error Messages
Even if they don't read the whole error message, they should be able to easily see which option to choose in order to...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think it would be good to add just a little more info to the Edit Filter dialog so that it’s not only the (extremely important) technical info. I’d also add a simple suggestion of filter use like “Filter files by name, extension, or more using glob patterns” before @CAM-Gerlach’s explanation of glob patterns. I think of this proposed addition as the “why” to the technical “how.”
I’d also like to make sure the dialog’s title matches the name of the hamburger menu item (Edit Filter).
Thanks @isabela-pf Definitely agreed, I’m a lot happier with that vs. the original, since it does a much better job explaining what they can be used for and many users without a *nix background may not be familiar.