{"id":16468,"date":"2015-01-28T12:30:17","date_gmt":"2015-01-28T17:30:17","guid":{"rendered":"http:\/\/blog.xamarin.com\/?p=16468"},"modified":"2015-01-28T12:30:17","modified_gmt":"2015-01-28T17:30:17","slug":"android-tips-hello-material-design-v7-appcompat","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/xamarin\/android-tips-hello-material-design-v7-appcompat\/","title":{"rendered":"Android Tips: Hello Material Design v7 AppCompat"},"content":{"rendered":"

\t\t\t\t\"NexusAndroid 5.0 Lollipop introduced a complete refresh, known as Material Design, to the Android user interface, which generated rapid adoption throughout the development community. Until Google introduced revision 21 of the Android Support v7 AppCompat library<\/a>, Material Design themes, controls, and features were utilized only if you wanted to target devices running API 21.<\/p>\n

We recently took a look at<\/a> how this library gives developers an opportunity to add the ActionBar to applications targeting older devices all the way back to API 7. However, now you can use this updated library to add Material Design to any of your applications and use new controls like the new Toolbar, which replaces the ActionBar<\/a>. Let’s see how easy it is to get started with the new Support Library v7 AppCompat by updating our Toolbar example.<\/p>\n

Getting Started<\/h2>\n

To start integrating AppCompat into your Android project you will want to install the Support Library v7 AppCompat from the Component Store<\/a> or directly from NuGet<\/a>. This will also install the Support v4 Library, which is required because it provides controls that help maintain backwards compatibility. <\/p>\n

\"Supportv7Component\"<\/p>\n

Since you will now be able to target older versions of Android, you will want to adjust your Minimum and Target Android version under Android Application in the project options.<\/p>\n

\"MinandTarget\"<\/p>\n

Updating to Material Theme<\/h2>\n

There are many differences to the actual resources that are embedded into your app when you use the AppCompat library. This means that the actual themes and attributes are completely different between normal Material and AppCompat themes. You will find three new themes that you can inherit from:<\/p>\n

Dark<\/strong>: Theme.AppCompat\nLight<\/strong>: Theme.AppCompat.Light\nLight with Dark ActionBar<\/strong>: Theme.AppCompat.Light.DarkActionBar<\/p>\n

\"MaterialDesign\"<\/a><\/p>\n

\"StylesFolders\"To use one of these themes, you’ll want to create two folders under your Resources folder named values<\/code> and values-v21<\/code> where you will create a styles.xml<\/code> where you can customize your applications theme. In our values\/styles.xml you will create the base theme of your application and then set custom attributes. You will see that these attributes are different than using the standard Material Theme since they have dropped the android:<\/b> prefix as they are now part of your application.<\/p>\n

values\/styles.xml<\/b><\/p>\n

\n<resources>\n  <style name="MyTheme" parent="MyTheme.Base">\n  <\/style>\n  <!-- Base theme applied no matter what API -->\n  <style name="MyTheme.Base" parent="Theme.AppCompat.Light.DarkActionBar">\n    <!--If you are using revision 22.1 please use just windowNoTitle. Without android:-->\n    <item name="windowNoTitle">true<\/item>\n    <!--We will be using the toolbar so no need to show ActionBar-->\n    <item name="windowActionBar">false<\/item>\n    <!-- Set theme colors from http:\/\/www.google.com\/design\/spec\/style\/color.html#color-color-palette-->\n    <!-- colorPrimary is used for the default action bar background -->\n    <item name="colorPrimary">#2196F3<\/item>\n    <!-- colorPrimaryDark is used for the status bar -->\n    <item name="colorPrimaryDark">#1976D2<\/item>\n    <!-- colorAccent is used as the default value for colorControlActivated\n         which is used to tint widgets -->\n    <item name="colorAccent">#FF4081<\/item>\n     <!-- You can also set colorControlNormal, colorControlActivated\n         colorControlHighlight and colorSwitchThumbNormal. -->\n  <\/style>\n<\/resources>\n<\/pre>\n
Then, inside of your values-v21\/styles.xml<\/code>, you’ll set a few more custom attributes that can take advantage of transitions on devices running Lollipop:<\/p>\n
\n<resources>\n  <!--\n        Base application theme for API 21+. This theme replaces\n        MyTheme from resources\/values\/styles.xml on API 21+ devices.\n    -->\n  <style name="MyTheme" parent="MyTheme.Base">\n    <item name="android:windowContentTransitions">true<\/item>\n    <item name="android:windowAllowEnterTransitionOverlap">true<\/item>\n    <item name="android:windowAllowReturnTransitionOverlap">true<\/item>\n    <item name="android:windowSharedElementEnterTransition">@android:transition\/move<\/item>\n    <item name="android:windowSharedElementExitTransition">@android:transition\/move<\/item>\n  <\/style>\n<\/resources>\n<\/pre>\n
The last step is to open your AndroidManifest.xml under the Properties folder and add reference to your new theme under the application node with android:theme=\"@style\/MyTheme\"<\/code>.<\/p>\n
Integrate Toolbar<\/h2>\n
Previously, we saw how to integrate the new Toolbar<\/a> into your application. The core of that remains the same, except that you will now directly reference the new Toolbar widget from the Support Library. If you haven’t already create a new Android Layout file under Resources\/Layout\/toolbar.axml:<\/p>\n
\n<?xml version="1.0" encoding="utf-8"?>\n<android.support.v7.widget.Toolbar \n    xmlns:android="http:\/\/schemas.android.com\/apk\/res\/android"\n    xmlns:app="http:\/\/schemas.android.com\/apk\/res-auto"\n    android:id="@+id\/toolbar"\n    android:layout_width="match_parent"\n    android:layout_height="wrap_content"\n    android:minHeight="?attr\/actionBarSize"\n    android:background="?attr\/colorPrimary"\n    android:theme="@style\/ThemeOverlay.AppCompat.Dark.ActionBar"\n    app:popupTheme="@style\/ThemeOverlay.AppCompat.Light" \/>\n<\/pre>\n
Note here the use of custom themes directly for the Toolbar and the use of custom attributes. These are a change form the normal use of the Toolbar when not using AppCompat. With our Toolbar setup we can now integrate it into our layouts by user the include<\/code> node to place the Toolbar where you want.<\/p>\n
\n<?xml version="1.0" encoding="utf-8"?>\n<RelativeLayout xmlns:android="http:\/\/schemas.android.com\/apk\/res\/android"\n    xmlns:local="http:\/\/schemas.android.com\/apk\/res-auto"\n    android:layout_width="fill_parent"\n    android:layout_height="fill_parent">\n    <include\n        android:id="@+id\/toolbar"\n        layout="@layout\/toolbar" \/>\n    <LinearLayout\n        android:orientation="vertical"\n        android:layout_width="fill_parent"\n        android:layout_height="fill_parent"\n        android:id="@+id\/main_content"\n        android:layout_below="@id\/toolbar">\n    <\/LinearLayout>\n<\/RelativeLayout>\n<\/pre>\n
Update that Activity<\/h2>\n
The core of any Android application are Activities. When you start using AppCompat, you simply need to update your activities inheritance.\nFrom:<\/p>\n
\npublic class MainActivity : Activity\n<\/pre>\n
To:<\/p>\n
\npublic class MainActivity : ActionBarActivity\n<\/pre>\n
You can now setup your Activity to set the SupportActionBar with the new Toolbar that you have embedded into your layout. I prefer to use an alias to ensure the correct Toolbar is always referenced:<\/p>\n
\nusing Toolbar = Android.Support.V7.Widget.Toolbar;\n<\/pre>\n
Then you simply need to find the Toolbar, set it, and access it in your OnCreate<\/code>:<\/p>\n
\nprotected override void OnCreate (Bundle bundle)\n{\n  base.OnCreate (bundle);\n  \/\/ Set our view from the "main" layout resource\n  SetContentView (Resource.Layout.main);\n\n  var toolbar = FindViewById<Toolbar> (Resource.Id.toolbar);\n\n  \/\/Toolbar will now take on default actionbar characteristics\n  SetSupportActionBar (toolbar);\n\n  SupportActionBar.Title = "Hello from Appcompat Toolbar";\n  \/\/..\n}\n<\/pre>\n
There you have it, you can now run your newly Material Themed Android application on devices that aren’t running Lollipop!<\/p>\n
\"Nexus<\/p>\n
Learn More<\/h2>\n
You can get the full source code for this project in the Support v7 Sample gallery<\/a>. There you will also find other awesome examples of more Support v7 libraries such as CardView, RecyclerView, and Palette. During Evolve 2014, J\u00e9r\u00e9mie Laval and I gave two talks on Material Design from Concept to Implementation. (Part 1<\/a> and Part 2<\/a>) that are available to watch now.  <\/p>\n
Discuss this post in the Xamarin forums.<\/em><\/a>\t\t<\/p>\n","protected":false},"excerpt":{"rendered":"
Android 5.0 Lollipop introduced a complete refresh, known as Material Design, to the Android user interface, which generated rapid adoption throughout the development community. Until Google introduced revision 21 of the Android Support v7 AppCompat library, Material Design themes, controls, and features were utilized only if you wanted to target devices running API 21. We […]<\/p>\n","protected":false},"author":544,"featured_media":39167,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[2],"tags":[4],"class_list":["post-16468","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-developers","tag-xamarin-platform"],"acf":[],"blog_post_summary":"
Android 5.0 Lollipop introduced a complete refresh, known as Material Design, to the Android user interface, which generated rapid adoption throughout the development community. Until Google introduced revision 21 of the Android Support v7 AppCompat library, Material Design themes, controls, and features were utilized only if you wanted to target devices running API 21. We […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/xamarin\/wp-json\/wp\/v2\/posts\/16468","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/xamarin\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/xamarin\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/xamarin\/wp-json\/wp\/v2\/users\/544"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/xamarin\/wp-json\/wp\/v2\/comments?post=16468"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/xamarin\/wp-json\/wp\/v2\/posts\/16468\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/xamarin\/wp-json\/wp\/v2\/media\/39167"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/xamarin\/wp-json\/wp\/v2\/media?parent=16468"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/xamarin\/wp-json\/wp\/v2\/categories?post=16468"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/xamarin\/wp-json\/wp\/v2\/tags?post=16468"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}