Up until 3 minutes ago, I was fairly clear on the role of the Android
Compatibility Library (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 the
It's also for cool APIs that can be useful to all app developers but that we
don't necessarily want to add to the platform.
On Mon, Jul 18, 2011 at 2:29 AM, BHL adsfors...@gmail.com wrote:
Up until 3 minutes ago, I was fairly clear on the role of the Android
Compatibility Library (ACL) -- it
On Mon, Jul 18, 2011 at 4:31 AM, Romain Guy romain...@android.com wrote:
It's also for cool APIs that can be useful to all app developers but that
we don't necessarily want to add to the platform.
Out of curiosity, why would you not want to add cool APIs that can be
useful to all app
Because APIs that we integrate in the platform must be forever maintained
and cannot be changed ever. This adds burden to the Android team and it's
less flexible for you because we need to maintain backward compatibility. It
also adds bloat to the platform. A good example of a widget that should
Makes sense - thanks!
-
TreKing http://sites.google.com/site/rezmobileapps/treking - Chicago
transit tracking app for Android-powered devices
--
You received this message because you are subscribed
Up until 3 minutes ago, I was fairly clear on the role of the Android
Compatibility Library (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 the
6 matches
Mail list logo