What's the best way of approaching having a single application window, which is capable of loading multiple UIs within it? To clarify, I'd like to have a single window with a basic menu, which, depending on the option clicked on that page, launches a completely new UI within the same window (completely replacing the menu interface). Basically, I'd like to be able to replace the content of the menu window, with the content of new user interface, and then to be able to go back to the menu interface again later.
I'd preferably like to do this in a non-paged, non-navigated WPF app, but if it's going to be easier to make this navigationally based, then I'll consider going the XBAP method. Is there a part of the WPF framework that will allow this kind of interaction? I've looked at doing a content load on XAML files, and replacing the Window.Content with this, but this seems *very* sloppy and not very elegant.
Is there a better way?
Loading
Suchit KhannaPosted May 27, 2009, 12:43 AM
According to your requirement I guess page based WPF application would be the best choice, Is there any specific reason for which you are not considering it and going for XBAP applications, mind you will have serious limitations..... I would suggest that --> WPF framework's page based navigation architecture is best suited for such senario's only... One example of this is Window's Vista itself. Its easy to use, UI is user friendly... So my suggestion is like one above :-)