docs: refactor upgrade doc mentions
This commit is contained in:
Родитель
8db9974cd5
Коммит
c4b8178ed9
|
@ -2,21 +2,20 @@
|
||||||
uid: Uno.Themes.Material.Migration
|
uid: Uno.Themes.Material.Migration
|
||||||
---
|
---
|
||||||
|
|
||||||
# Upgrading Uno.Material
|
# Upgrading Uno Material
|
||||||
|
|
||||||
## Upgrading to Uno Themes v5.0
|
## Upgrading to Uno Themes v5
|
||||||
|
|
||||||
Version 5.0.0 of Uno Themes introduces breaking changes to the library. Below are the changes that have been made:
|
The Uno Material v5 packages introduce a new dependency on the [Uno Themes](https://www.nuget.org/packages/Uno.Themes.WinUI) package. Uno Themes is the base library for all design system implementations going forward. As a result, the following change have been made:
|
||||||
|
|
||||||
### Converters
|
### Converters
|
||||||
|
|
||||||
All Converters were moved to the `Uno.Themes` library, and the new `namespace` is `Uno.Themes`.
|
All Converters were moved to the base `Uno.Themes` library, and the new `namespace` is `Uno.Themes`.
|
||||||
|
|
||||||
Before:
|
Before:
|
||||||
|
|
||||||
```xml
|
```xml
|
||||||
<Page xmlns:um="using:Uno.Material">
|
<Page xmlns:um="using:Uno.Material">
|
||||||
|
|
||||||
<Page.Resources>
|
<Page.Resources>
|
||||||
<um:FromNullToValueConverter x:Key="NotNullVisibilityConverter">
|
<um:FromNullToValueConverter x:Key="NotNullVisibilityConverter">
|
||||||
</Page.Resources>
|
</Page.Resources>
|
||||||
|
@ -27,7 +26,6 @@ After:
|
||||||
|
|
||||||
```xml
|
```xml
|
||||||
<Page xmlns:ut="using:Uno.Themes">
|
<Page xmlns:ut="using:Uno.Themes">
|
||||||
|
|
||||||
<Page.Resources>
|
<Page.Resources>
|
||||||
<ut:FromNullToValueConverter x:Key="NotNullVisibilityConverter">
|
<ut:FromNullToValueConverter x:Key="NotNullVisibilityConverter">
|
||||||
</Page.Resources>
|
</Page.Resources>
|
||||||
|
|
|
@ -4,13 +4,6 @@ uid: Uno.Themes.Control.Extensions
|
||||||
|
|
||||||
# Control Extensions
|
# Control Extensions
|
||||||
|
|
||||||
Starting on version 5.0.0 the `ControlExtensions` are available on the `Uno.Themes` namespace, so to use that in xaml you should add the following xmlns to your project:
|
|
||||||
|
|
||||||
`xmlns:ut="using:Uno.Themes"`
|
|
||||||
|
|
||||||
> [!INFO]
|
|
||||||
> For more information about see our [migration docs](material-migration.md).
|
|
||||||
|
|
||||||
## Icon
|
## Icon
|
||||||
|
|
||||||
This feature allows for the addition of icon on the supported controls. Those icons could be any of the [`IconElement`](https://learn.microsoft.com/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.iconelement)s: `<BitmapIcon />`, `<FontIcon />`, `<PathIcon />`, or `<SymbolIcon />`.
|
This feature allows for the addition of icon on the supported controls. Those icons could be any of the [`IconElement`](https://learn.microsoft.com/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.iconelement)s: `<BitmapIcon />`, `<FontIcon />`, `<PathIcon />`, or `<SymbolIcon />`.
|
||||||
|
@ -114,4 +107,3 @@ The following control styles have support for elevation:
|
||||||
| Control | Supporting Styles |
|
| Control | Supporting Styles |
|
||||||
|----------|-----------------------|
|
|----------|-----------------------|
|
||||||
| `Button` | `ElevatedButtonStyle` |
|
| `Button` | `ElevatedButtonStyle` |
|
||||||
|----------|-----------------------|
|
|
||||||
|
|
Загрузка…
Ссылка в новой задаче