diff --git a/uwp/Docking/Auto-Hide-Window.md b/uwp/Docking/Auto-Hide-Window.md index ecd4dc5e..b88c657a 100644 --- a/uwp/Docking/Auto-Hide-Window.md +++ b/uwp/Docking/Auto-Hide-Window.md @@ -7,16 +7,16 @@ control: SfDockingManager documentation: ug --- -# Auto Hide Window in UWP SfDockingManager +# Auto Hide Window in UWP Docking Control -`AutoHide` window is one of the states in the `SfDockingManager`. To enable Auto hidden for `SfDockingManager`'s children, set the `SfDockingManager` child `DockState` value as `AutoHidden`. +`AutoHide` is one of the window states supported by the `UWP Docking Control`. To enable the `AutoHide` state for a child window, set its `DockState` property to `AutoHidden`. ![Auto-Hide-Window-img1](Auto-Hide-Window-images/Auto-Hide-Window-img1.jpeg) ## Configuring Window in Different Sides -`AutoHidden` window can be placed in four different sides such as Top, Bottom, Left and Right. To place the four auto hidden children in four different sides, set the `SideInDockedMode` property according to its corresponding values in the `SfDockingManager`. +`AutoHidden` window can be placed in four different sides such as Top, Bottom, Left and Right. To place the four auto hidden children in four different sides, set the `SideInDockedMode` property according to its corresponding values in the `UWP Docking Control`. {% tabs %} @@ -51,7 +51,7 @@ documentation: ug ## Side Panel and TabItem Customization -The side panel and side panel header can be customized through `SidePanelBackground`, `SidePanelItemsBackground` and `SidePanelItemsForeground` properties of the `SfDockingManager`. +The side panel and side panel header can be customized through `SidePanelBackground`, `SidePanelItemsBackground` and `SidePanelItemsForeground` properties of the `UWP Docking Control`. {% tabs %} @@ -99,7 +99,7 @@ The animation speed while auto hiding a window can be configured by setting the ## Applying Different Animations for AutoHide Window -`SfDockingManager` supports three different built-in animations while auto-hiding the windows such as Fade, Scale and Slide, which can be set through the `AutoHideAnimationMode` property. +`UWP Docking Control` supports three different built-in animations while auto-hiding the windows such as Fade, Scale and Slide, which can be set through the `AutoHideAnimationMode` property. `Fade` – AutoHidden window fades while auto hiding. @@ -173,7 +173,7 @@ The Pin button, which performs the Auto Hide functionality, is visible by defaul ![Auto-Hide-Window-img4](Auto-Hide-Window-images/Auto-Hide-Window-img4.jpeg) -To show or collapse the AutoHide button for a specific child in the `SfDockingManager`, the `IsPinButtonVisible` attached property can be used. By default, the `IsPinButtonVisible` value is true. This functionality can be disabled by setting its value as false. +To show or collapse the AutoHide button for a specific child in the `UWP Docking Control`, the `IsPinButtonVisible` attached property can be used. By default, the `IsPinButtonVisible` value is true. This functionality can be disabled by setting its value as false. {% tabs %} @@ -196,7 +196,7 @@ To show or collapse the AutoHide button for a specific child in the `SfDockingMa ![Auto-Hide-Window-img5](Auto-Hide-Window-images/Auto-Hide-Window-img5.jpeg) -To enable or disable the AutoHide functionality for a specific child in the `SfDockingManager`, the `CanAutoHide` attached property can be used. By default, the `CanAutoHide` value is true. This functionality can be disabled by setting its value as false. +To enable or disable the AutoHide functionality for a specific child in the `UWP Docking Control`, the `CanAutoHide` attached property can be used. By default, the `CanAutoHide` value is true. This functionality can be disabled by setting its value as false. {% tabs %} diff --git a/uwp/Docking/Dealing-with-Windows.md b/uwp/Docking/Dealing-with-Windows.md index de3206cc..257fbb19 100644 --- a/uwp/Docking/Dealing-with-Windows.md +++ b/uwp/Docking/Dealing-with-Windows.md @@ -7,11 +7,11 @@ control: SfDockingManager documentation: ug --- -# Dealing with Windows in UWP SfDockingManager +# Dealing with Windows in UWP Docking Control ## Activating a window -A particular child window can be activated in `SfDockingManager` using its name or instance reference through the property `ActiveWindow` and `ActivateWindow` method that passes the element as argument to activate. +A particular child window can be activated in `UWP Docking Control` using its name or instance reference through the property `ActiveWindow` and `ActivateWindow` method that passes the element as argument to activate. {% tabs %} @@ -72,9 +72,9 @@ docking.ActivateWindow(SolutionExplorer); ## Adding Window Programmatically -Any UI element can be added inside the `SfDockingManager` as its child windows. The windows are added as Dock windows, since the default value of the `DockState` is Dock. The UI element is added in the `SfDockingManager` using the Add method of the `DockItems` property of the `SfDockingManager`. +The `UWP Docking Control` supports hosting any UI element as a child window. By default, child windows are added as docked windows because the `DockState` property is set to Dock. UI elements can be added using the `Add` method of the `DockItems` collection. -For example, `ContentControl` is added as a window for `SfDockingManager`. +For example, `ContentControl` is added as a window for `UWP Docking Control`. {% tabs %} @@ -125,7 +125,7 @@ DockingManager1.DockItems.Add(content5); ## Hiding Window Programmatically -To hide the window, set the `DockState` attached property of the `SfDockingManager` as `Hidden`. +To hide the window, set the `DockState` attached property of the `UWP Docking Control` as `Hidden`. {% tabs %} @@ -167,7 +167,7 @@ A Docking window can be customized using the property `DockWindowCaptionBackgrou ## Customizing Active Docking Window -Active docking window can be customized using the property `DockWindowActiveForeground`, `DockWindowActiveBackground` with desired brush values. +Active Docking window can be customized using the property `DockWindowActiveForeground`, `DockWindowActiveBackground` with desired brush values. {% tabs %} @@ -217,7 +217,7 @@ ForeColor and BackColor of Inactive document window can be customized using the ## Customizing Selected Document window -Selected Document window can be customized using the property `DocumentTabItemSelectedBackground`, `DocumentTabItemSelectedForeground` with desired brush values. Font size of the selected document window can be customized through `DocumentTabItemSelectedFontSize` property of DockingManager. +Selected Document window can be customized using the property `DocumentTabItemSelectedBackground`, `DocumentTabItemSelectedForeground` with desired brush values. Font size of the selected document window can be customized through `DocumentTabItemSelectedFontSize` property of UWP Docking Control. {% tabs %} @@ -266,7 +266,7 @@ The float window can be customized by setting `FloatWindowBackground`, `FloatWin ![Customized float window in Docking Manager](Dealing-with-Windows-images/Dealing-with-Windows-img6.jpeg) -## Handling state change of DockingManager child element +## Handling state change of UWP Docking Control child element The `DockStateChanging` event will be raised whenever the child element is changing its State. The state change of a child element can now be restricted by setting `args.Cancel` to true. "args" represents the event argument of `DockStateChangingEventArgs` for the `DockStateChanging` event. The default value of `args.Cancel` is false. @@ -310,7 +310,7 @@ args.Cancel = true; {% endtabs %} -## Restricting DockingManager child element from being closed +## Restricting UWP Docking Control child element from being closed The state of the child element will change to `Hidden` while closing it. It can be restricted by changing the value of `args.Cancel` to true. The following code describes how to handle the closing of a child using the `DockStateChanging` event. @@ -392,9 +392,9 @@ The fill color of hint shadow/dock preview element can be customized using `Dock ![Customized docking hint shadow color in Docking Manager](Dealing-with-Windows-images/Dealing-with-Windows-img8.jpeg) -## Sizing Docking Windows +## Sizing UWP Docking Windows -`SfDockingManager` allows to set the desired width and height for the docking windows. +`UWP Docking Control` allows to set the desired width and height for the docking windows. The desired height and width can be set for the Dock windows through the AttachedProperty `DesiredWidthInDockedMode` and `DesiredHeightInDockedMode` with the desired values. @@ -419,7 +419,7 @@ The desired height and width can be set for the Dock windows through the Attache ## Occupy Whole Window -To arrange the dock windows to a whole available space in the `SfDockingManager`, set `DockFill` property of `SfDockingManager` as true. +To arrange the dock windows to a whole available space in the `UWP Docking Control`, set `DockFill` property of `SfDockingManager` as true. {% tabs %} @@ -440,7 +440,7 @@ To arrange the dock windows to a whole available space in the `SfDockingManager` ## Enable/Disable ContextMenus -`SfDockingManager` provides ContextMenu's for docking, floating, auto hiding and document windows. +`UWP Docking Control` provides ContextMenu's for docking, floating, auto hiding and document windows. ### Enable/Disable context menu for docking, floating, auto hiding windows diff --git a/uwp/Docking/Docking-Window.md b/uwp/Docking/Docking-Window.md index cc010ef7..b073cf0d 100644 --- a/uwp/Docking/Docking-Window.md +++ b/uwp/Docking/Docking-Window.md @@ -7,9 +7,9 @@ control: SfDockingManager documentation: ug --- -# Docking Window in UWP SfDockingManager +# Docking Window in UWP Docking Control -Docking window is one of the states of `SfDockingManager`. Since Dock is the default value, initially all the children stay as Docking Window. +Docking window is one of the states of `UWP Docking Control`. Since Dock is the default value, initially all the children stay as Docking Window. ![Docking-Window-img1](Docking-Window-images/Docking-Window-img1.jpeg) @@ -24,7 +24,7 @@ The Five sides where the children can be docked are * Bottom * Tabbed -To dock four children of `SfDockingManager` to each side, set the `SideInDockedMode` property with appropriate values. +To dock four children of `UWP Docking Control` to each side, set the `SideInDockedMode` property with appropriate values. {% tabs %} @@ -57,7 +57,7 @@ To dock four children of `SfDockingManager` to each side, set the `SideInDockedM A Docking window can be docked on any side of the Target Docking Window using an attached property named `TargetNameInDockedMode`. -To set the child window as a TabbedWindow, the window should be aware of a Target window name. The following code helps to arrange children of `SfDockingManager` that target a single Docking window docked along Left, Top, Right and Tabbed. +To set the child window as a TabbedWindow, the window should be aware of a Target window name. The following code helps to arrange children of `UWP Docking Control` that target a single Docking window docked along Left, Top, Right and Tabbed. {% tabs %} diff --git a/uwp/Docking/Document-Windows.md b/uwp/Docking/Document-Windows.md index 7d191c84..6b013722 100644 --- a/uwp/Docking/Document-Windows.md +++ b/uwp/Docking/Document-Windows.md @@ -7,9 +7,9 @@ control: SfDockingManager documentation: ug --- -# Document Window in UWP SfDockingManager +# Document Window in UWP Docking Control -Document window is one of the states available in the `SfDockingManager`. To make the children of the `SfDockingManager` as Document, set the child's `DockState` value as `Document`. +Document is one of the window states supported by the` UWP Docking Control`. To display a child window in the document area, set its `DockState` property to `Document`. All the Document windows are added in a `DocumentContainer`. Content can be switched by clicking the item header or choosing item from TabStripMenu. @@ -34,7 +34,7 @@ When the `DockFill` property is set to true, dock windows are allowed to occupy ## Specify Placement for Document Window -A Document window can be added either at the start or end index position in the `DocumentContainer` by setting the `DocumentTabItemPlacement` property of the `SfDockingManager`. The `DocumentTabItemPlacement` enumeration values are `Start` and `End`; the default value is `Start`. +A Document window can be added either at the start or end index position in the `DocumentContainer` by setting the `DocumentTabItemPlacement` property of the `UWP Docking Control`. The `DocumentTabItemPlacement` enumeration values are `Start` and `End`; the default value is `Start`. * Adding Documents at Start position diff --git a/uwp/Docking/Floating-Window.md b/uwp/Docking/Floating-Window.md index 259e97ae..f52da42b 100644 --- a/uwp/Docking/Floating-Window.md +++ b/uwp/Docking/Floating-Window.md @@ -7,9 +7,9 @@ control: SfDockingManager documentation: ug --- -# Floating Window in UWP SfDockingManager +# Floating Window in UWP Docking Control -Floating window is one of the states in the `SfDockingManager`. To make children of the `SfDockingManager` as Float, set the `SfDockingManager` child’s `DockState` values as Float. +Float is one of the window states supported by the `UWP Docking Control`. To display a child window as a floating window, set its `DockState` property to `Float`. {% tabs %} @@ -74,7 +74,7 @@ SfDockingManager.SetSideInDockedMode(ErrorList, Dock.Top); ## Positioning on Desired Location -The `FloatWindow` can be placed at any desired location. To position the `FloatWindow` at the desired location with the required rectangle bounds, invoke the `SetFloatingWindowRect` method of the `SfDockingManager`. +The `FloatWindow` can be placed at any desired location. To position the `FloatWindow` at the desired location with the required rectangle bounds, invoke the `SetFloatingWindowRect` method of the `UWP Docking Control`. {% tabs %} diff --git a/uwp/Docking/Getting-Started.md b/uwp/Docking/Getting-Started.md index 8201b97b..b1771a0a 100644 --- a/uwp/Docking/Getting-Started.md +++ b/uwp/Docking/Getting-Started.md @@ -7,13 +7,13 @@ control: SfDockingManager documentation: ug --- -# Getting Started with UWP SfDockingManager +# Getting Started with UWP Docking Control -This section explains how to implement a similar UI as Visual Studio using the `SfDockingManager`. +This section explains how to implement a similar UI as Visual Studio using the `UWP Docking Control`. -## Add SfDockingManager +## Add UWP Docking Control -There are several ways to add Syncfusion control in to the Visual Studio UWP project. The following will help to add a `SfDockingManager` control through XAML Code. +There are several ways to add Syncfusion control in to the Visual Studio UWP project. The following will help to add a `UWP Docking Control` control through XAML Code. * Create a UWP project in Visual Studio and refer to the following assemblies. @@ -44,7 +44,7 @@ xmlns:layout="using:Syncfusion.UI.Xaml.Controls.Layout"> {% endtabs %} -* Now add the `SfDockingManager` control with a required optimal name by using the included namespace. +* Now add the `UWP Docking Control` control with a required optimal name by using the included namespace. {% tabs %} @@ -58,7 +58,7 @@ xmlns:layout="using:Syncfusion.UI.Xaml.Controls.Layout"> ## Add Children to SfDockingManager -`SfDockingManager` can accept any control as its children. Here five ContentControls have been added as the children of the `SfDockingManager`. +The `UWP Docking Control` can host any control as a child window. In the following example, five ContentControl elements are added as child windows. {% tabs %} @@ -87,7 +87,7 @@ xmlns:layout="using:Syncfusion.UI.Xaml.Controls.Layout"> ## Set Header for the Children -`SfDockingManager` provides an attached property `Header`, that helps to set the header for a child window. Set the Header Property value as “Solution Explorer” for the first child and repeat the same procedure for the remaining children with values "ToolBox", "Properties", "Output" and "Start Page". +`UWP Docking Control` provides an attached property `Header`, that helps to set the header for a child window. Set the Header Property value as “Solution Explorer” for the first child and repeat the same procedure for the remaining children with values "ToolBox", "Properties", "Output" and "Start Page". {% tabs %} @@ -116,7 +116,7 @@ xmlns:layout="using:Syncfusion.UI.Xaml.Controls.Layout"> ## Set State for the Children -`SfDockingManager` provides an attached property `DockState`, that helps to set the State of child windows. Since Dock is the default value of DockState, initially all the children will stay as Docking Window. +`UWP Docking Control` provides an attached property `DockState`, that helps to set the State of child windows. Since Dock is the default value of DockState, initially all the children will stay as Docking Window. To Auto hide the “ToolBox” window, set its `DockState` property as `AutoHidden`. Repeat the same procedure with the `DockState` value as Float and Document for “Properties” and “Start Page” windows respectively to make them as Floating Window and Document Window. @@ -147,7 +147,7 @@ To Auto hide the “ToolBox” window, set its `DockState` property as `AutoHidd ## Set Sides for the Children -`SfDockingManager` provides an attached property `SideInDockedMode`, that helps to dock a window at the required side. Since Left is the default value, initially all the windows are docked to left side. +`UWP Docking Control` provides an attached property `SideInDockedMode`, that helps to dock a window at the required side. Since Left is the default value, initially all the windows are docked to left side. Set the `SideInDockedMode` value as Right for “Solution Explorer” window to dock it on the right side. diff --git a/uwp/Docking/Nested-DockingManager.md b/uwp/Docking/Nested-DockingManager.md index e3e33bba..0f18ad2a 100644 --- a/uwp/Docking/Nested-DockingManager.md +++ b/uwp/Docking/Nested-DockingManager.md @@ -7,9 +7,9 @@ control: SfDockingManager documentation: ug --- -# Nested DockingManager in UWP SfDockingManager +# Nested DockingManager in UWP Docking Control -`SfDockingManager` provides the Nested DockingManager support, which allows adding `SfDockingManager` as a child window to another `SfDockingManager`. +The `UWP Docking Control` provides nested docking support, enabling it to be hosted as a child window within another `UWP Docking Control`. {% tabs %} diff --git a/uwp/Docking/Overview.md b/uwp/Docking/Overview.md index ccfa48a4..0da986b8 100644 --- a/uwp/Docking/Overview.md +++ b/uwp/Docking/Overview.md @@ -7,16 +7,16 @@ control: SfDockingManager documentation: ug --- -# About Syncfusion® UWP SfDockingManager Control +# About Syncfusion® UWP Docking Control -The `SfDockingManager` control implements an architecture, that allows child controls to be docked at any part of a page as in Microsoft Visual Studio. The dock panels containing the child elements can be interactively dragged to any area within the page. These windows can also be floated, tabbed, and auto hidden at runtime. +The `UWP Docking Control` implements an architecture, that allows child controls to be docked at any part of a page as in Microsoft Visual Studio. The dock panels containing the child elements can be interactively dragged to any area within the page. These windows can also be floated, tabbed, and auto hidden at runtime. ## Features -* `SfDockingManager` supports different dock states such as [Docking](https://help.syncfusion.com/uwp/docking/docking-window), [Floating](https://help.syncfusion.com/uwp/docking/floating-window), [AutoHide](https://help.syncfusion.com/uwp/docking/auto-hide-window) and [Document](https://help.syncfusion.com/uwp/docking/document-windows). -* [Tabbed Document Interface(TDI)](https://help.syncfusion.com/uwp/docking/tabbed-window) is available in `SfDockingManager`. +* `UWP Docking Control` supports different dock states such as [Docking](https://help.syncfusion.com/uwp/docking/docking-window), [Floating](https://help.syncfusion.com/uwp/docking/floating-window), [AutoHide](https://help.syncfusion.com/uwp/docking/auto-hide-window) and [Document](https://help.syncfusion.com/uwp/docking/document-windows). +* [Tabbed Document Interface(TDI)](https://help.syncfusion.com/uwp/docking/tabbed-window) is available in `UWP Docking Control`. * Built-in support for TabList ContextMenu and TabItem ContextMenu. -* `SfDockingManager` supports all possible ways to dock the elements. +* `UWP Docking Control` supports all possible ways to dock the elements. * Support for resizing Splitters. * Different types of auto hide animation such as Fade, Scale and Slide. * ToolTip support for all default buttons. diff --git a/uwp/Docking/State-Persistence.md b/uwp/Docking/State-Persistence.md index 2a0fabca..71cfca6a 100644 --- a/uwp/Docking/State-Persistence.md +++ b/uwp/Docking/State-Persistence.md @@ -7,11 +7,11 @@ control: SfDockingManager documentation: ug --- -# State Persistence in UWP SfDockingManager +# State Persistence in UWP Docking Control State persistence is the combined process of `serialization` and `deserialization`. -`SfDockingManager` provides built-in state persistence functionality to save and load the layout across sessions, preserving the dock states and sides of its child windows. It also provides the `ResetDockState()` method to reset the layout to its initial state. +`UWP Docking Control` provides built-in state persistence functionality to save and load the layout across sessions, preserving the dock states and sides of its child windows. It also provides the `ResetDockState()` method to reset the layout to its initial state. ## Saving Current State @@ -61,7 +61,7 @@ dockingManager.LoadDockState(); ## Resetting Initial State -To reset the `SfDockingManager` state, call the `ResetDockState()` method of the `SfDockingManager` instance. +The `UWP Docking Control` state can be reset using the `ResetDockState()` method. {% tabs %} @@ -75,7 +75,7 @@ dockingManager.ResetDockState(); ## Serializing Dynamically Added Children -By default, `SfDockingManager` cannot de-serialize its saved layout properly when its child collection is modified after the DockState is saved. +By default, `UWP Docking Control` cannot de-serialize its saved layout properly when its child collection is modified after the DockState is saved. -The `SfDockingManager` state persistence feature is implemented in such a way that the `SfDockingManager` matches the child collection of the saved layout with the current `SfDockingManager` layout internally and loads properly when the `SfDockingManager` children collection remains the same. Therefore, when any child collection changes dynamically, it results in an improper layout. To avoid this, ensure the children collection of `SfDockingManager` is the same at both save and load time. +The `UWP Docking Control` state persistence feature matches the saved layout with the current child collection and restores the layout accordingly. State persistence works correctly when the child collection remains unchanged between save and load operations. If the collection is modified dynamically, the layout may not be restored as expected. To avoid this issue, ensure that the child collection remains the same during both save and load operations. diff --git a/uwp/Docking/Tabbed-Window.md b/uwp/Docking/Tabbed-Window.md index 8e4a118e..416cbe1c 100644 --- a/uwp/Docking/Tabbed-Window.md +++ b/uwp/Docking/Tabbed-Window.md @@ -7,7 +7,7 @@ control: SfDockingManager documentation: ug --- -# Tabbed Window in UWP SfDockingManager +# Tabbed Window in UWP Docking Control A child window can be arranged as a Tabbed window by setting `TargetNameInDockedMode` and the side value as `Tabbed` using the property `SideInDockedMode`. @@ -236,7 +236,7 @@ dockingManager.DockTabPlacement = Syncfusion.UI.Xaml.Controls.Layout.TabPlacemen ## TabbedWindow Customization -`DockWindow` have an internal `DockTabControl` for Tabbed Windows in `SfDockingManager` and its `DockTabItem` Background and Foreground can be customized. The following table lists the details of the customization properties in DockTabControl. +`DockWindow` have an internal `DockTabControl` for Tabbed Windows in `UWP Docking Control` and its `DockTabItem` Background and Foreground can be customized. The following table lists the details of the customization properties in DockTabControl. ### Customization Properties diff --git a/uwp/Ribbon/BackStage.md b/uwp/Ribbon/BackStage.md index 5282dfb7..75e714eb 100644 --- a/uwp/Ribbon/BackStage.md +++ b/uwp/Ribbon/BackStage.md @@ -7,9 +7,9 @@ control: SfRibbon documentation: ug --- -# BackStage in UWP SfRibbon +# BackStage in UWP Ribbon -Commands can be added to the BackStage similar to the Office UI. The BackStage is completely customizable. To navigate to the BackStage, click on the BackStage button at the left end of the Ribbon Tab Items panel. BackStageTabItems can be easily navigated using the scroll buttons. To navigate back from the BackStage, click on the back button in the top-left corner. The BackStage can be opened and closed programmatically using the `OpenBackStage()` and `CloseBackStage()` methods. +Commands can be added to the BackStage similar to the Office UI. The BackStage is completely customizable. To navigate to the BackStage, click on the BackStage button at the left end of the UWP Ribbon Tab Items panel. BackStageTabItems can be easily navigated using the scroll buttons. To navigate back from the BackStage, click on the back button in the top-left corner. The BackStage can be opened and closed programmatically using the `OpenBackStage()` and `CloseBackStage()` methods. BackStageButton and BackStage TabItems can be added as follows, diff --git a/uwp/Ribbon/Getting-Started.md b/uwp/Ribbon/Getting-Started.md index 5c838542..44dedf2c 100644 --- a/uwp/Ribbon/Getting-Started.md +++ b/uwp/Ribbon/Getting-Started.md @@ -7,11 +7,11 @@ control: SfRibbon documentation: ug --- -# Getting Started with UWP SfRibbon +# Getting Started with UWP Ribbon -This section explains you on how to add SfRibbon in your application. +This section explains you on how to add UWP Ribbon in your application. -## Add SfRibbon +## Add UWP Ribbon Create a Universal Windows Platform project in Visual Studio and refer to the following assemblies. @@ -36,7 +36,7 @@ xmlns:Ribbon="using:Syncfusion.UI.Xaml.Controls.SfRibbon"> {% endtabs %} -2. Now add the `SfRibbon` control with a required optimal name using the included namespace. +2. Now add the `UWP Ribbon` control with a required optimal name using the included namespace. {% tabs %} @@ -74,9 +74,9 @@ Execute the above code to render the following output. ![SfRibbon control for UWP](Getting-Started_images/Getting-Started_img1.jpeg) -## Add Ribbon Tab +## Add UWP Ribbon Tab -The SfRibbon control accepts RibbonTab as children. The following code example illustrates how to add a RibbonTab. +The UWP Ribbon control accepts RibbonTab as children. The following code example illustrates how to add a RibbonTab. {% tabs %} @@ -170,7 +170,7 @@ private async void SfRibbonTab_Tapped(object sender, TappedRoutedEventArgs e) ![Click of Ribbon tab](Getting-Started_images/Getting-Started_img7.jpeg) -## Add Ribbon Bar +## Add UWP Ribbon Bar The RibbonTab accepts RibbonBar as children; here two RibbonBar controls are added inside the “HOME” RibbonTab. @@ -252,9 +252,9 @@ Execute the above code to render the following output. ![Adding Ribbon bar](Getting-Started_images/Getting-Started_img3.jpeg) -## Add Ribbon controls to RibbonBar +## Add UWP Ribbon controls to RibbonBar -The following code example illustrates how to add ribbon controls to the Ribbon bar from code-behind and XAML. +The following code example illustrates how to add UWP Ribbon controls to the RibbonBar from code-behind and XAML. {% tabs %} diff --git a/uwp/Ribbon/Overview.md b/uwp/Ribbon/Overview.md index c11e52de..2fa0a9bc 100644 --- a/uwp/Ribbon/Overview.md +++ b/uwp/Ribbon/Overview.md @@ -7,13 +7,13 @@ control: SfRibbon documentation: ug --- -# About Syncfusion® UWP SfRibbon Control +# About Syncfusion® UWP Ribbon Control -SfRibbon allows the user to implement a Touch based Ribbon layout and functionality. It exposes most of the features of the WinRT touch style. Configuring and designing the layout is very easy through XAML code. +The UWP Ribbon enables the creation of touch-based layouts and interactions. It supports most WinRT touch-style features and offers simple configuration and customization through XAML. * [BackStage](https://help.syncfusion.com/uwp/ribbon/backstage) is provided for placing the items that provide a UI similar to Office. * [QuickAccessToolBar (QAT)](https://help.syncfusion.com/uwp/ribbon/quick-access-toolbar) customization can be done. Commands can be added, removed and rearranged in the tool bar. -* [State Persistence](https://help.syncfusion.com/uwp/ribbon/state-persistence) support is provided for QAT items, QAT state, Ribbon State and the selected Ribbon tab. +* [State Persistence](https://help.syncfusion.com/uwp/ribbon/state-persistence) support is provided for QAT items, QAT state, UWP Ribbon State and the selected tab. * Several [Ribbon controls](https://help.syncfusion.com/uwp/ribbon/ribbon-controls) are provided with three size forms: Extra-Small, Small and Large. diff --git a/uwp/Ribbon/Quick-Access-ToolBar.md b/uwp/Ribbon/Quick-Access-ToolBar.md index 9919b276..dbc2d6c8 100644 --- a/uwp/Ribbon/Quick-Access-ToolBar.md +++ b/uwp/Ribbon/Quick-Access-ToolBar.md @@ -7,9 +7,9 @@ control: SfRibbon documentation: ug --- -# Quick Access Toolbar in UWP SfRibbon +# Quick Access Toolbar in UWP Ribbon -The Quick Access Toolbar in the ribbon instance is used to group the most commonly used commands and access the commands easily without searching for them in the menu bar. The position of the QAT can also be moved above or below the ribbon dynamically. +The Quick Access Toolbar in the UWP Ribbon instance is used to group the most commonly used commands and access the commands easily without searching for them in the menu bar. The position of the QAT can also be moved above or below the UWP Ribbon dynamically. ## Add Default QAT Items diff --git a/uwp/Ribbon/Ribbon-Controls.md b/uwp/Ribbon/Ribbon-Controls.md index 9ff66a3d..6ce99fcf 100644 --- a/uwp/Ribbon/Ribbon-Controls.md +++ b/uwp/Ribbon/Ribbon-Controls.md @@ -7,9 +7,9 @@ control: SfRibbon documentation: ug --- -# Ribbon UI Controls in UWP SfRibbon +# UI Controls in UWP Ribbon -Several Ribbon controls are provided to add to a Ribbon Bar. Button controls are provided with 3 size forms: Extra-Small, Small and Large. +Several UWP Ribbon controls are provided to add to a RibbonBar. Button controls are provided with 3 size forms: Extra-Small, Small and Large. * SfRibbonButton * SfDropDownButton @@ -292,7 +292,7 @@ The SfRibbonGallery displays items with a good look and feel, and is also used t ### SfRibbonGalleryItem -Ribbon Gallery Items are the contents of the Ribbon Gallery Group and it does not restrict the type of content that can be added to it. Use the following code example to add a Ribbon Gallery Item. +UWP Ribbon Gallery Items are the contents of the `SfRibbonGalleryGroup` and it does not restrict the type of content that can be added to it. Use the following code example to add a UWP Ribbon Gallery Item. {% tabs %} @@ -310,7 +310,7 @@ Ribbon Gallery Items are the contents of the Ribbon Gallery Group and it does no ### SfRibbonGalleryGroup -A Ribbon Gallery Group is a collection of Ribbon Gallery Items. The items are grouped in the Ribbon Gallery control based on some classifications. Use the following code to add a Ribbon Gallery Group to the Ribbon Gallery control. +A `SfRibbonGalleryGroup` is a collection of UWP Ribbon Gallery Items. The items are grouped in the SfRibbonGallery control based on some classifications. Use the following code to add a SfRibbonGalleryGroup to the SfRibbonGallery control. {% tabs %} @@ -391,7 +391,7 @@ _ribbonGallery.Items.Add(_ribbongalleryGroup) ## SfRibbonMenu -The SfRibbonMenu control is used to display items. It can contain sub menu items. The following code example is used to add a Ribbon menu control to the application. +The SfRibbonMenu control is used to display items. It can contain sub menu items. The following code example is used to add a UWP Ribbon menu control to the application. {% tabs %} diff --git a/uwp/Ribbon/ToolTip-Support.md b/uwp/Ribbon/ToolTip-Support.md index 64d8e3c4..41f4a8ca 100644 --- a/uwp/Ribbon/ToolTip-Support.md +++ b/uwp/Ribbon/ToolTip-Support.md @@ -7,9 +7,9 @@ control: SfRibbon documentation: ug --- -# ToolTip Support in UWP SfRibbon +# ToolTip Support in UWP Ribbon -Ribbon Controls support tooltips that are used to display small information while hovering the mouse over them. +UWP Ribbon Controls support tooltips that are used to display small information while hovering the mouse over them. {% tabs %} diff --git a/uwp/Ribbon/state-persistence.md b/uwp/Ribbon/state-persistence.md index ded946a2..644a86d1 100644 --- a/uwp/Ribbon/state-persistence.md +++ b/uwp/Ribbon/state-persistence.md @@ -7,16 +7,16 @@ control: SfRibbon documentation: ug --- -# State Persistence in UWP SfRibbon +# State Persistence in UWP Ribbon State Persistence is the combined process of Serialization and Deserialization. Serialization is the process of converting the state of an object to a format where it can be persisted as a file in the memory. The serialized format contains the object’s state information. Deserialization is the complement process of Serialization that converts the stored state information back into the object. A user can save and load the following: * RibbonState (Normal, Adorner, Hide) -* Selected Ribbon Tab +* Selected RibbonTab * QuickAccessToolbar items -* QuickAccessToolBar State (Above or Below Ribbon) +* QuickAccessToolBar State (Above or Below UWP Ribbon) -The Ribbon State Persistence feature helps users to load the state of the Ribbon control that existed when the application was closed. The State Persistence feature gives a more consistent workflow for an application that is executed for a long time. The `Serialize()` and `DeSerialize()` public methods are provided for state persistence. They can be called whenever required. State persistence is not done internally. +The State Persistence feature helps users to load the state of the UWP Ribbon control that existed when the application was closed. The State Persistence feature gives a more consistent workflow for an application that is executed for a long time. The `Serialize()` and `DeSerialize()` public methods are provided for state persistence. They can be called whenever required. State persistence is not done internally. The following code snippet shows how to achieve the serialization and deserialization.