Your SlideShare is downloading. ×
CodeCamp Iasi 7 mai 2011 My Friends Around
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

CodeCamp Iasi 7 mai 2011 My Friends Around


Published on

A demo explaining core concepts for building application with Windows Phone 7

A demo explaining core concepts for building application with Windows Phone 7

Published in: Business, 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

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide
  • Two flavors of applications that can run on Windows Phone 7 (over time the differences between the two flavors might get smaller). There is already overlap by sample games written in Silverlight and sample apps written using XNA. Silverlight flavored application ‘ traditional’ application Metro style UI Rich controls + XAML XNA flavored application Highly user interactive Use of 3 D Typically games The Windows Phone Application Platform
  • -Does not have a presenter, has a controller -Request first comes to controller, binds the model with the view -Logic is stored in controller
  • -State and Logic stored in Presenter -Presenter is an abstraction of view, Presenter unaware of view -View is aware of Presenter, however isolated from Model -Uses WPF and Silverlight bindings -A very loose coupling between view and viewmodel, very easy to write unit tests -Growing in popularity (several toolkits MVVM Light, Prism, Caliburn) -Used internally at Microsoft during Expression Blend creation - Why MVVM ? ( Separation of concerns ; Easy data binding(XAML); Testability via unit tests (TDD); Designers vs. developers; Consistency, Maintainability, Scalability )
  • The application life time on a phone is basically similar to any other application. An application that is not running can be started, therefore becomes running and after some time it might be terminated, reentering the not running state. A phone application differs slightly from a ‘normal’ application. [Animate] While you are running on the phone two things can happen, each with their own behavior that we will cover in detail: The application can be obscured The application can be paused
  • There are three different ways to retrieve location on the phone: GPS Location information very accurate Radio drains significant power Initial reading slow (especially if the device has been moved over a long distance without GPX fixes) Does not work indoors Cell Tower Lookup Not that accurate (depends on the distance between cell towers) No additional power requirements (assuming the phone radio is switched on already) Fast location retrieval (if the phone radio is switched on, you are already connected to tower(s)) No 100% coverage WiFi Lookup In between GPS and Cell Tower in both accuracy, speed and battery consumption Works pretty good in larger cities Independent of physical location retrieval, one consistent API is used inside your application. The cloud can help getting more accurate location readings, based on other people having been at the same location (without the need for enabling GPS on a particular, individual device) Location services do not only retrieve Lat/Long readings, but can also resolve address information through reverse geocoding services.
  • Transcript

    • 1.
      • Virtual Orienteering
    • 2.  
    • 3.
    • 4.
    • 5.
    • 6.  
    • 7.
    • 8.
    • 9. Model View Controller
    • 10.
    • 11. INotifyPropertyChanged Interface
    • 12.  
      • Splash screen
      • App constructor
      • Startup event
      • Exit event
      Running Closing Closing Launching Launching Activating Activated Deactivating Deactivated Save state for later use Load state to continue where you left off
    • 14.  
    • 15.
    • 16.
    • 17. Talking to the WCF service WCF service
    • 18.
    • 19. Location Services: Sources of Location Location services + Accuracy - Power - Speed - Indoors - Accuracy + Power + Speed - Wilderness + / - Accuracy + / - Power + / - Speed + / - Urban areas
      • Consistent API across platforms
      • No Emulator Support
      GPS Cell towers WiFi
    • 20.
    • 21.
    • 22.
    • 23.