Windows phone 8 session 13


Published on

Published in: Education, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Windows phone 8 session 13

  1. 1. WP8 USING PHONE RESOURCES 1. Using the Contacts and Calendars in Windows Phone 2. Launchers and Choosers 3. The Windows Phone Camera 4. Taking still images 5. Manipulating the video stream 6. The Windows Phone Microphone 7. The Windows Phone Sensors 8. The Motion sensor 9. Video Content
  2. 2. FOLLOW US Twitter : @chothanihitesh Slideshare : Email : Support : LinkedIn : W8 Publisher : AppStudios WP Publisher : AppStudios Website :
  4. 4. YOUR OBLIGATIONS  Before an application uses contact data in an application you must inform the user and request their permission  You must also ensure that your application manages contact data in a secure way  It would be completely unacceptable for your application to make a copy of the contact list and upload this or use it for spamming
  5. 5. APPLICATION CAPABILITIES  Before an application can use the Contacts and Appointments data on a phone the user has to authorise this capability  Applications identify their capabilities in the WMAppManifest.xml file which is part of the application project  Visual Studio 2012 provides a GUI which can be used to manage these capabilities  Not all the capabilities are enabled when you make a new application
  6. 6. CONTACTS AND CALENDAR PROVIDERS  A Windows Phone application can read contact and calendar information from the different accounts  Windows Live  Exchange (Outlook, Google)  Facebook  Aggregated accounts (Twitter, LinkedIn etc)  The precise abilities depend on the source of the information being used
  8. 8. FINDING DATA SOURCES  Each account has a property that allows an application to identify the source of that account  The StorageKind enumeration has values for all the account types available on Windows Phone
  9. 9. READING CONTACTS  This starts off a contacts load request  This is not a filtered search, all contacts are returned
  10. 10. DISPLAYING CONTACTS  This runs when the search returns  It uses data binding to display the results on the screen in a ListBox
  11. 11. DATA BINDING  This is the XAML that databinds the DisplayName property of the contact to a series of items in a list
  13. 13. FILTERING SEARCHES  By setting the FilterKind value on the search an application can apply a filter to the results  There are a number of filters available  Display Name, Pinned to start, Email address, Phone number  For advanced filtering a LINQ query could be used on the result enumeration  Although this might be a slow operation
  14. 14. DISPLAYING APPOINTMENTS  There is an analogous set of methods for finding appointments  An application can search in a particular account type, for appointments in a particular time range  There is also a search method to search a particular account  The reply is provided as a call back  There are no appointments built into the emulator
  16. 16. CREATING A CONTACT  An application cannot create a contact without the user being aware this action is being performed  This ensures that the user is always aware of what is going on when they are using the program  Applications can create their own custom contact store to store contact details for use in that application  This appears on the People Hub and in contact searches on that phone  To create a contact we use a “Chooser” which will display a confirmation dialog and give the user the option to create the contact or not  The chooser is called asynchronously and will generate an event that tells the application whether the action succeeded or not
  17. 17. LAUNCHERS AND CHOOSERS  A Chooser is used when an application wants to perform a task and get a response from the user  Select a contact or image  On completion of the choice the application is resumed  A Launcher called when application wants to perform a task  Visit a web page or place a phone call  The user can return to the application via the navigation stack  In either case the application is made dormant/tombstoned while the task completes
  18. 18. CREATING A CHOOSER  This creates a chooser to display the save contact dialog
  19. 19. CHOOSER COMPLETION  This method is called when the chooser returns  Some choosers return the result of selection the user has made  This chooser returns whether the user saved the contact or not
  20. 20. CUSTOM CONTACTS STORE  It is only possible for an application to add contacts to any of the users’ configured accounts by using the SaveContactTask  An application can create a Custom Contacts store to which it can add contacts directly without user confirmation  Contacts added in this way will show up in the People Hub on the phone and also in searches for contacts  These contacts can also be linked with other contacts on the phone  Your application can also add custom properties (for example passwords or additional user data) to entries in the custom contacts store
  21. 21. CREATING A CUSTOM CONTACT  This method creates a custom contact with a custom password property  This will not cause a Chooser to be displayed, the contact is stored directly
  22. 22. USING CUSTOM CONTACTS  An application can search through the custom contacts that it has created  Custom contacts created by an application can be linked with other contacts on the phone  They can also be created from vCard electronic business cards  If the user tries to edit a custom contact the phone will offer to create a copy of the account and link it to the custom one, as shown on the right
  23. 23. MAKE A CONTACT
  24. 24. OTHER SAVE TASKS  There are a number of other ‘save’ Choosers available  SaveEmailAddressTask  Save an email address  The address can be added to a contact  SavePhoneNumberTask  Save a phone number  SaveRingtoneTask  Save a sound file as a ringtone
  25. 25. LAUNCHERS VS CHOOSERS  A Chooser allows the given action to return a result  Often the result is an item that has been chosen  Sometimes the result is a status report from an action that may succeed or fail  The application can bind to an event which will be fired once the choice has been made or the action performed  The action may never be completed if the user goes off and does something else  A Launcher causes a change of context into the target of the launch  The current application is made dormant or tombstoned  If the user returns to the application it will be Activated or Launched at that point
  28. 28. CREATING AN APPOINTMENT WITH A LAUNCHER (NEW IN WP8)  This code creates a 1 hour appointment 2 hours into the future  It will have a reminder set for 15 minutes before the event
  29. 29. CREATING AN APPOINTMENT  When the appointment is created the launcher runs in the same way as for an address book entry  The user can assign the appointment to a particular calendar and save it  Note that this is a launcher event  There is no data returned from the task  If your application wants to see if the appointment was created it will have to go and look for it  When the launcher completes the application is Activated from Dormant or Tombstoned
  30. 30. LAUNCHING A BUILT-IN APP USING LAUNCHURIASYNC (NEW IN WP8)  As an alternative to the Launcher APIs, you can use the LaunchUriAsync method to launch system applications  Some built-in applications are *only* available by this technique
  34. 34. ALARMS AND REMINDERS  Time-based, on-phone notifications  Persist across reboots  Adheres to user settings  Consistent with phone UX  These are displayed whether the application is running or not  Reminder notifications can be deep linked to an application page  Notifications can fire once, or repeatedly at configurable intervals  Limit of 50 Alarms and Reminders at a time per application
  36. 36. THE “EGG TIMER” APPLICATION  This is a simple two page Silverlight application  The user sets the time using the slider and then presses the Start Timer button to create a notification  When the notification fires the “Egg Ready” page is displayed if the user clicks through to the application
  37. 37. CREATING A REMINDER  This code creates a reminder and adds it as a scheduled service  The value eggTime holds the length of the delay  This code also sets the url of the page in the application
  38. 38. REMINDER HOUSEKEEPING  Reminders are identified by name  This code finds the “Egg Timer” reminder and then removes it from the scheduler
  41. 41. THE WINDOWS PHONE CAMERA  There are a number of ways the camera can be used by an application  The application can launch the CameraCaptureTask chooser to capture a photograph  The application can use the PhotoCamera class to capture photos or stream video data from the camera  Can use this for product recognition or augmented reality  Use the PhotoCaptureDevice class for advanced photo capture and AudioVideoCaptureDevice for advanced video capture  A real-time video processing application can be registered as a “Lens”  It can be selected by the user from a menu of available lens types  The Lens application will provides a viewfinder display and performs video processing on the signal from the camera
  42. 42. CAPTURING A PHOTO  This task launches the camera so that the user can take a picture  The cameraTask_Completed event fires when the picture is taken  The emulator will return an image containing a small block
  43. 43. CAPTURE COMPLETE  When capture has been made, completed method is executed  This version just displays the image on the screen  You can access the photo stream data to save it
  44. 44. IN APPLICATION CAPTURE  It is also possible to capture an image from within your application  An application can also display a viewfinder  The application can also access the video data directly and use this for augmented reality or to create a customised viewfinder  eg. Barcode scanners  The PhotoCamera class provides camera control and access to the camera video screen
  45. 45. THE PHOTOCAMERA CLASS  This creates a camera and binds a handler to the captured event  The viewfinderBrush source is set to the camera
  46. 46. DISPLAYING THE VIEWFINDER  This is the rectangle in the xaml for the camera viewfinder page  This will display the viewfinder on the screen  The source for the viewfinder brush is set to the camera
  47. 47. INITIATING THE CAPTURE  This is the event handler for the photo button  It asks the camera to take a picture  The current camera settings are used for this  You can override these (for example turn the flash on or off) by setting properties on the camera instance
  48. 48. SAVING THE IMAGE  This saves the image in the camera roll
  49. 49. DISPLAYING THE IMAGE  This saves the image into a BitmapImage which is displayed on the screen in an <Image>
  50. 50. SAVING TO THE LOCAL FOLDER  This saves the image in the local folder
  51. 51. FUNKY CAMERA
  52. 52. CREATING A LENS  A Lens is a custom camera application which can be accessed from within the camera application  An application is flagged as a Lens application by setting a flag in the manifest and providing icons that can be used to browse for the Lens when the camera is in use  I’ve created a FunkyCamera lens application which I have registered in this way
  53. 53. CREATING A LENS APPLICATION  This text must be added to the WMAppManifest.xml file for the application, just after the <Tokens> section  There is no GUI for this alteration, you have to edit the XML directly
  54. 54. ADDING THE LENS ICONS  Three Icons are required, one for each Windows Phone screen size  WVGA 173 × 173 AssetsLens.Screen-WVGA.png  720p 259 × 259 AssetsLens.Screen-720p.png  WXGA 277 × 277 AssetsLens.Screen-WXGA.png  They are all placed in the Assets folder of the application  Use a transparent background to match the Windows Phone color scheme
  55. 55. LENS STARTUP  You can create a URI Mapper to direct the application to the page that implements the viewfinder for the Lens  This can use the string “Viewfinderlaunch” in the destination uri that is activated when the user selects the lens application  Alternatively, if the program only contains a single page this page is displayed  If the user “backs out” of the lens application they will be returned to the camera
  56. 56. IMAGE PROCESSING IN A LENS  The PhotoCamera class is used to provide access to the video stream  This can be used by applications to perform image processing on the live data  Augmented reality  Scanning applications  We are going to use it to make the funky camera display a funky image
  57. 57. FUNKY IMAGE PROCESSING  This separates out the primaries and adds an offset to each  It is called for each pixel in the image
  58. 58. STARTING THE CAMERA  This creates the camera and the bitmap that will contain the image processed output  It binds to the event fired when the camera is ready
  59. 59. STARTING THE CAMERA  When the camera is ready we start the thread that will pump frames into our image processor  This will run alongside our application
  60. 60. GETTING THE IMAGE DATA  This code grabs the preview buffer from the camera and processes it
  61. 61. DRAWING THE IMAGE DATA  This code writes the processed pixels back to a writeable bitmap that is displayed on the screen
  62. 62. CREATING AN AUTO-UPLOADER FOR PHOTOS  You can also create an application that has an auto-upload behaviour for pictures that the user may take  The upload behaviour is a “resource intensive” background task  The application must set the extension shown above and display a settings page where the user can set authentication and upload options  This is a background process and therefore might not get to run
  64. 64. THE WINDOWS PHONE MICROPHONE  The Windows Phone microphone can capture 16 bit audio  Microphone input is managed as part of the XNA framework  It is possible to record sound, process the audio and either store or replay it  There is a complete example of how to do this on MSDN
  66. 66. SENSORS AVAILABLE  There are a number of different sensors:  Accelerometer  Compass  Gyroscope  Inclinometer  Orientation  All the sensors are used in the same way:  They will fire an event when they have a reading  Two APIs for managed code developers:  Microsoft.Devices.Sensors (Windows Phone OS 7.1 API set)  Windows.Devices.Sensors (Windows Phone Runtime)
  67. 67. THE WINDOWS RUNTIME SENSORS LIBRARY  The Windows Phone Runtime sensors APIs are compatible with sensor usage in WinRT on Windows 8  Accelerometer – returns G-force values with respect to the x, y, and z axes  All phones have an accelerometer  Inclinometer - returns pitch, roll, and yaw values that correspond to rotation angles around the x, y, and z axes, respectively  The inclinometer readings are derived from multiple sensors  Gyrometer - returns angular velocity values with respect to the x, y, and z axes  Compass - returns a heading with respect to True North and, possibly, Magnetic North  OrientationSensor - returns a rotation matrix and a Quaternion that can be used to adjust the user's perspective in a game application  Combines the data from the accelerometer, compass, and gyrometer – known as “Sensor Fusion”
  68. 68. DETERMINING SENSOR AVAILABILITY  All the sensor classes have a GetDefault() method  This method only returns values for hardware that has been integrated into the computer by the manufacturer  Returns null if the sensor is not available on that device  All phones will have an accelerometer
  69. 69. STARTING AND STOPPING A SENSOR  Application must set the report interval to a non-zero value prior to registering an event handler or calling GetCurrentReading to activate it  When finished with the sensor, set it to zero  Check the MinimumReportInterval property  Setting a value below the minimum supported interval will either trigger an exception or have undefined results.  Sensor driver will determine the actual report interval
  70. 70. USING THE SENSOR READINGCHANGED EVENT  Register the ReadingChanged event handler to obtain sensor readings  Must set the ReportInterval property first
  71. 71. GETTING READINGS BY POLLING A SENSOR  An application can poll the sensor for the current reading as an alternative to registering a ReadingChanged event handler  The preferred alternative for an application that updates its user interface at a specific frame rate  Must still establish a desired ReportInterval before polling in order to activate the sensor
  73. 73. VIDEO ON THE PHONE  An application can contain a single MediaElement that can play video  The sample above plays a resource file that is part of the project containing the application  You can find a list of supported codecs here: 
  74. 74. STREAMING VIDEO ON THE PHONE  If you want to stream from the internet, just replace the source file with a url  This implementation has the location hard coded into the XAML  You can also do this under program control
  75. 75. CONTROLLING PLAYBACK  The MediaElement exposes methods that can be used to control the media playback  An application can also determine the properties of the media stream  To determine if it can be paused for example
  76. 76. SMOOTH STREAMING  •Windows Phone also supports Smooth Streaming  This is an adaptive streaming that manages the quality of the video signal in response to the abilities of the network connection  Playback quality is managed in real time to handle changes in network performance during viewing  It uses a server side plugin and client code on the viewing device  You can download the viewing software here:
  77. 77. Thank You