From fb355da43c1889c7b9e92ad3d3d638fda2dfbbdf Mon Sep 17 00:00:00 2001 From: Ben Brookes Date: Fri, 31 Jul 2020 13:27:20 +0100 Subject: [PATCH] Update overview.md Fix spelling mistakes --- app/ng-ui-widgets-category/bottom-navigation/overview.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/app/ng-ui-widgets-category/bottom-navigation/overview.md b/app/ng-ui-widgets-category/bottom-navigation/overview.md index bd0ec78a..d6b3e8d0 100644 --- a/app/ng-ui-widgets-category/bottom-navigation/overview.md +++ b/app/ng-ui-widgets-category/bottom-navigation/overview.md @@ -1,13 +1,13 @@ The `BottomNavigation` component provides a simple way to navigate between different views while providing common UI for both iOS and Android platforms. The recommended scenario suitable for `BottomNavigation` is a high level navigation with 3 to 5 tabs each with separate function. For additional information and details about bottom navigation refer to [the Material Design guidelines](https://material.io/design/components/bottom-navigation.html#usage). -> **Note:** NativeScript 6 introduced two new UI components called `BottomNavigation` and `Tabs`. The idea behind them is to provide more control when building tab based UI, while powering the CSS styling, the icon font support and other specific functionalities. Prior to NativeScript 6, we had the `TabView` component which had top and bottom implementations with different behavoirs for the different platofrms and some styling limitations. With `BottomNavigaiton` and `Tabs` coomponents available, the `TabView` can be considered obsolete. +> **Note:** NativeScript 6 introduced two new UI components called `BottomNavigation` and `Tabs`. The idea behind them is to provide more control when building tab based UI, while powering the CSS styling, the icon font support and other specific functionalities. Prior to NativeScript 6, we had the `TabView` component which had top and bottom implementations with different behaviors for the different platforms and some styling limitations. With `BottomNavigaiton` and `Tabs` components available, the `TabView` can be considered obsolete. The `BottomNavigation` component roundup: Component Primary Objectives: - Used for High Level navigation. - Good for UX structure with 3 to 5 different options. -- Greater control over styling (copared to `TabVIew`). +- Greater control over styling (compared to `TabView`). Limitations - No navigation transitions.