I worked as a document scanner, and we had to have our files match some really stupid formats. With microsoft explorer, I was able get the dev environment up, find examples, and create a column that I could sort by that was a regular expression search on the name. I could create a column from the filename where I reordered the date format to YYYYMMDD and then was able to sort nicely, and it happened within an evening. It would also be nice to be able to refer to a search index, or actually read the file and grep each file searching the contents and counting the occurrences of words. Basically, there could be a plugin system, or this feature could be a custom column with meta data taken from a meta data library (to read resolution of the image, compression type, number of pages in a pdf or tiff image) and using a regex on the filename or filename contents. This would appear as add custom tab, and there should be no limit to the number of them. When a custom tab is added to the list of tabs, it can be edited, a selection of metadata library, regex, or file search, or shell command. the metadata library could populate a submenu with all the types of data. bitrate,x pixels, y pixels ,inches,word count, signed date, there are so many things this could be. there may be more than one metadata scraper. We wouldn't even need to compile anything. KDE has had cool regex searches in a few applications before, so that may already have components ready. Basically, this is an advanced col *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
>Basically, this is an advanced col Your comment is cut off there. Maybe you would have put a nice summary there. As it stands it is really difficult to follow what exactly you want to see changed. It reads more like a huge list of features and behaviour changes that would be necessary to fulfill a very specific workflow. Please also be aware that Dolphin does explicitly not have the design goal to have features for niche and advanced use cases. One thing you mention is regex filtering. That is indeed a feature that has been requested in the past and is supposed to be added to Dolphin's "Filter" feature as soon as any contributor shows up to implement it. There is also some work underway that would allow end users to use command line tools for the search. I am not sure how exactly that feature will materialise (it is quite complicated and currently in review) but there is a chance that it might allow you to create a command that serves your use case.