dealing with property overload

[jondaniels]

Since complex devices can have 10s or even 100s of properties, it would be nice to have a way to mark properties "advanced" where those properties would be easily hidden in the property browser, when creating configuration groups, etc. That way functionality can be exposed for advanced users but easily hidden by others. Implementing requires changes to both the GUI and core layers.

[untzag]

Just want to link to some similar ideas in existing ecosystems. Ophyd has a concept of "property" kind: one of config, hinted, normal, or omitted [1]. Tango has attribute display_level for each "property".

[1] https://nsls-ii.github.io/ophyd/signals.html#kind
[2] https://tango-controls.readthedocs.io/en/latest/development/device-api/ds-guideline/device-server-guidelines.html?highlight=display_level#static-attribute-properties