Actionbar implementation in earlier Android versions

-

 

The ActionBar was introduced in Android 3.0 (API 11) and enable us to develop applications with a more fluid navigation using Fragments. Ever since, we are using the Action Bar in pretty much every application.

The question is, how to be able to implement the Action bar in earlier < 3.0 API’s ?

The support library which enables us to use Fragments for devices with API<3 is great and does the work just like we want and need. but what about action bar support? it’s not out of the box even in the support library. the excepted method of implementing Action bar for those earlier versions is actionbarsherlock(or ABS) just to keep things short.

The ABS is an open-source expansion of the Android support library and it enables us to write application without having to make a implicit adjustment to out activities in order to support Action bars.

The usage is simple:

1. download the project from the ABS website at : http://actionbarsherlock.com/

2. inside the archive you’ll find a folder named library, you’ll only need this as a project to be included in the build path of your application.

3. start a new project (create from existing code) and choose the library folder which you’ve extracted from the download archive.

4. make sure that the manifest for your project and the library project matches in the minSDK and targetSDk versions

5. on the properties of your project – > android –> at the bottom you need to include the library to the build path, the project will rebuild in order to have all the needed references.

6. in API 4+ there’s the theme issue (Hollo.Dark, Hollo.Light etc..) , you need to make sure that each activity in your application has the reference to the style :

android:theme="@style/Theme.Sherlock.Light"

* or any other ABS theme which come ready to use in the library

7. In your app , make sure that instead of extending Activity class, you are extending the SherlockActivity class.

8. from now on you are using the support library which comes within the ABS library, so please make sure that all the native references are updated, for example: Menu, MenuInflater,MenuItem:

 

import com.actionbarsherlock.app.SherlockActivity;
import com.actionbarsherlock.view.Menu;
import com.actionbarsherlock.view.MenuInflater;
import com.actionbarsherlock.view.MenuItem;

9. in order to enable Home as enabled for the back button please user :

getSupportActionBar().setDisplayHomeAsUpEnabled(true);

instead of:

getActionBar()

And that’s it, you’re golden

Comments

Post a Comment

Popular posts from this blog

Spinner VS AutoCompleteTextView

-
Image
       We’ve all been in a situation where we needed to show a list of some sort, a list which should be triggered by a user interaction (click, tap, etc..) A list is simple enough, probably even a spinner if we don’t want to spend that much screen real-estate on showing a list which the user clicks once and probably doesn’t need to see it after that. A spinner can be a real bug once there are too much entries for the user to choose from, how much is too much? that’s a good question – probably it differs from user to user, and probably this will have some performance issues with areal large number of entries, you cannot scroll forever to find what you’re looking for. A simple solutions for the problems mentioned above is an AutoCompleteTextView. it’s a control which is basically a combination of a TextView, EditText, and a Spinner all wrapped up in a single easy to use and configurable control. let’s see how it’s done:   first, in the layout file, create an AutoCompleteTextView
Read more

Utilizing Http response cache

-
     A typical mobile application will probably consume some resources from a web server using http requests. This repeated task has some drawbacks: Bandwidth has a cost, polling the same data over and over again results in a waste of user’s quota. the responsiveness and user experience is compromised once the user keeps waiting for data. If the requested data hasn’t changed on the server, then there’s no reason for us to fetch it. Of course, local caching of data is a must, but we also need to be able to refresh the data if it has changed on the server. A simple solution which comes out of the box for API 4+ is http response caching. Http response caching is a mechanism which enables us as developers to save a footprint of the response utilizing the abilities of the Http protocol. Basically, is holds a simple cache of the response which can be defined and enabled in code, and it prevents from fetching unchanged data from the server which was already fetched and processed into t
Read more

ORM for android

-
     ORM – Object relational mapping has been around for quite some time now. Basically it’s a piece of software (regardless of targeted platform), which simplifies the connection between objects (as in OOP) and data in database (mostly used is tables based relational database), and it exists in order to help simplify bridging the gap between the two in our development process.     Microsoft's Entity framework is a great example for a robust easy to use framework which allows creating and querying the database from an object’s point of view with classic object oriented programming paradigms while maintaining all DB construction’s needs such as relationships between objects (tables) such as one to many or many to many including all the indexing, optimization etc..      In android, we have SQLite as a database platform, from simple to advanced application, it’s likely to assume that we’ll need some relational database to store and retrieve local data from the database using the bas
Read more