Windows phone 8 session 4
0 likes440 views
This document discusses building Windows Phone applications and page navigation. It covers the frame and page controls, with the frame being the top-level container and pages filling the frame's content region. It describes how pages are navigated to and back in a similar way to web pages, with each page having its own URI. It also discusses passing data between pages via query strings or storing a view model in the app class, as well as handling non-linear navigation using the NavigationService.RemoveBackEntry() method.
Windows phone 8 session 4
- 1. BUILDING WINDOWS PHONE APPLICATIONS Page Navigation
- 2. FOLLOW US Twitter : @chothanihitesh Slideshare : http://www.slideshare.net/Chothani-Hitesh Email : chothani.hitesh@gmail.com Support : windows.chothani@live.com LinkedIn : in.linkedin.com/pub/hiteshchothani/6b/311/2b8 W8 Publisher : AppStudios WP Publisher : AppStudios Website : www.appmobinfotech.com
- 3. FRAME AND PAGE •Frame Top-level container control PhoneApplicationFrame class Contains the page control and system elements such as system tray and application bar Page Fills entire content region of the frame PhoneApplicationPage-derived class Contains a title Optionally surfaces its own application bar
- 4. PAGE NAVIGATION XAML apps on Windows Phone use a page-based navigation model Similar to web page model Each page identified by a URI Each page is essentially stateless
- 5. NAVIGATING BACK Application can provide controls to navigate back to preceding page The hardware Back key will also navigate back to preceding page No code required – built-in behaviour
- 6. OVERRIDING BACK KEY •May need to override Back hardware key if ‘back to previous page’ is not logical behaviour For example, when displaying a popup panel User would expect Back key to close the panel, not the page
- 7. OVERRIDING THE BACK KEY
- 8. PASSING DATA BETWEEN PAGES Can pass string data between pages using query strings On destination page
- 9. PASSING OBJECTS BETWEEN PAGES Often, you will pass a data object from one page to another E.g., user selects an item in a list and navigates to a Details page One solution is to store your ViewModel (that is, data) in your App class Global to whole application Pass the ID of the selected item in query string
- 10. HANDLING NON LINEAR NAVIGATION Design your app navigation strategy carefully! If you navigate from ‘third page’ to ‘main page’ and your user then presses the Back key, what happens? User expects app to exit App actually navigates back to Third Page Solution for Windows Phone 7.0 was complex code to handle back navigation correctly, or the Non-Linear Navigation Recipe library from AppHub Windows Phone APIs: NavigationService.RemoveBackEntry()
- 11. NAVIGATIONSERVICE.REMOVEBACKENTRY() When ‘Third Page’ navigates back to MainPage, put a marker in the query string In OnNavigatedTo() in MainPage, look for the marker and if present, remove the ‘ Third Page’, ‘SecondPage’ and original instance of ‘MainPage’ from the navigation history stack
- 12. Thank You