History log of /frameworks/support/v4/Android.mk
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
dd2c232b1f64d270269a2f515b4f9d448893f858 10-Oct-2013 Adam Powell <adamp@google.com> Build kitkat support components against API 19

Bug 10804178

Change-Id: I65fa588bd536a64394d1525481d194d809e9d10a
/frameworks/support/v4/Android.mk
b7c7eb8b8c520f5a3256205a42e42e071854d929 18-Sep-2013 Mindy DelliCarpini <mindyp@google.com> Make the isQuickScaleEnabled method


bring it back now that current.jar is updated

Change-Id: I18d01ab14b7ab77cc6d644a9d20ab56d7be71856
/frameworks/support/v4/Android.mk
b53d9592fac077fe35deab6fdfd185da7eb2bc5f 18-Sep-2013 Mindy DelliCarpini <mindyp@google.com> Revert "Make the isQuickScaleEnabled method"

This reverts commit cb80ea4aad01cd26f295e173f37dcf9e20be6bca.

Change-Id: I97efb94dcd4a963f9ab68dcc29c4aa4198f085aa
/frameworks/support/v4/Android.mk
cb80ea4aad01cd26f295e173f37dcf9e20be6bca 10-Sep-2013 Mindy Pereira <mindyp@google.com> Make the isQuickScaleEnabled method

Change-Id: I328dd6e73c29b1751b3473d25e0542c14efe1bdc
/frameworks/support/v4/Android.mk
eed274d8547b206963e7abf1440f2761934215d9 18-Jun-2013 Adam Powell <adamp@google.com> am d2590d21: am c92fc3db: Merge "Refine SlidingPaneLayout opacity detection" into jb-mr2-ub-dev

* commit 'd2590d2117cf0adfe8f869b95831c4def7f4500d':
Refine SlidingPaneLayout opacity detection
c029e15f5a4709214cb433a562256586824a0f33 18-Jun-2013 Adam Powell <adamp@google.com> Refine SlidingPaneLayout opacity detection

Before API 18, View#isOpaque would aggressively return false for
scrollbar modes that still implied view opacity and SlidingPaneLayout
relied directly on the format of the background drawable as a
fallback. In API 18 and above, this has been fixed.

Use View#isOpaque as the primary signal and only fall back on the
background drawable check on older platform versions if isOpaque
returns false. This allows applications with custom views to override
isOpaque as needed when they're Really Really Sure that they want
SlidingPaneLayout's detected opacity behavior instead of creating a
Drawable that lies.

Bug 9466551

Change-Id: I668f0a79fe83e09a36878d4c2f8b77258d55af6b
/frameworks/support/v4/Android.mk
16b9c32acfd3e6c96bd5571742bd09927f53bffe 21-May-2013 Ying Wang <wangying@google.com> Clean up dist files.

Change-Id: Ib22ec5e867955a71d4e42db0d2c56775fe37a4ae
/frameworks/support/v4/Android.mk
b507e525a61ed761eecfc2eaaf19af7e8db5dca5 20-Mar-2013 Jeff Brown <jeffbrown@google.com> Move support library media router to v7 package.

Resolved some TODOs related to missing resources.

Bug: 8175766
Change-Id: I57632d0a961de58a5dd53e889b4fd39832b5fba0
/frameworks/support/v4/Android.mk
c21f57ed68b81a77167f1df000b0e272e1598bc0 08-Mar-2013 Jeff Brown <jeffbrown@google.com> Add media router and display manager to support library.

The support library MediaRouter API is somewhat different from
the framework's existing MediaRouter API. It is designed to
be simpler and easier to extend.

In the new MediaRouter, routes are published by MediaRouteProviders.
MediaRouteProviders replace the concept of UserRoutes.
The built-in SystemMediaRouteProvider publishes the default
system routes and interoperates with the framework MediaRouter.

Each route now declares its capabilities and behaviors by way
of MediaControlIntents. The type of the route (live audio,
live video, or remote playback) is specified by the categories
of media control intents that the route supports. A route
may support any number of custom provider-defined media control
intent categories that provide access to specialized features.

The old concepts of route categories and route groups have
been removed. Route providers are now responsible for implementing
the route grouping and configuration through some UI of their
own that is not managed by the media router.

This patch does not include support for route icon drawables,
the new route picker UI or route provider services. These features
will be added in follow on patches.

Change-Id: I10cf078917d053a916254a5aa9d208b8cfd341ea
/frameworks/support/v4/Android.mk
0fc5bd7644f7563f7b59bd1017df9c938857e794 05-Feb-2013 Svetoslav <svetoslavganov@google.com> Updating support lib v4 with new accessibility APIs.

1. Adding support for the new APIs for getting/setting the
view id of the AccessibilityNodeInfo's source.

2. Adding toString() APIs to AccessibilityNodeInfo to workaround
a framework issue where we throw an exception if one of the
node actions is not known for the current platform version.
Unfortunately the exception throwing code is already shipped
and clients should use the support lib to avoid crashing.

3. Adding new constants from AccessibilityServiceInfo to the
corresponding support class.

bug:8131980

Change-Id: I7ec484800c2adf8c1d6f49ffeeed551ff5e6ad26
/frameworks/support/v4/Android.mk
8295680249abdd0cffece49cbefb337f03425c20 05-Dec-2012 Jim Guggemos <jimg@google.com> LOCAL_SDK_VERSION=17 for android-support-v4-jellybean-mr1

This was set to "current" previously.

Change-Id: Ie80184ccba8fd9bd5dfe378fae7a19e7d14a2edd
/frameworks/support/v4/Android.mk
0af001b9e0d173f6b9836e66539bf764b897c36f 21-Sep-2012 Svetoslav Ganov <svetoslavganov@google.com> This is revert of a reverted patch to wait for some build system changes.

This reverts commit 83df688ed22cdc90e7eae83e13ddf1b3ba378947

Change-Id: Ia81d72ea349d603a022287963eb41c0e1c1d41a6
/frameworks/support/v4/Android.mk
96c8829c8bfb5f6651cc06b4c19a6b27cf67e0e4 22-Sep-2012 Baligh Uddin <baligh@google.com> Revert "This is revert of a reverted patch to wait for some build system changes."

Broken Build.

This reverts commit f959f51d9eafa48a08e43e694b58f289315c119e

Change-Id: If21cdaa4560282bf1bd12691a4ee174aeb3244ab
/frameworks/support/v4/Android.mk
f959f51d9eafa48a08e43e694b58f289315c119e 21-Sep-2012 Svetoslav Ganov <svetoslavganov@google.com> This is revert of a reverted patch to wait for some build system changes.

This reverts commit 83df688ed22cdc90e7eae83e13ddf1b3ba378947

Change-Id: I4dad0ccf1d2bb03dbfe73bc9e123266bcbe19136
/frameworks/support/v4/Android.mk
83df688ed22cdc90e7eae83e13ddf1b3ba378947 14-Sep-2012 Svetoslav Ganov <svetoslavganov@google.com> Temporary revert until unbunded builds are configured porperly to either use a prebuilt of the framework and the support lib or none.

Revert "Compatibility support for new accessibility APIs in View."

This reverts commit 7cf0b33a31b57e78a06214a43f580598e0f35031

Change-Id: I47e7e625eaf65e70a37bcf30751953ac2d2b2000
/frameworks/support/v4/Android.mk
7cf0b33a31b57e78a06214a43f580598e0f35031 13-Sep-2012 Svetoslav Ganov <svetoslavganov@google.com> Compatibility support for new accessibility APIs in View.

1. For accessibility purposes it is important to be able to associate
a view with content with a view that labels it. For example, if
an accessibility service knows that a TextView is associated with
an EditText, it can provide much richer feedback.

This change adds compatibilityt support for the APIs for setting
a view to be the label for another one and setting the label for
a view, i.e. the reverse association.

bug:5016937

Change-Id: I54ea51f6e6ff46447c8f4d64383cb88f62d99812
/frameworks/support/v4/Android.mk
f3ed7c56e6c409d27c60f7d74c026906593c21d4 13-May-2012 Svetoslav Ganov <svetoslavganov@google.com> Update the API version checks in the support lib.

1. Since the API version has been finalized this change
updates the SDk version checks to use the JellyBean
verson number.

bug:5947249

Change-Id: I1011f76612f95ceef179acd0b8ab258c055a8369
/frameworks/support/v4/Android.mk
70e96ebf69f91da84681a6263b3862c63d53ab11 11-May-2012 alanv <alanv@google.com> Update AccessibilityNodeInfoCompat for JellyBean.

Also ensures that non-null wrapper is always used and fixes compiler warnings.

Bug: 6469473
Change-Id: I2029ae87d5525a54d26a559b8304f04fd39144f6
/frameworks/support/v4/Android.mk
95baf8fd79ebb4171a4ef495b1f32829ca28f186 26-Apr-2012 Ying Wang <wangying@google.com> Build android-support-v4-jellybean against SDK 16.

Bug 5947249.

Change-Id: Ic74154c2701bbc7206c8aea3bf9ce531fa96ef1a
/frameworks/support/v4/Android.mk
956b013dfda37760b0232ed6d448900a546d2903 31-Jan-2012 Svetoslav Ganov <svetoslavganov@google.com> Adding APIs for using AccessibilityNodeProvider to android-support-v4.

1. AccessibilityNodeProvider APIs enable a View to report a virtual
sub-tree rooted at it. Adding APIs that enable using that facility
in a backwards compatible fashion.

bug:5940165

Change-Id: I441762f4f943d5e0d149c114f974c992be4df20d
/frameworks/support/v4/Android.mk
c64858f808c159a8b144d22e3168459074cdc181 31-Jan-2012 Svetoslav Ganov <svetoslavganov@google.com> Fixing issues with accessibility APIs in the support-v4 library.

1. AccessibilityRecordCompat#getSource() was not implemented
correctly. If the internal implementation returns null
then this method should also do so for consistency.

2. AccessibilityNodeInfoCompat#getParent() and getChild()
making incorrect recursive call and also not returning null
if the internal implementation does so.

3. get/setMaxScrollX and get/setMaxScrollY now exposed for
devices running MR1.

bug:5920810
bug:5920093
bug:5913803

Change-Id: I74d73491ec7640f3074b0a6f094430f877ecf6ec
/frameworks/support/v4/Android.mk
73df5d38da5c66eca9dfdb93de9c17d8e9e6c6d6 29-Jan-2012 Omari Stephens <xsdg@android.com> Revert " Fixing issues with accessibility APIs in the support-v4 library."

This reverts commit bf0a90aac4fb0392d975887eb1cbe8f55827d91f.

To fix build
/frameworks/support/v4/Android.mk
bf0a90aac4fb0392d975887eb1cbe8f55827d91f 28-Jan-2012 Svetoslav Ganov <svetoslavganov@google.com> Fixing issues with accessibility APIs in the support-v4 library.

1. AccessibilityRecordCompat#getSource() was not implemented
correctly. If the internal implementation returns null
then this method should also do so for consistency.

2. AccessibilityNodeInfoCompat#getParent() and getChild()
making incorrect recursive call and also not returning null
if the internal implementation does so.

3. get/setMaxScrollX and get/setMaxScrollY now exposed for
devices running MR1.

bug:5920810
bug:5920093
bug:5913803

Change-Id: Iffaf34d16e463933b55f8cf6d79d21918aa1145b
/frameworks/support/v4/Android.mk
2f57132efb6e8ce3aa19d4f39518073e00680265 20-Sep-2011 Ying Wang <wangying@google.com> Build the ics support libraries against SDK 14.

Change-Id: Ie1dedb7c087d8460b030381508b300ec20a60e29
/frameworks/support/v4/Android.mk
560114f591be31d0fb73c26a1ee1cc0a15184aba 03-Sep-2011 Adam Powell <adamp@google.com> Make ViewPager aware of EdgeEffect on ICS devices.

Add EdgeEffectCompat for apps that also want to selectively show the
ICS-style edge effect.

Add ViewCompat methods for checking/changing over scroll modes on GB+

Change-Id: If0de62c389c9eaef4593f2321ee99787b13b2418
/frameworks/support/v4/Android.mk
bc889e39e279fcf8c3d35fc11d8052c002eddf38 14-Jun-2011 Adam Powell <adamp@google.com> Add support for horizontal scrolling within a ViewPager (ICS-only)

Change-Id: I7ceb2eb65536a2dc7a9323202c1999071cae237a
/frameworks/support/v4/Android.mk
5c1637087453de15e31861f073eae5133c4e9f7b 06-Jun-2011 Dianne Hackborn <hackbod@google.com> Move PagerView down to the v4 support lib.

Adds in standard adapters for using PagerView with the fragment support library.

Also bring in the most recent HC fragment API and impl changes so that the support
lib matches it.

Change-Id: Id8a590378b8c544a92df4f3c11af323c930aa5fd
/frameworks/support/v4/Android.mk
e4417c91a0bb2fba42a0aaa99edcca1b238af21a 05-Apr-2011 Dianne Hackborn <hackbod@google.com> DO NOT MERGE. Integrate support work from master.

First submit of FragmentPager class.

This provides an easy way to build a UI where the user can
swipe left or right through its elements. The elements are
implemented as fragments, and the class takes care of managing
those fragments as the user navigates through it.

This implementation also introduces a new FragmentManager
concept of a "detached" fragment -- basically a way for you
to put a fragment in the same state as when it is on the
back stack, where the framework is managing its current state
but it is no longer actively running.

Also required the introduction of new compatibility code for
MotionEvent and VelocityTracker for accessing multi-touch data.

Tweak view save/restore state so it will play well with list views.

We need to restore the state *after* the adapter has been set;
setting the adapter clears the state. To do this, we move the
state restore from immediately after the view is created to after
we call Fragment.onActivityAttached().

Also introduced a new Fragment.onViewCreated() callback which is
nice for fragments that want to do some setup after onCreateView()
but allow for subclasses to override that method. (ListFragment
I'm looking at you.)
/frameworks/support/v4/Android.mk
614bd22138e6c13f9f3f3d2e85d13623f1c088dd 28-Feb-2011 Xavier Ducrohet <xav@android.com> Add android-support-v4.jar to sdk builds.

Change-Id: I98514c9ca872a0d3ae77db7baa5e45d38c465c75
/frameworks/support/v4/Android.mk
27aea04b07c1fafa0f815aa4f80374a9e051b41c 22-Feb-2011 Dianne Hackborn <hackbod@google.com> Implement support for menus in fragments.

This uses a little trick to be able to take care of rebuilding
the menu when the fragments change, when running on pre-HC
platforms. When running on HC or better, it uses the new API
to invalidate the menu.

Also adds a little bit of a helper for using new menu APIs and
fixes the implementation of dump() to call up to the super class
dump() when running on HC.

And fix a few problems that came up when running on Donut.

Change-Id: I2420545632796b3199d5eec90aa3f3372ceedb90
/frameworks/support/v4/Android.mk
cba2e2c881e8e16ea5025b564c94320174d65f01 08-Feb-2011 Dianne Hackborn <hackbod@google.com> First checkin!

Change-Id: Ib09737c48a144dd778efe4750452d74ac8265a29
/frameworks/support/v4/Android.mk