Bug 245712

Summary: provide list or table view for all configuration data about:config
Product: [Applications] systemsettings Reporter: Aaron Peterson <alpeterson>
Component: generalAssignee: System Settings Bugs <sourtooth+ssbugs>
Status: RESOLVED INTENTIONAL    
Severity: wishlist CC: nate
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:

Description Aaron Peterson 2010-07-25 08:58:56 UTC
Version:           unspecified (using KDE 4.4.92) 
OS:                Linux

Lots of people have put effort into creating logically grouped configuration options, however, there are stragglers, and extra features that we can edit in the configuration file.

These are often items of large scale internet-search-quests that result in some pour sap editing a configuration file by hand, with no revision control, or other safety net.

Just as most database programs allow for form view, and table view, We should be able to provide a rich table interface, such as in Firefox that lets users query, and explore options.

I suggest that this be added as a 3rd view, as we have tree-view, category view?, and then we could have table view.



Reproducible: Didn't try




Some criticism that I have already heard, is that this would let users muck with undocumented and experimental settings...   

if that is really a problem, if we really have a configuration setting that is "should I delete all files on start up?", we could have an initial query that hides improperly supported options,

And this would increase the amount of testing and feedback we get on those tough-to configure settings,  and would eliminate some bug feature requests where we ask for things that the developer can't figure out where should go.


Styled after mozilla firefox's about:config, (but not hidden and not in a "danger content area")
Comment 1 Nate Graham 2020-10-12 21:53:24 UTC
Not sure there's a way for us to aggregate all settings like that. Applications don't really make them available in a parseable way. Sorry. :)