diff --git a/doc/articles/uno-community-toolkit-v8.md b/doc/articles/uno-community-toolkit-v8.md index a628bba775e7..490aa255adc6 100644 --- a/doc/articles/uno-community-toolkit-v8.md +++ b/doc/articles/uno-community-toolkit-v8.md @@ -184,6 +184,100 @@ You can set the `Header`, `HeaderIcon`, `Description`, and `Content` properties A complete working sample, along with additional examples, is available on GitHub: [Uno Windows Community Toolkit SettingsCard Sample](https://github.com/unoplatform/Uno.Samples/tree/master/UI/WindowsCommunityToolkit/Version-8.x/UnoWCTSettingsCardSample) +## Using Non-UI Elements from the CommunityToolkit: Converters + +The CommunityToolkit is providing some ready-to-use Converters for e.g. x:Bind in Xaml, whithout having to write already existing basic Converters yourself. +[List of CommunityToolkit Converters | Windows Toolkit Documentation](https://learn.microsoft.com/en-us/dotnet/communitytoolkit/windows/converters/) + +The implementation of those are quite similar to the example of the SettingsControl above, but there are small adjustments to be done to use them: + +1. Import of the Package + + Change this: + + ```CommunityToolkit.WinUI.Controls.SettingsControls``` + + to Converters namespace: + + ```CommunityToolkit.WinUI.Converters``` + + while the Version will stay the same as above. + +1. Add the related needed namespace(s) + + > [!NOTE] + > In WCT version 8.x, the namespaces between UWP and WinAppSDK were merged. + + ### WinUI / WinAppSDK / UWP + + In XAML: + ```xmlns:converters="using:CommunityToolkit.WinUI.Converters"``` + + In C#: + ```using CommunityToolkit.WinUI.Converters;``` + + In case you are developing a App that's using C# Markup and you want to use the Converters, you can now switch to [C#-Markup Converters](https://platform.uno/docs/articles/external/uno.extensions/doc/Learn/Markup/Converters.html) Documentation for future Usage Guide, the general Import is done from here on. + + 1. Xaml Definition + +Important Difference to the previous seen SettingsCard Control Example, a Non-UI Converter has to be imported to the Page.Ressources Section to StaticRessources like this for using it, since there is no single Namespace per Converter like on the Controls: + +### [Example StringToVisibilityConverter](#tab/string-visible-conv) + +StringToVisibilityConverter is a Converter that has to be bound to a String typed Property and will return a Visibility State. + + ``` + + + + ``` + +Somewhere in your Page Content: + + ```xml + +