Page MenuHomePhabricator

Use icons with Config Options page
ClosedPublic

Authored by chad on Feb 2 2015, 5:38 PM.
Tags
None
Referenced Files
F14058960: D11619.diff
Sun, Nov 17, 4:13 PM
F14046132: D11619.diff
Wed, Nov 13, 6:27 PM
F14035115: D11619.diff
Sun, Nov 10, 4:16 AM
F14022113: D11619.diff
Wed, Nov 6, 3:18 PM
F14003022: D11619.diff
Sat, Oct 26, 1:14 AM
F13999466: D11619.id27955.diff
Thu, Oct 24, 2:58 PM
F13970218: D11619.id27959.diff
Oct 17 2024, 6:24 AM
F13968038: D11619.id.diff
Oct 16 2024, 6:08 PM
Subscribers

Details

Reviewers
epriestley
btrahan
Commits
Restricted Diffusion Commit
rP99292c5c6a67: Use icons with Config Options page
Summary

This sets an icon for each config, makes it easier to scan.

Test Plan

Reload Config page, see all new icons

pasted_file (975×525 px, 158 KB)

Diff Detail

Repository
rP Phabricator
Branch
config-icons
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 4240
Build 4253: [Placeholder Plan] Wait for 30 Seconds

Event Timeline

chad retitled this revision from to Use icons with Config Options page.
chad updated this object.
chad edited the test plan for this revision. (Show Details)
chad added reviewers: epriestley, btrahan.
epriestley edited edge metadata.

I'm a little hesitant about the potential for overloading here, but it looks like the application icons pretty much are all associated with application settings.

This revision is now accepted and ready to land.Feb 2 2015, 5:57 PM

Is there a simple way to group them (app config, phab config, mail config?). Breaking it into 2-3 boxes would help alleviate clutter.

On the technical side, we've sort of been trying to remove as much of the config as we can and move what we can't remove (but is application settings) into Applications > Options (e.g., all of @btrahan's recent work with email turns a bunch of email Config into application settings). I think we can maybe get through ~100 of the ~200 settings like this, maybe.

That would remove a bunch of these groups, and then maybe we could reorganize what's left a little better. This is probably a ways out, though. There's some config I think we can delete outright (e.g., we have 7 gcdaemon.ttl settings which I believe are never useful and likely never adjusted). I want to at least shop this around a little bit with users first, though (maybe I'll pose a question in the change log, which I guess I'm due to write).

Upshot: maybe not worth reorganizing yet, since we'll hopefully have a different/easier problem in like 3-6 months, depending on how things go?

This revision was automatically updated to reflect the committed changes.