Explore additional layout control surfaces for discoverability

[sbatten]

The goal of this issue is to experiment with new layout control surfaces to help users understand/discover the different layout customization options.

The initial version of this is available in insiders and disable-able via workbench.experimental.layoutControl.enabled

[sbatten]

The latest here is

[heartacker]

hei, how can we exit the view without keyboard?

I think we should add a close button to the left-top

[bpasero]

From testing: Some entries toggle on click, other entries are more like radio boxes, I think this picker needs a UX revisit.

[miguelsolorio]

My comments from Slack:

While I do like that I can customize the layout, the quick pick feels like an odd choice because:

• the options by themselves don’t make a ton of sense without the title, which is on the right, so your eyes are bouncing left/right which make it not easy to scan and takes a bit longer to read
• it’s not clear if hitting enter or clicking an item will toggle it or if it’s the eye
• the sections titles should be more user friendly, instead of “move side bar” maybe “side bar placement” etc.
• after playing with this, the ux feels very strange as there is a mixture of checks and toggles. there’s also no way to dismiss with the mouse (you have to use “esc”)

While I can see the need to make layout customization more discoverable, the overall ux of the quick pick in this context suffers from usability as there’s so many patterns being used. I personally prefer the menu version, better but keeping the menu open, since it’s simpler & a known pattern.

[Tyriar]

My thoughts:

• I like the theme picker-like quick pick approach
• Can we get radio buttons supported?
• Can we use checkboxes? Instead of the eye?
• Highlighting sections based on the hovered/focused item is a great idea

[TylerLeonhardt]

• Can we get radio buttons supported?
• Can we use checkboxes? Instead of the eye?

Right now the quickpick is all or nothing with checkboxes so that would need to change but is a pretty large item. #141500
Only after that would it be worth implementing radio button support for a group for this feature. #141503

Also I might also say that having #120866 would be a dependency as I think a bunch of checkboxes (6 in this case) is kinda jarring over the approach @sbatten already took.