Provide the EnableVirtualization property to the TabView control.

[ArunachalamSyncfusion]

Root Cause of the Issue

The TabView control takes more time to load initially because all tab items are loaded upfront. Customers require a feature to support the lazy loading of tab items and enhance performance.

Description of Change

Introduced a new public property, EnableVirtualization, in the TabView control. When enabled, only the selected tab item is loaded during the initial rendering. Placeholder views (BoxView) are used for non-selected tab items, reducing the initial load time. After the initial load, the content of a tab item will load when you either navigate to the next tab by selecting it from the TabBar or swipe to the next item.

Issues Fixed

• Addressed the performance issue with the TabView control's initial loading.
• Improved load times by introducing lazy loading through the EnableVirtualization feature.
• Ensured that only the selected tab item was rendered initially, while non-selected tab items used lightweight placeholder views.

[PaulAndersonS]

Fixes #32

[Arviksain]

Hi @PaulAndersonS @naveenkumar-sanjeevirayan @SimonCropp @Jeyasri-Murugan As I have mentioned previously the situation, that when tab is opened that time it is loading all the tabitems at a time means all bindingcontext called at a time.

But expected should be when select particular tabItem, then only particular this tabItem's BindingContext should be called and when tap to next tabItem that time 2nd tabItem's BindingContext should be called.

But still the problem is not resolved yet. So, Kindly fix this issue at earliest, As our application already facing this issues in production mode.

Version :- 1.0.3

Opening this issue again