uno-navigation-panel-visibility

Toggle view Visibility in a Grid for lightweight navigation.

9|1|Updated Dec 10, 2024
One-click install
npx skills add https://github.com/unoplatform/studio --skill uno-navigation-panel-visibility
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uno-navigation-panel-visibility
Source: https://github.com/unoplatform/studio/tree/main/plugins/uno-platform-studio/skills/uno-navigation-panel-visibility
Command: npx skills add https://github.com/unoplatform/studio --skill uno-navigation-panel-visibility

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enable lightweight content-area navigation by injecting multiple views into a single Grid and toggling their Visibility, avoiding Frame overhead and preserving visual tree structure.

Core Features & Use Cases

  • Inline, grid-based view switching: registered routes render into a Grid and are shown/hidden via Visibility.
  • No back stack: immediate switching between views without complex navigation stacks.
  • Shell integration: suitable inside TabBar, NavigationView, or responsive shells while keeping views in the visual tree.

Quick Start

Configure the content Grid with uen:Region.Navigator='Visibility' and uen:Region.Attached='True', register your views with RouteMap, and runtime switches will display the appropriate view.

Frequently Asked Questions about uno-navigation-panel-visibility

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I switch views in a Grid using visibility instead of Frame navigation in Uno Platform?

Visibility-based view switching in Uno Platform injects registered routes into a single Grid and toggles their Visibility property, avoiding Frame overhead and preserving the visual tree structure for lightweight content area navigation.

What is the best way to handle lightweight content switching in a responsive shell without a back stack?

Lightweight content switching without a back stack uses a single Grid with uen:Region.Navigator='Visibility' and uen:Region.Attached='True', immediately showing or hiding registered views without complex navigation stacks.

Does visibility-based navigation work with TabBar and NavigationView in Uno Platform XAML?

Yes, visibility-based navigation integrates with TabBar, NavigationView, and responsive shells, toggling view Visibility within a content Grid while keeping views in the visual tree for seamless shell integration.

How do I set up RouteMap registrations for runtime view switching in a Uno Platform Grid?

To set up RouteMap registrations for runtime view switching, register your views with RouteMap to map view names, configure the content Grid with uen:Region.Navigator='Visibility' and uen:Region.Attached='True', and runtime switches will display the appropriate view.

Why use visibility toggling over Frame-based navigation for inline grid-based view switching?

Visibility toggling avoids Frame overhead and preserves the visual tree structure, making it ideal for inline grid-based view switching where immediate transitions between views are preferred over complex navigation stacks.

When should I not use visibility-based navigation in my Uno Platform application?

You should not use visibility-based navigation when your application requires a back stack or complex navigation history, as this approach focuses on immediate switching between views without preserving navigation stacks.