{"id":8658,"date":"2013-12-11T11:00:19","date_gmt":"2013-12-11T16:00:19","guid":{"rendered":"http:\/\/blog.xamarin.com\/?p=8658"},"modified":"2013-12-11T11:00:19","modified_gmt":"2013-12-11T16:00:19","slug":"android-support-library-v7-hello-actionbarcompat","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/xamarin\/android-support-library-v7-hello-actionbarcompat\/","title":{"rendered":"Android Support Library v7: Hello ActionBarCompat"},"content":{"rendered":"

\t\t\t\tTo provide backwards compatibility for new features and controls in Android, Google regularly releases a set of support libraries that developers can integrate into their application. You might already be very familiar with Support Library v4<\/a>, which gives developers that want to provide support all the way back to Android 1.6 (v4) with features such as Fragments, ViewPager, DrawerLayout, and so much more. One lacking feature of the v4 Library was the use of the Action Bar, which there have been a few libraries providing backwards compatibility for, such as LegacyBar<\/a> and ActionBarSherlock<\/a>. While these both provide great Action Bar replacement for targeting pre-HoneyComb devices, Google has recently released Support Library v7, now available on the Component Store<\/a>, which adds a few nice features including ActionBarCompat. The only requirement is that your application must have a minimum target of Android 2.1 (v7) to use the Support Library.<\/p>\n

Recently, Support Library v7 AppCompat has been updated for material design. See our full blog post on how to integrate AppComps’s latest version<\/a> add material design and the new Toolbar to your app.<\/p>\n

\"ActionBar\"<\/p>\n

Support Library v7<\/strong> is split into multiple components including AppCompat<\/a>, GridLayout<\/a>, and MediaRouter (component coming soon). GridLayout<\/a> allows you to create and arrange user interface elements using a grid of rows and columns similar to the Grid in Windows Store\/Phone. MediaRouter Library includes MediaRouter, MediaRouteProvider and additional media classes for Google Cast. These libraries provide functionality for controlling the routing of media channels and streams from an Android device to external screens, speakers, and other destination devices. <\/p>\n

By far the most exciting addition in v7 is the AppCompat library, which adds not only the ActionBar and ActionBarActivity, but also the ShareActionProfider, which allows a standardized sharing action such as sharing text or images from inside the Action Bar.<\/p>\n

Getting Started:<\/h2>\n

To get started with Support Library v7 you will need to simply add the Support Library v7 AppCompat<\/a> from the Component Store into your Android App.<\/p>\n

\"Support<\/p>\n

Once you have the Support Library component added we can now adjust the minimum and target version numbers for our a\\Android application under the project properties. Since we added Support Library v7 we are able to set our minimum to API 7 and set the target to the current android API version of 18.<\/p>\n

\"MinimumVersion\"<\/p>\n

Adding an Action Bar to your application is now as easy inheriting from “ActionBarActivity<\/strong>” instead of “Activity<\/strong>“:<\/p>\n

\npublic class MainActivity : ActionBarActivity\n<\/pre>\n
Styling your Action Bar in AppCompat is a little bit different as now there are unified themes including:<\/p>\n
Holo<\/strong>: @style\/Theme.AppCompat\nHolo Light<\/strong>: @style\/Theme.AppCompat.Light\nHolo Light with Dark Action Bar<\/strong>: @style\/Theme.AppCompat.Light.DarkActionBar<\/p>\n
\"DarkTheme\"\"LightTheme\"\"DarkLightTheme\"<\/p>\n
You can set these themes in the attributes when creating your Activity:<\/p>\n
\n[Activity (Label = "ActionBarCompat", Icon = "@drawable\/ic_launcher", Theme = "@style\/Theme.AppCompat.Light", MainLauncher = true)]\n<\/pre>\n
Adding Actions:<\/h2>\n
Android Action Bar items are defined in your Menu xml files. If you have created menus before you can simply update your xml files as there are a few key differences. First, is that you will want to update your icons so they are the correct size for the Action Bar. You can use Google\u2019s Android Asset Studio to generate these new icons. Second, is that there are new specific attributes on the menu items that define Action Bar specific functionality such as \u201cshowAsAction\u201d, which is used to determine which items are always in the Action Bar or if they are in the over flow.  Here is an example of setting this:<\/p>\n
\n<menu xmlns:android="http:\/\/schemas.android.com\/apk\/res\/android"\n      xmlns:app="http:\/\/schemas.android.com\/apk\/res-auto" >\n    <item android:id="@+id\/action_edit"\n          android:title="@string\/edit"\n          android:icon="@drawable\/ic_action_content_edit"\n          app:showAsAction="ifRoom"\/>\n  <item android:id="@+id\/action_save"\n          android:title="@string\/save"\n          android:icon="@drawable\/ic_action_content_save"\n          app:showAsAction="always"\/>\n<\/menu>\n<\/pre>\n
\"ActionBarItems\"<\/p>\n
The most important part here is that I added a custom \u201cxmlns\u201d definition of xmlns:app=”http:\/\/schemas.android.com\/apk\/res-auto” which is used by Android to find where the property is located when we use it in \u201capp:showAsAction\u201d.<\/p>\n
Share Action Providers:<\/h2>\n
One great native feature is the ShareActionProvider<\/strong>, which allows you to add an item to the Action Bar that will display a list of applications that can handle a specific share intent, such as sharing text or images. <\/p>\n
You can add this to your Menu xml by specifying the actionProviderClass<\/strong> attribute:<\/p>\n
\n<item android:id="@+id\/action_share"\n          android:title="@string\/share"\n          app:showAsAction="always"\n          app:actionProviderClass="android.support.v7.widget.ShareActionProvider"\n          \/>\n<\/pre>\n
We will then get reference to this ShareActionProvider<\/strong> when we create the menu and specify the Intent for it to use:<\/p>\n
\nShareActionProvider actionProvider;\npublic override bool OnCreateOptionsMenu(IMenu menu)\n{\n  this.MenuInflater.Inflate(Resource.Menu.main_menu, menu);\n\n  var shareItem = menu.FindItem(Resource.Id.action_share);\n  var test = MenuItemCompat.GetActionProvider (shareItem);\n  actionProvider = test.JavaCast<ShareActionProvider>();\n\n  var intent = new Intent(Intent.ActionSend);\n  intent.SetType("text\/plain");\n  intent.PutExtra(Intent.ExtraText, "ActionBarCompat is Awesome! Support Lib v7 #Xamarin");\n\n  actionProvider.SetShareIntent (intent);\n\n  return base.OnCreateOptionsMenu(menu);\n}\n<\/pre>\n
\"ShareIntent\"<\/p>\n
ProgressBar in Action Bar:<\/h2>\n
Showing a spinning indeterminate ProgressBar is a great way of notifying your users that you are loading information into your view. You are now able to add this functionality into the ActionBarCompat with just a few lines of code. You will have to request the WindowFeatures.IndeterminateProgress feature and then set the visibility of the ProgressBar<\/p>\n
Here I have setup a button that will toggle the ProgressBar<\/strong> on and off:<\/p>\n
\nbool indeterminateVisible;\nprotected override void OnCreate (Bundle bundle)\n{\n  base.OnCreate (bundle);\n\n  \/\/ Needs to be called before setting the content view\n  SupportRequestWindowFeature((int)WindowFeatures.IndeterminateProgress);\n\n  \/\/ Set our view from the "main" layout resource\n  SetContentView (Resource.Layout.Main);\n\n  SetSupportProgressBarIndeterminate (true);\n\n  var button = FindViewById<Button> (Resource.Id.progress_button);\n  button.Click += (sender, e) => {\n    \/\/ Switch the state of the ProgressBar and set it\n    indeterminateVisible = !indeterminateVisible;\n    SetSupportProgressBarIndeterminateVisibility(indeterminateVisible);\n    \/\/ Update the button text\n    button.Text = indeterminateVisible ? "Stop Progress" : "Start Progress";\n   };\n}\n<\/pre>\n
\"ProgressBar\"<\/p>\n
This is just a peek at some of the features of Support Library v7. After you have installed the components<\/a> make sure that you read the documentation and the sample application showing off a lot more features. For a full sample of the code here feel free to download it from GitHub<\/a> and get ActionBarCompat integrated into your app today!<\/p>\n
Discuss this blog post in the Xamarin Forums<\/em><\/a>\t\t<\/p>\n","protected":false},"excerpt":{"rendered":"
To provide backwards compatibility for new features and controls in Android, Google regularly releases a set of support libraries that developers can integrate into their application. You might already be very familiar with Support Library v4, which gives developers that want to provide support all the way back to Android 1.6 (v4) with features such […]<\/p>\n","protected":false},"author":544,"featured_media":39167,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[2],"tags":[5,4],"class_list":["post-8658","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-developers","tag-android","tag-xamarin-platform"],"acf":[],"blog_post_summary":"
To provide backwards compatibility for new features and controls in Android, Google regularly releases a set of support libraries that developers can integrate into their application. You might already be very familiar with Support Library v4, which gives developers that want to provide support all the way back to Android 1.6 (v4) with features such […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/xamarin\/wp-json\/wp\/v2\/posts\/8658","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=8658"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/xamarin\/wp-json\/wp\/v2\/posts\/8658\/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=8658"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/xamarin\/wp-json\/wp\/v2\/categories?post=8658"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/xamarin\/wp-json\/wp\/v2\/tags?post=8658"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}