[android-developers] Re: Role of the Compatibility Library?

hi,

Could you please clarify one moment - if my app was build with ACL and
runs on Honeycomb tablet is it still use ACL classes or Honeycomb
platform native? thanks.

On Jul 16, 9:04 am, Mark Murphy <mmur...@commonsware.com> wrote:
> Up until 3 minutes ago, I was fairly clear on the role of the AndroidCompatibilityLibrary (ACL) -- it was to provide backwards-compatible
> clones of stuff that exist "for realz" only in newer versions of
> Android.
>
> However, Roman Nurik just tweeted:
>
> "ViewPager and PagerAdapter are in theCompatibilityPackager3 as
> part of the Android 3.2 SDK release"
>
> pointing to:
>
> http://developer.android.com/sdk/compatibility-library.html
>
> ViewPager, PagerAdapter, and kin are classes *presently unique to the ACL*.
>
> I couch that with "presently" as, for all we know, those classes could
> show up in a yet future version of Android, and they were added to the
> ACL now because, ummm, they stowed away on the release or something.
>
> Does anyone out there with greater insight into the ACL have a clearer
> explanation of its role, in light of these ACL-only classes?
>
> Thanks in advance!
>
> --
> Mark Murphy (a Commons Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy
>
> Android Training...At Your Office:http://commonsware.com/training

--
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en