CommunityToolkit / CommunityToolkit/Labs-Windows

No samples are using a custom options pane

Open
#447 0 comments 0 reactions 1 assignee Claimed by @Arlodotexe View on GitHub
documentation :page_with_curl: sample app 🖼 ux :paintbrush:
Dominant language
C#
Stars
482
Forks
89
PR merge metrics
No merged PRs in 30d

Description

## Background
Sample Options are the pane next to sample controls that allow users to manipulate the sample. This separate pane is either generated using attributes, or manually assigned with a UserControl of your choice, and an instance of the sample is provided for manipulation. This approach keeps the sample XAML and C# source code presented to the user clean and succinct.

## Problems

In order to create sample options, samples in CommunityToolkit vNext and CommunityToolkit Labs currently use either:
- Generated option attributes, or
- Directly insert the UI for manipulating the sample into the sample itself.

The second method is problematic, as it makes the source code for the sample hard to read and can lead to an inconsistent user experience. This issue arises due to a lack of documentation and samples for using a fully custom options pane.

## Solution
For components with option-related UI inside their samples, migrate to using a custom options pane instead. This will improve the readability of the source code and provide a more consistent user experience.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.