Hello,

Our developer teams have designed navigation-related controls to support the navigation framework. In this case, we also have supported content controls, Items Control or TabControl.

You might want to see information regarding our ContentControl in here.
Or, see learn Navigation in here.

Hi.

Can be that i don´t understand.

PRISM4 allow define a TABCONTROL or ITEMSCONTROL as Region (as UXFrame) and then navigate to a View (as UXPage) in this Region. The RegionAdapter manage as the view is showed in the Region. In a TabControl, the view is showed as TabItem.  When I navigate to a view already existing in the region, the view is only activated, when the view is not already in the region, the view is created.

I see that the only Region equivalent in the ClientUi is the UXFrame, in the UXFrame when i navigate to a view the previous view is ALWAYS replaced with the new view. In PRISM when used a tabcontrol as region, multiple views can be attached at the same time.

Hello Ramiro,

Our ClientUI already provided rich navigation that is built upon ClientUI Navigation Framework, allowing you to take advantage many of the advanced navigation features available in the framework such as user-friendly URI mapping, loading pages on demand from external XAP , built-in error pages, shell integration, and much more. 

ClientUI Navigation Framework includes UXFrame as the main navigator component and a multitude of navigation UI controls - from hyperlink, navigation button, journal button to menu bar and menu item - supporting navigation to both local XAML pages and external download-on-demand XAP package. To learn more about navigation controls, see Navigation Controls Overview.

The following section lists the links to the navigation controls available in ClientUI.

•  UXFrame
•  UXHyperlinkButton
•  UXJournalButtons
•  UXNavigationBar
•  UXNavigationButton
•  UXNavigationWindow
•  UXTabControl
•  UXTreeView

Regards,
Handy

Hi Handy.

Well, i´m try to explain the difference.

I want that UXTabControl WOULD BE a Navigation Host as UXFRAME.

i would be have a MainPage.xaml with a UXTabControl as Navigation Host as:

<Intersoft:UXPage 
        xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" 
        xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
        xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
        xmlns:Intersoft="http://intersoft.clientui.com/schemas"
        mc:Ignorable="d"
        x:Class="Intersoft.ClientUI.WebSiteNavigation.Samples.MainPage" 
        Title="MainPage Page"
        d:DesignWidth="1024" d:DesignHeight="768">
        
        <Grid x:Name="LayoutRoot">
                <Border>
                        <Grid Margin="10">
                                <Grid.RowDefinitions>
                                        <RowDefinition Height="64"/>
                                        <RowDefinition/>
                                </Grid.RowDefinitions>
                                <Grid x:Name="Header">
                                        <Image Source="/Assets/Images/Branding.png"/>
                                </Grid>                                    
                                <Intersoft:UXTabControl x:Name="ContentFrame" Grid.Row="1">
                                        <Intersoft:UXTabControl.UriMapper>
                                                <Intersoft:UriMapper>
                                                        <Intersoft:UriMapping Uri="" MappedUri="/Views/Home.xaml"/>
                                                        <Intersoft:UriMapping Uri="/Error" MappedUri="/ErrorPage.xaml"/>
                                                        <Intersoft:UriMapping Uri="/{page}" MappedUri="/Views/{page}.xaml"/>
                                                </Intersoft:UriMapper>
                                        </Intersoft:UXTabControl.UriMapper>
                                </Intersoft:UXTabControl>
                        </Grid>
                </Border>
        </Grid>
</Intersoft:UXPage>

and a StackPanel as this

<StackPanel>
     <Intersoft:UXHyperlinkButton Content="Home" NavigateUri="/Home">
     <Intersoft:UXHyperlinkButton Content="Settings" NavigateUri="/Settings">
     <Intersoft:UXHyperlinkButton Content="About" NavigateUri="/About">
</StackPanel>

then, when i push the "About" Hiperlink, the UXTabControl (NavigationHost) navigate to the About.xaml page, if the About.xaml page is not already a TabItem on the TabControl, a new tabItem is created and his content is set to a new About.xaml page created, if the About.xaml page is already exist as TabItem in the TabControl, the TabItem is focused.

I expect that this explainatios is more clear. Excuse my bad english.

regards.

Ramiro Bautista

Hello Ramiro,

Surely you can also achive the scenario by using UXTab control. Our navigation itself already fully integrated with MVVM patern. You can create new tab item by set binding to it source property or focus to existing Tab item by using Selected binding.

Regards,
Handy

Can you to elaborate an example to me?

thanks in advanced.