Introducción al desarrollo de aplicaciones universales
•Als PPTX, PDF herunterladen•
2 gefällt mir•1,740 views
Introducción al desarrollo de aplicaciones universales, diferencias de las plataformas, controles comunes e implementación de MVVM
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Mehr von Josué Yeray Julián Ferreiro
Mehr von Josué Yeray Julián Ferreiro (20)
Introducción al desarrollo de aplicaciones universales
- 1. Josué Yeray Julián @JosueYeray Geeks.ms/blogs/jyeray
- 2. Introducción al desarrollo de aplicaciones universales
- 12. 80% exactamente el mismo XAML 20% personalizado Comunes Optimizados Propietarios DatePicker TimePicker CommandBar Button CheckBox ToggleSwitch Slider RadioButton ProgressBar Hub Pivot ListView GridView SysTray
- 15. Button Button Button Contenido del botón Grid Grid.ColumnDefinitions ColumnDefinition ColumnDefinition Grid.ColumnDefinitions Image StackPanel TextBlock TextBlock StackPanel Grid Button HyperlinkButton
- 16. TextBlock ProgressRing IsActive="True" TextBlock ProgressBar Minimum="0" Maximum="250" Value="50" TextBlock ProgressBar IsIndeterminate="True" ¡Importante! Debes desactivar el ProgressRing y ProgressBar cuando no sean visibles. Si no lo haces tendrás una penalización de rendimiento.
Hinweis der Redaktion
- This module is an introduction to building Windows Phone Store Apps which use the same version of XAML used for Windows Store Apps. It does not cover app development using Silverlight – if you want to learn more about that, see the Building Apps for Windows Phone 8 Jumpstart. In this module, we’ll look at the component parts of a Visual Studio project, introduce you to XAML, to XAML controls and how a page is layed out. We’ll look at how you style text and controls, and we will cover some of the System UI that takes up part of the page: the AppBar and the Status Bar.
- The Windows Phone 8.1 development tools are included in Update 2 and later for Visual Studio 2013 Professional or higher editions. Alternatively, you can download and install the completely free and standalone Visual Studio 2013 Express Editions for Windows Store Apps which allows development of Windows Store apps and Windows Phone Store apps. Note that you can still build apps targeting Windows Phone 7.1 and these will run on Windows Phone 7.1 and later – including Windows Phone 8.1, but you cannot target version 7.1 from Visual Studio 2013. You must use Visual Studio 2012 for that.
- The Windows Phone 8.1 development tools are included in Update 2 and later for Visual Studio 2013 Professional or higher editions. Alternatively, you can download and install the completely free and standalone Visual Studio 2013 Express Editions for Windows Store Apps which allows development of Windows Store apps and Windows Phone Store apps. Note that you can still build apps targeting Windows Phone 7.1 and these will run on Windows Phone 7.1 and later – including Windows Phone 8.1, but you cannot target version 7.1 from Visual Studio 2013. You must use Visual Studio 2012 for that.
- The Windows Phone 8.1 development tools are included in Update 2 and later for Visual Studio 2013 Professional or higher editions. Alternatively, you can download and install the completely free and standalone Visual Studio 2013 Express Editions for Windows Store Apps which allows development of Windows Store apps and Windows Phone Store apps. Note that you can still build apps targeting Windows Phone 7.1 and these will run on Windows Phone 7.1 and later – including Windows Phone 8.1, but you cannot target version 7.1 from Visual Studio 2013. You must use Visual Studio 2012 for that.
- When you create a new project in Visual Studio 2013, you get a single Solution which is the container for one or more projects. [Build] This example shows a single project, but in a Universal project, you get two projects, one for Windows Phone and one for Windows. You can add many different kinds of project to a solution such as class libraries or unit test projects. [Build] The library references shows the class libraries that this project references. You can add additional class library references to allow your project to make use of the APIs in a class library. [Build] The Assets folder in a new project contains all the default artwork, which you’ll need to change for your project. Artwork doesn’t have to be in the Assets folder – that’s just the convention used by the New Project templates. [Build] Every Windows Store App has an App class which is where the startup logic sits and where you define app-wide resources such as XAML styles. As you can see, it is defined in two files: the App.Xaml file containing XAML app-wide resources and the App.xaml.cs file where the logic is. [Build] This new project has a single page, again divided up into a Xaml file and it’s code-beside file, MainPage.xaml.cs [Build] Finally, the App manifest is an XML file where you make declarations about how the app operates and the capabilities it requires, such as whether it requires Internet access, or makes use of the user’s location. For those familiar with the old Windows Phone structure: - Assets are in line with Windows 8 for splash/tiles etc - Package.appxmanifest replaces WMAppManifest to configure application properties
- The Windows Phone 8.1 development tools are included in Update 2 and later for Visual Studio 2013 Professional or higher editions. Alternatively, you can download and install the completely free and standalone Visual Studio 2013 Express Editions for Windows Store Apps which allows development of Windows Store apps and Windows Phone Store apps. Note that you can still build apps targeting Windows Phone 7.1 and these will run on Windows Phone 7.1 and later – including Windows Phone 8.1, but you cannot target version 7.1 from Visual Studio 2013. You must use Visual Studio 2012 for that.
- The Windows Phone 8.1 development tools are included in Update 2 and later for Visual Studio 2013 Professional or higher editions. Alternatively, you can download and install the completely free and standalone Visual Studio 2013 Express Editions for Windows Store Apps which allows development of Windows Store apps and Windows Phone Store apps. Note that you can still build apps targeting Windows Phone 7.1 and these will run on Windows Phone 7.1 and later – including Windows Phone 8.1, but you cannot target version 7.1 from Visual Studio 2013. You must use Visual Studio 2012 for that.
- We’ve divided the controls up into three loose groupings: Common controls: These controls are simple ones that you code in the same way and have the same appearance when rendered on Windows and on Windows Phone. Optimized controls: The developer uses the same or similar XAML when coding these controls, but when rendered appear differently as the control itself has logic built into it to render in a way that is appropriate for the platform where it is running. A great example of this is the DatePicker and TimePickers which render as the full page rotary pickers on Windows Phone, but render as drop-down boxes on Windows. Signature controls: These controls aren’t really different from the optimized controls in the way you code them, but they are the controls that allow you to create the signature experiences that define the User Experience on our platforms. Some of these, such as the Pivot are phone-only, but others such as the Hub, ListView or GridView are usable on both, but include built-in support for the animations and touch usage that define our User Expereince. Typically you would define templates for laying out the data they display in ways that give good usability on the different screen orientations and screen sizes of the Phone and Tablet/PC platforms.
- Almost every app needs to display text to the user. In most cases, the element you’ll use is the TextBlock. The TextBlock allows for text display, but isn’t limited to plain fonts. You have access to opentype features through the Typography namespace, and all the standard font features (Size, Weight, Family, etc.) through properties. The TextBlock also supports line breaks and word wrapping, but for more complex text, we have another control. RichTextBlock: Paragraphs, spans, and runs allow for formatting sections of the rich text, using all the same font formatting options employed by the TextBlock. InlineUIContainer element can be included in the text which enables inclusion of any XAML content, including other text controls, images, and even buttons and drop-down list boxes. RichTextBlockOverflow facilitates smooth overflow for multi-column text layout.
- Buttons make things happen. There are other specialized buttons, such as the AppBarButton which we’ll discuss in the context of the AppBar later. The ButtonStyle static resource simply defines the font and margin We’ll cover images more near the end of this session.
- ProgressRing and ProgressBar are used to show that your app is waiting for an operation to complete. Use these sparingly, typically only when the user cannot perform any other meaningful action while something is loading, or to show that a portion of the content on an otherwise usable page is still loading. The performance note here is very important. When a progress ring or bar is no longer visible, be sure to deactivate it by setting IsActive to False.
- The Date and Time Pickers are great examples of controls that you programthe same way on Windows and Windows Phone, but which render quite differently as appropriate for the platform at runtime.
- Flyouts are great for creating transient UI. You use the MenuFlyout to implement a context menu. Other flyouts that are phone only, such as List Picker, Date/Time picker selectors, render full-screen. As with big Windows, all flyouts are ‘light dismiss’ which means when you tap outside the flyout, it is dismissed. For full-screen flyouts, the flyout is dismissed by the user pressing the back button.