I agree with this.
At least having some option to display files and directories in a classic tree view would be great
I am not entirely sure what this should be good for.
There is no file hierarchy in the media uploader.
It is not a PHP Directory Manager, it is a Media Manager, and thus there is just files, without “parent” folders.
If this refers to the “date” folders, I rather suggest to make the decision in the begin to not use date folders and even make this not the default (thus: not use date folders as default)
This because it is rather annoying and useless, even disturbing when programming with dynamically generated file urls, for example, when having media in date folders.
It is not developer friendly, it is “manager” friendly, and I am not sure this should be the default.
For me that could be step one of the betterment: make the non-date organised upload directory the default.
Step two could be to check each, and fixe where needed, API for the media management.
Then there are things like medium_size, which should be looked at (and probably removed).
Then there is a lot of (IMO) messy stuff going on in the editor of media in terms of UI.
Just as example, to crop an image, you have to know that first you got to move the mouse on the image to designate a crop area and only then the crop tool will become active and useable. That is horrible UI. After almost 10 years using WP I still every time I crop an image in there kind of get lost.
To save a alt tag, you have to know that it will save when clicking outside the text area. Etc.
I agree with almost all points made here as well Petititon: Improved Media Library but again, those are different things, they likely shouldn’t be part of one big project, rather a step by step thingy (just to make sure we do not force unwanted feature while pushing wanted feature)
So I would personally suggest to proceed with chunked requests, if we need, because this here is seems a “please fix all issues but there are too many issues to list them all” kind of task. That means it will never lead to a result. Developers need “micro” tasks to successfully and quickly make things happen (at least, that is how I see it)
So let’s make microvotes
Then each can be implemented, even by different contributors.
On the other hand there is https://github.com/ClassicPress-research/improved-media-library, maybe we can just open that to let users add “Feature Requests” there?
So we do not have to open (probably hundreds) of Votes?