Working with Android Actionbarcompact basics
I strongly believe that you should use ActionBarCompat for all new projects that want to support older devices. It also might make sense to migrate existing projects. So read on to learn why you should migrate or use ActionBarCompat right away and how to migrate existing projects.
There are many reasons why you should prefer ActionbarCompat over ActionbarSherlock.
A.First of all this project is by Google, is part of the Support Library and thus likely will support new Action Bar related stuff at the same time Google releases them with stock Android.
B.Another good reason is that it supports the Navigation Drawer pattern right out of the box, while ActionBarSherlock does not. Thus if you want to add this drawer to an existing project/app you should migrate.
C.The last and Important is, that the creator of ActionBarSherlock, Jake Wharton, announced on Google+ that further development of ActionBarSherlock has been stopped. ActionBarSherlock 4.4 is the last release and might get bug fixes – but there won’t be any new features:
So if new functionality is included in actionbar you may not keepup to it with actionbarsherlock.
He’s not too sad either
Here is a list for the difference between the actionbarsherlock and actionbarcompact
I originally developed this project using Eclipse – which is why I occasionally refer to Eclipse specific shortcuts or why I include an Eclipse dialog later on. But the core of this post is independent of the IDE you want to use.
How to proceed?
In the next post i will take you through all the steps needed to get the project deployable again.
I start with the resources and deal with code changes later on. Android’s Development Tools only generate a new
R.javafile when the resources are error-free. And without a correct
Rfile your Java sources won’t compile properly. Thus I prefer to fix resources first.