You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentioned here, we may want to take inspiration from the XAML Control Gallery and allow for multiple, separate samples under the same Lab/Experiment.
This would help clean up samples that already contain multiple other samples, like SwitchPresenter, OrbitView, and TextBoxMask, by physically separating them into separate samples with their own copy-able code and settings to tweak.
It would also allow us to embed each one inline with documentation, or deep-link to a very specific sample.
Current toolkit:
XAML Control Gallery (proposed approach)
The text was updated successfully, but these errors were encountered:
Yeah, this sounds exactly what I was thinking we'd end up with. Though I think we'd have two different versions.
In the single-experiment mode where a developer is developing, each sample would be its own page listed out on the navigation bar, as it'd be only displaying this experiment. (And one tab would also be the doc page.)
In the multi-experiment mode, it would use the doc page as the main page template, and then the documentation would have a tag call out like [[Sample1]] (in whatever syntax we decide) then it would insert that example in that spot. (This is kind of what we tried to do in the MVVM Samples app https://github.com/CommunityToolkit/MVVM-Samples)
Arlo suggested that we could have a button to toggle the navigation type between the basic mode we use per-experiment and the hybrid documentation mode...
We can use the right-side bar that the control gallery has to jump to the specific sections/samples in the doc as well.
Overview:
As mentioned here, we may want to take inspiration from the XAML Control Gallery and allow for multiple, separate samples under the same Lab/Experiment.
This would help clean up samples that already contain multiple other samples, like SwitchPresenter, OrbitView, and TextBoxMask, by physically separating them into separate samples with their own copy-able code and settings to tweak.
It would also allow us to embed each one inline with documentation, or deep-link to a very specific sample.
Current toolkit:
XAML Control Gallery (proposed approach)
The text was updated successfully, but these errors were encountered: