Back to: Magellan Home
In web applications, requests are initiated from the web browser, and are sent to a web server for processing. In smart clients, the application is responsible for both initiating the request and processing it. To this end, Magellan provides a Navigator class and INavigator interface
(Work in progress)
Back to: Magellan Home
Discussion
Dean Thrasher
Why did you decide to write your own Navigator class instead of using the built-in NavigationService class provided as part of the Windows.System.Navigation namespace? Was it for the reasons you outlined in your Magellean and WPF Page Management Woes article?
One advantage to using the built-in NavigationService class is the support for simple navigation using the Hyperlink element. Does Magellan support the Hyperlink element? Most of your examples use Button elements to control navigation instead. As a web guy, I find hyperlinking a more natural concept for moving around.
Paul Stovell
Hi Dean,
The issue with the built in NavigationService is you can only navigate to a .XAML page. That doesn't give a chance for the controller to intercept to decide which page to show.
However, you can use the Click event of the Hyperlink to navigate, or use the NavigateAction/NavigateBehavior to perform the navigation.
Paul
Dean Thrasher
Ah. That makes sense. The built-in NavigationService simply links one View (or .XAML page) to another directly.
That also explains why other MVC/MVP/MVVM frameworks avoid using the built-in service, too.