Modifying DataGrid Commands section and NumericInput control

_config.yml

@@ -190,12 +190,15 @@ navigation:
     controls/datagrid/columns/column-types: 
         title: "Column Types"
         position: 1    
+    controls/datagrid/commands:
+        title: "Commands"
+        position: 9
     controls/datagrid/theming-and-styles: 
         title: "Theming and Styles"
-        position: 12
+        position: 10
     controls/datagrid/howto: 
         title: "How To"
-        position: 13
+        position: 11
     ## End DataGrid
     
     ## Entry
@@ -219,14 +222,6 @@ navigation:
     ## NumericInput
     controls/numericinput:
         title: "NumericInput"
-        ## Entry Sub-Folders
-    controls/numericinput/getting-started:
-        title: "Getting Started"
-        position: 1
-    controls/numericinput/features:
-        title: "Features"
-        position: 2
-        ## End NumericInput Sub-Folders
     ## End NumericInput
     
     ## Path

controls/datagrid/commands/cell-tap.md

@@ -0,0 +1,17 @@
+---
+title: Cell Tap
+page_title: Cell Tap
+position: 1
+slug: datagrid-commands-cell-tap
+---
+
+# Cell Tap
+
+
+## Example
+
+
+## See Also
+
+- [Editing]({%slug datagrid-commands-editing%})
+- [Validation]({%slug datagrid-commands-validation%})

controls/datagrid/commands/commands.md

@@ -1,7 +1,7 @@
 ---
-title: Commands
-page_title: Commands
-position: 9
+title: Overview
+page_title: Overview
+position: 0
 slug: datagrid-commands-overview
 ---
 

controls/datagrid/commands/egiting.md

@@ -0,0 +1,17 @@
+---
+title: Editing
+page_title: Editing
+position: 2
+slug: datagrid-commands-editing
+---
+
+# Editing
+
+## Example
+
+
+## See Also
+
+- [Validation]({%slug datagrid-commands-validation%})
+- [DataGrid Styling]({%slug datagrid-styling%})
+- [Columns Styling]({%slug datagrid-columns-styling%})

controls/datagrid/commands/validation.md

@@ -0,0 +1,16 @@
+---
+title: Validation
+page_title: Validation
+position: 3
+slug: datagrid-commands-validation
+---
+
+# Validation
+
+## Example
+
+## See Also
+
+- [Editing]({%slug datagrid-commands-editing%})
+- [DataGrid Styling]({%slug datagrid-styling%})
+- [Columns Styling]({%slug datagrid-columns-styling%})

controls/numericinput/getting-started/numericinput-getting-started-required-assemblies.md

@@ -1,27 +0,0 @@
----
-title: Required Telerik Assemblies
-page_title: Required Telerik Assemblies
-position: 1
-slug: numericinput-getting-started-required-assemblies
----
-# Required Telerik Assemblies
-
-This article contains a list of the assemblies required by the **RadNumericInput** control.
-
-> The path of the assemblies is relative to the `Binaries` folder that is located in the installation folder of the controls. The default location is:  
-> `C:\Program Files (x86)\Progress\Telerik UI for Xamarin RX XXX\Binaries`.
-
-> All binaries built for a specific platform are placed in a folder named after that platform.
-
-| Platform | Assemblies |
-| -------- | ---------- |
-| Portable | Telerik.XamarinForms.Common.dll<br/>Telerik.XamarinForms.Input.dll |
-| Android  | Telerik.Xamarin.Android.Common.dll <br/>Telerik.Xamarin.Android.Data.dll <br/>Telerik.Xamarin.Android.Input.dll <br/>Telerik.Xamarin.Android.List.dll <br/> Telerik.Xamarin.Android.Primitives.dll <br/>Telerik.XamarinForms.Common.dll <br/>Telerik.XamarinForms.Input.dll |
-| iOS      | Telerik.Xamarin.iOS.dll <br/>Telerik.XamarinForms.Common.dll <br/>Telerik.XamarinForms.Input.dll |
-| UWP      | Telerik.Core.dll <br/>Telerik.Data.dll <br/>Telerik.UI.Xaml.Controls.Data.UWP.dll <br/> Telerik.UI.Xaml.Input.UWP.dll <br/>Telerik.UI.Xaml.Primitives.UWP.dll <br/>Telerik.XamarinForms.Common.dll <br/>Telerik.XamarinForms.Input.dll <br/>|
-
->important As some of the controls included in **UI for Xamarin** suite rely on the **SkiaSharp** rendering library, you should either install [SkiaSharp.Views.Forms](https://www.nuget.org/packages/SkiaSharp.Views.Forms/1.59.0) in all projects included in the Xamarin solution (portable, android, ios, etc.) or in case you do not intend to use any of the Skia-dependent components (Gauges, Rating, BusyIndicator), you could reference the [Lite assemblies]({%slug telerik-light-assemblies%}).
-
-## See Also
-
-- [NumericInput Getting Started]({% slug numericinput-getting-started %})

controls/numericinput/getting-started/numericinput-getting-started.md

@@ -1,37 +0,0 @@
----
-title: Getting Started
-page_title: Getting Started
-position: 0
-slug: numericinput-getting-started
----
-
-# Getting Started
-   
-This example will guide you through the steps needed to add a basic **RadNumericInput** control in your application.
-
->Before you proceed, please, take a look at these articles and follow the instructions to set up your app:
->
->- [Setup on Windows]({%slug getting-started-windows%})
->- [Setup on Mac]({%slug getting-started-mac%})
-
-
-## Example
-
-Once your application is correctly set, you are ready to add a **RadNumericInput** control to the page:
-
-<snippet id='numericinput-getting-started-xaml'/>
-
-In addition to this you need to add the following namespace:
-
-<snippet id='xmlns-telerikinput'/>
-<snippet id='ns-telerikinput'/>
-
-Here is the result:
-
-![NumericInput Getting Started Example](../images/numericinput_getting_started.png)
-
->important The **SDK Browser** and **QSF** applications contain different examples that show RadNumericInput's main features. You can find the applications in the **Examples** and **QSF** folders of your local **Telerik UI for Xamarin** installation.
-
-## See Also
-
-- [Key Features]({% slug numericinput-key-features%})

controls/numericinput/numericinput-commands.md

@@ -1,7 +1,7 @@
 ---
 title: Commands
 page_title: Commands
-position: 2
+position: 4
 slug: numericinput-commands
 ---
 
@@ -27,4 +27,5 @@ Where:
 
 ## See Also
 
-- [NumericInput Getting Started]({% slug numericinput-getting-started%})
+- [Key Features]({%slug numericinput-key-features%})
+- [Globalization]({%slug numericinput-globalization%})

controls/numericinput/numericinput-getting-started.md

@@ -0,0 +1,71 @@
+---
+title: Getting Started
+page_title: Getting Started
+position: 1
+slug: numericinput-getting-started
+---
+
+# Getting Started
+   
+This article will guide you through the steps needed to add a basic **RadNumericInput** control in your application.
+
+* [Setting up the app](#1-setting-up-the-app)
+* [Adding the required Telerik references](#2-adding-the-required-telerik-references)
+* [Adding RadNumericInput control](#3-adding-radnumericinput-control)
+
+## 1. Setting up the app
+
+Take a look at these articles and follow the instructions to setup your app:
+
+- [Setup app with Telerik UI for Xamarin on Windows]({%slug getting-started-windows%})
+- [Setup app with Telerik UI for Xamarin on Mac]({%slug getting-started-mac%})
+
+## 2. Adding the required Telerik references
+
+You have two options:
+
+* Add the Telerik UI for Xamarin Nuget packages following the instructions in [Telerik NuGet package server]({%slug telerik-nuget-server%}) topic.
+
+* Add the references to Telerik assemblies manually, check the list below with the required assemblies for **RadNumericInput** component:
+
+| Platform | Assemblies |
+| -------- | ---------- |
+| Portable | Telerik.XamarinForms.Common.dll<br/>Telerik.XamarinForms.Input.dll |
+| Android  | Telerik.Xamarin.Android.Common.dll <br/>Telerik.Xamarin.Android.Data.dll <br/>Telerik.Xamarin.Android.Input.dll <br/>Telerik.Xamarin.Android.List.dll <br/> Telerik.Xamarin.Android.Primitives.dll <br/>Telerik.XamarinForms.Common.dll <br/>Telerik.XamarinForms.Input.dll |
+| iOS      | Telerik.Xamarin.iOS.dll <br/>Telerik.XamarinForms.Common.dll <br/>Telerik.XamarinForms.Input.dll |
+| UWP      | Telerik.Core.dll <br/>Telerik.Data.dll <br/>Telerik.UI.Xaml.Controls.Data.UWP.dll <br/> Telerik.UI.Xaml.Input.UWP.dll <br/>Telerik.UI.Xaml.Primitives.UWP.dll <br/>Telerik.XamarinForms.Common.dll <br/>Telerik.XamarinForms.Input.dll <br/>|
+
+## 3. Adding RadNumericInput control
+
+You could use one of the following approaches:
+
+#### Drag the control from the Toolbox. 
+
+Take a look at the following topics on how to use the toolbox:
+
+* [Telerik UI for Xamarin Toolbox on Windows]({%slug telerik-xamarin-toolbox%})
+* [Telerik UI for Xamarin Toolbox on Mac]({%slug telerik-xamarin-toolbox-mac%})
+	
+#### Create the control definition in XAML or C#.
+
+The snippet below shows a simple RadAutoCompleteView definition:
+
+<snippet id='numericinput-getting-started-xaml'/>
+<snippet id='numericinput-getting-started-csharp'/>
+
+In addition to this you need to add the following namespace:
+
+<snippet id='xmlns-telerikinput'/>
+<snippet id='ns-telerikinput'/>
+
+Here is the result:
+
+![NumericInput Getting Started Example](images/numericinput_getting_started.png)
+
+>important The **SDK Browser** and **QSF** applications contain different examples that show RadNumericInput's main features. You can find the applications in the **Examples** and **QSF** folders of your local **Telerik UI for Xamarin** installation.
+
+## See Also
+
+- [Key Features]({%slug numericinput-key-features%})
+- [Globalization]({%slug numericinput-globalization%})
+- [Commands]({%slug numericinput-commands%})

controls/numericinput/numericinput-globalization.md

@@ -1,7 +1,7 @@
 ---
 title: Globalization
 page_title: Globalization
-position: 1
+position: 3
 slug: numericinput-globalization
 ---
 
@@ -40,4 +40,5 @@ Depending on the UICulture of the current thread, the result is the following:
 
 ## See Also
 
-- [Key Features]({% slug numericinput-key-features%})
+- [Key Features]({%slug numericinput-key-features%})
+- [Commands]({%slug numericinput-commands%})

controls/numericinput/numericinput-key-features.md

@@ -1,7 +1,7 @@
 ---
 title: Key Features
 page_title: Key Features
-position: 0
+position: 2
 slug: numericinput-key-features
 ---
 
@@ -55,4 +55,5 @@ RadNumericInput supports read-only mode in which the end user cannot type into t
 
 ## See Also
 
-- [NumericInput Getting Started]({% slug numericinput-getting-started%})
+- [Globalization]({%slug numericinput-globalization%})
+- [Commands]({%slug numericinput-commands%})

controls/numericinput/numericinput-overview.md

@@ -9,22 +9,18 @@ slug: numericinput-overview
 
 **RadNumericInput** is a highly customizable input control for numeric data. It allows the user to set/edit a number using the decrease and increase buttons or directly enter it in the input field.  RadNumericInput also provides consistent look with the rest of the controls from the Telerik UI for Xamarin suite.
 
-> **RadNumericInput** is available for the following platforms:
-> 
-> - **Android**
-> - **iOS**
-> - **Universal Windows Platform**
-
 #### Figure 1: RadNumericInput Overview
 ![NumericInput Overview](images/numericinput_overview.png "NumericInput Overview")
 
 ## Key features
 
- * **Minimum/Maximum values**: RadNumericInput allows you to restrict the input value through Min/Max properties, check [here]({% slug numericinput-key-features %}#restricting-the-input) for more details.
- * **Increment Step**: You could define the step that will be applied to the input value upon each decrease/increase. Read more about this [here]({% slug numericinput-key-features %}#setting-the-step-for-decrementincrement-the-value).
- * **Customizable text of the buttons**: You could specify the text of the increase/decrease buttons, so that it’s applicable to your scenario, read [here]({% slug numericinput-key-features %}#setting-buttons-text) for more details.
- * **Commands**: You could use the NumericInput commands to define custom functionality upon decrease/increase action. Check the [Commands]({%slug numericinput-commands %}) topic for more details.
+ * **Minimum/Maximum values**: RadNumericInput allows you to restrict the input value through Min/Max properties, check [here]({%slug numericinput-key-features%}#restricting-the-input) for more details.
+ * **Increment Step**: You could define the step that will be applied to the input value upon each decrease/increase. Read more about this [here]({%slug numericinput-key-features%}#setting-the-step-for-decrementincrement-the-value).
+ * **Customizable text of the buttons**: You could specify the text of the increase/decrease buttons, so that it’s applicable to your scenario, read [here]({%slug numericinput-key-features%}#setting-buttons-text) for more details.
+ * **Commands**: You could use the NumericInput commands to define custom functionality upon decrease/increase action. Check the [Commands]({%slug numericinput-commands%}) topic for more details.
 
 ## See Also
 
-- [Getting Started]({% slug numericinput-getting-started %})
+- [Getting Started]({%slug numericinput-getting-started%})
+- [Key Features]({%slug numericinput-key-features%})
+- [Commands]({%slug numericinput-commands%})