I've recently fitted my apps that have a menu with action bar. The end result: Running on Gingerbread and earlier, I keep the existing menu structure, no change, but on HC and beyond the apps now sport the ole' menu items in action bar form instead. So I have the cake and eat it too. If you are starting from scratch, I'd recommend you approach it as follows: Develop towards a menu structure as if ActionBar had never happened, with one exception: think which items you'd later want to show in the action bar. You'll need compelling icons for that. When the "old school" menu is in place, add the relevant tags and hooks to turn the menu items into action bar items when the app runs on HC and later. Depending on how far back you need compatibility, you may have to use reflection to mask away methods introduced with ActionBar that previously didn't exist. That's the part that stinks, especially if you didn't sink you teeth into it before. There's an older blog entry that explains how to do that: http://android-developers.blogspot.com/2009/04/backward-compatibility-for-android.html
On Feb 3, 5:38 pm, Drun <m.p.ocon...@gmail.com> wrote: > I seen that google is trying to get developers to use action bars > instead of menus, but also know that action bars were not put in till > 3.x, and I am targeting 2.1 as the min SDK. I have seen that there > are a few libraries out there to try to imitate action bars for as far > back as 1.6. > > My question is this, is it worth it to force action bars to older > version of android, or is it ok just to stay with menues, and use that > in the code. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
