Windows Universal. Devices Architecture Frameworks

Transcription

1 Windows Universal Devices Architecture Frameworks

2 Inheritance and specification Windows Mobile since 2000 Native programming using C/C++ in Windows CE.NET CF since 2003 Windows Phone 7 new framework / API Breaks from previous programming models Introduces two new models based in Silverlight (XAML, code behind, MVVM pattern) XNA (used for Xbox games) New versions Windows Phone 8 / 8.1 / 10 8/8.1 start convergence with Windows 8 apps Convergence was completed with version 10 (Universal Windows Apps) Designed from start for great performance Powerful processors with high performance and memory Graphics accelerator processor Touch screen (capacitive) At least 800 x 480 Sensors: accelerometer, GPS, camera three hardware buttons: Back, Start, Search Wi-Fi, 3G+/4G, Bluetooth, NFC Windows Universal 2

3 Emulator Windows Universal 3

4 Development APIs and models Windows Phone 8.0 Windows Phone RT Windows Phone 8.1 WinRT 8.1 WP RT 8.1 Windows Universal 4

5 Windows platform convergence Converged OS kernel Xbox One Windows 8 Windows 8.1 Unified core and app platform Windows Phone 8 Converged app model Windows Phone 8.1 Windows 10 Easy for users to get & stay current Windows Phone 7.5 Windows on Devices Windows Universal 5

6 Windows 10 devices Phone Phablet Small Tablet Large Tablet 2-in-1s (Tablet or Laptop) Classic Laptop Desktops & All-in-Ones Windows 10 Surface Hub Xbox Holographic IoT Windows Universal 6

7 Universal Windows Platform Adaptive User Interface Natural User Inputs One SDK + Tooling One Store + One Dev Center Reuse Existing Code One Universal Windows Platform Windows Universal 7

8 Device family specific extensions Family-specific capabilities Compatible across devices Unique update cadence Desktop extension Windows App Phone extension Xbox extension Universal Windows Platform Windows Core Desktop Device Phone Device Xbox Device Windows Universal 8

9 Windows 10 development stacks WPF WF MFC XAML DirectX HTML Obj.C Swift ios Java Android Web hosted Win32 desktop.net languages C++.Net languages C++ & CX WWA Bridging technologies.net runtime Universal Windows Platform Windows 10 operating system Windows Universal 9

10 Panoramic applications (hubs) Windows Universal 10

11 Application sets with panoramic menus Windows Universal 11

12 Visual Studio and UWP Projects Windows Universal 12

13 Visual Studio and Screen Design Windows Universal 13

14 Interface layout using XAML Windows Universal 14

15 Page code (code behind) Windows Universal 15

16 In the Add Reference option Choosing Extensions Windows Universal 16

17 Memory Application lifecycle Running Suspended Running Suspended Not Running Launched Suspended (5 seconds) Activated Suspended (5 seconds) Terminated (no event) Windows Universal 17

18 A Windows application can have several pages Navigation Each page contains the functionality to navigate to others through the page container which is the Frame object (namespace Windows.UI.Xaml.Controls) It is accessed from the Page object as the Frame property page address is the type of the derived Page class Frame.Navigate( typeof(page1) ); It is possible to go back to the most recent page This behavior can be associated to the Back button (otherwise it will exit the App): Frame.GoBack(); It is also possible to go forward (after navigating back) with: Frame.GoFoward(); // Handler for the Back Button only on phones (prevent to terminate app with the back button) if (Windows.Foundation.Metadata.ApiInformation.IsTypePresent("Windows.Phone.UI.Input.HardwareButtons")) { Windows.Phone.UI.Input.HardwareButtons.BackPressed += (s, e) => { if (Frame.CanGoBack) { Frame.GoBack(); e.handled = true; Windows Universal 18

19 Passing values between pages It is possible to transmit values from a page to another destination page using the Navigate method. It accepts an arbitrary Object as a parameter. For instance: SolidColorBrush brush = (SolidColorBrush) backgrid.background; // the Background brush of a Grid Color clr = brush.color; Frame.Navigate(typeof(Second), clr); The navigation also triggers two events. One of them is in the origin page but the other is in destination page. This last event executes the method OnNavigatedTo() in the destination page, when it is created. We can read, in that handler, the passed Object: override protected void OnNavigatedTo(NavigationEventArgs arg) { Color clr = (Color) arg.parameter; string strcolor = Color: + clr.tostring(); myrect.fill = new SolidColorBrush(clr); base.onnavigatedto(arg); Windows Universal 19

20 Returning values One way to share information between pages can be done through the Application object. The Application object is a singleton visible from all the pages. For instance: public partial class App : Application { public Color? SharedColor { set; get; // declaring a variable inside Application // In MainPage setting the variable (ContentPanel is a Grid object (or other interface control)) (Application.Current as App).SharedColor = (ContentPanel.Background as SolidColorBrush).Color; // In SecondPage retrieving the value protected override void OnNavigatedTo(NavigationEventArgs args) { Color? sharedcolor = (Application.Current as App).SharedColor; if (sharedcolor!= null) ContentPanel.Background = new SolidColorBrush(sharedColor.Value); base.onnavigatedto(args); // In SecondPage setting for returning the value (Application.Current as App).SharedColor = (ContentPanel.Background as SolidColorBrush).Color; Windows Universal 20

21 Returning values (2) It is also possible to put information directly in the destination page of a navigation. For instance: public partial class MainPage : Page { public Color? ReturnedColor { set; get; // In SecondPage public partial class SecondPage : Page { protected override void OnNavigatedFrom(NavigationEventArgs args) { Color clr = (ContentPanel.Background as SolidColorBrush).Color; if (args.content is MainPage) (args.content as MainPage).ReturnedColor = clr; base.onnavigatedfrom(e); when navigating back to the MainPage NavigationServices triggers an event in the originating page, as said before. This event executes the method OnNavigatedFrom() in the originating page. We can access there the destination page class and put in a property the values we want to return. Windows Universal 21

22 Saving and loading settings public partial class App : Application { // Application settings public Brush BackgroundBrush { set; get; void LoadSettings() { IsolatedStorageSettings settings = IsolatedStorageSettings.ApplicationSettings; Color color; if (settings.trygetvalue<color>("backgroundcolor", out color)) BackgroundBrush = new SolidColorBrush(color); void SaveSettings() { IsolatedStorageSettings settings = IsolatedStorageSettings.ApplicationSettings; if (BackgroundBrush is SolidColorBrush) { settings["backgroundcolor"] = (BackgroundBrush as SolidColorBrush).Color; settings.save(); We can call these methods from the handlers of lifetime events. For instance: Application_Launching or Application_Activated LoadSettings() Application_Deactivated or Application_Closing SaveSettings() Settings are persisted values of an application. Usually defined and available in the Application object. Windows Universal 22