Bug 476904

Summary: File Associations list should be a table.
Product: [Applications] systemsettings Reporter: Roke Julian Lockhart Beedell <4wy78uwh>
Component: kcm_filetypesAssignee: Plasma Bugs List <plasma-bugs-null>
Status: REPORTED ---    
Severity: wishlist CC: faure, nate
Priority: NOR    
Version First Reported In: 5.27.9   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
URL: https://discuss.kde.org/t/file-associations-list-should-be-a-table/7123/1?u=rokejulianlockhart
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Current appearance.
Depiction of a table with a multitude of object-specific attributes visible.

Description Roke Julian Lockhart Beedell 2023-11-12 23:10:19 UTC
SUMMARY
I'd like to be able to see the current association at a glance so that I can look down the list and only change what matters.

STEPS TO REPRODUCE
1. Invoke `kcmshell5 kcm_filetypes`.

OBSERVED RESULT
I'm forced to see the attributes of each individually.

EXPECTED RESULT
For instance, if most file types are set to one application, but a few exceptions exist, I would like to be able to change those without introspecting all of them indivudally.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20231108
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11
Kernel Version: 6.5.9-1-default (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor
Memory: 30.5 GiB of RAM
Graphics Processor: AMD Radeon RX 5700
Manufacturer: ASRock
Product Name: X670E Taichi

ADDITIONAL INFORMATION
https://discuss.kde.org/t/file-associations-list-should-be-a-table/7123/1?u=rokejulianlockhart
Comment 1 Roke Julian Lockhart Beedell 2023-11-12 23:17:18 UTC
Created attachment 163094 [details]
Current appearance.
Comment 2 Nate Graham 2023-11-15 20:24:43 UTC
What do you mean by "should be a table?" How would that help you? Can you maybe provide a mockup of what you think it should look like, and how specifically it would help resolve the issue you're facing?
Comment 3 Roke Julian Lockhart Beedell 2023-11-15 21:00:35 UTC
Created attachment 163196 [details]
Depiction of a table with a multitude of object-specific attributes visible.

(In reply to Nate Graham from comment #2)
> What do you mean by "should be a table?" How would that help you? Can you
> maybe provide a mockup of what you think it should look like, and how
> specifically it would help resolve the issue you're facing?

It would allow me to see which MIME-types are assigned to which applications, if such a column were added, as aforestated.
Comment 4 Roke Julian Lockhart Beedell 2023-11-15 21:03:26 UTC
(In reply to `{third: "Beedell", first: "Roke"}`{.JSON5} from comment #3)
> Created attachment 163196 [details]
> Depiction of a table with a multitude of object-specific attributes visible.
> 
> (In reply to Nate Graham from comment #2)
> > What do you mean by "should be a table?" How would that help you? Can you
> > maybe provide a mockup of what you think it should look like, and how
> > specifically it would help resolve the issue you're facing?
> 
> It would allow me to see which MIME-types are assigned to which
> applications, if such a column were added, as aforestated.

I forgot to reiterate how this would assist me — as aforestated, it would “[Allow me] to change those without introspecting all of them individually” in which I referred to how I wanted to change all items assigned to a specific application to another.