![]() So, I thought I would share my simple approach, getting you off the ground with this nifty control. Implementing the SplitView is a little tricky. This problem is the purpose of this article. This means we must build our own implementations and styles from scratch. I can respect the philosophy of not pushing me toward a certain look or feel, but most Windows apps that elect to use the SplitView probably want to use a specific look and feel common in all apps (not all, just many). To me, it is a real pain that the SplitView does not ship with any visual. It is similar to the Grid in that its final visual is the product of the developer or designer. You might have expected the SplitView to include a menu button. You might have expended the SplitView to include a hamburger button. Remember, keep hidden menus as intuitive and easy-to-use as main visuals. ![]() It makes the menu unpredictable users ask “what will I find when I click the menu button?” Bad. But some developers/designers have used the hamburger “drawer” as a catch-all for everything – a disorderly junk drawer, if you will. The hamburger button allows for the main visual to be clean. Perhaps I could offer just a little design guidance, however. The SplitView is a first-party control intended to make implementation easier for developers and designers who choose to include top-level navigation in their Windows app. It is not part of the default template neither is it part of a design prescription for Windows apps. It enables XAML developers to build Windows apps with popular navigation patterns we see on the web and other mobile platforms. The SplitView does not invoke navigation or extend the capabilities of the navigation framework. I believe the most common scenario for the SplitView will be CompactOverlay, a value for DisplayMode that allows the Compact mode to be always visible and the Inline mode to overlay until it is dismissed by the user. Mixed with IsPaneOpen, DisplayMode set one of four possible interaction states. The Content property is intended to be a ContentPresenter for those not using the navigation framework, or the Frame for those who are (which will be most apps).Īnother important SplitView property is DisplayMode. ![]() The Pane property is intended to be some type of navigation affordance for your Windows app. The SplitView has two content properties called Pane and Content. ![]() The purpose of the SplitView is to help developers build popular navigation experiences. This control is like the Grid in that it has no visible interface until something is put inside it. Windows XAML apps, specifically, enjoy several new members to their Visual Studio toolbox including the SplitView. Windows 10 introduces the universal app platform for Windows apps. ![]() Read on, but remember the Navigation View control. That said, there are plenty of things to learn in this article. Again, this blog article remains accurate, but a hand-made Hamburger Menu is no longer the suggested approach anymore. You can review my article on this control in MSDN Magazine: here. Warning NUMBER 2! Since the release of Windows 10 Fall Creators Update (2017), there is a native control giving developers a beautiful Hamburger Menu in their UWP apps. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |