53378188683d54e59d5d192cd3a88af3a48c255a |
16-May-2016 |
Clara Bayarri <clarabayarri@google.com> |
Hide BaseFragmentActivity* from the API Bug: 28775596 Change-Id: I971c837541036ebd6cb1913f512932291c0477b6
4/app/BaseFragmentActivityHoneycomb.java
|
5f5ffb9bea7e6db394d6879f37ab1aadb8d2fdeb |
25-Apr-2016 |
Chris Banes <chrisbanes@google.com> |
resolve merge conflicts of 4519642 to nyc-dev Change-Id: Iffcd2dec64d31ba297a1806c11d1e48116248dba
|
be678137d44778590a6220ae0ef13649e83363a9 |
21-Apr-2016 |
Chris Banes <chrisbanes@google.com> |
Tidy up DrawableCompat + VDC/AVDC calls Currently DrawableCompat will wrap any drawable on API < 22. As VDC supports tinting natively, we should use that instead of wrapping. This CL fixes this by extracting the calls to an marker interface and making VDC + AVDC implement it. Also tidied up the doc on DrawableCompat.wrap(). BUG: 28296684 Change-Id: I6e23db54aa10758b3c0a08e8d110210799453595
4/graphics/drawable/DrawableCompatHoneycomb.java
|
03d45b9a2e6552010d46a36866838d000fd515bd |
21-Apr-2016 |
Clara Bayarri <clarabayarri@google.com> |
Merge "Provide startIntentSenderForResult for fragments" into nyc-dev
|
fed04169c31e7e3d8c7a328876358dd3564062bb |
14-Apr-2016 |
Clara Bayarri <clarabayarri@google.com> |
Provide startIntentSenderForResult for fragments Bug: 27700608 Change-Id: I43139604b0aa60c2dcce93db92a38e1327566a4e
4/app/BaseFragmentActivityHoneycomb.java
|
3faba4d9eaba0ac552a9f6dd5c54bfa45e51a133 |
18-Apr-2016 |
Chris Banes <chrisbanes@google.com> |
Merge "Fix invalidation workaround" into mnc-ub-dev am: b878633 * commit 'b878633128a0533d843edcc7c086155bbddb4db8': Fix invalidation workaround Change-Id: Icbb200907e08833848a98d8eae6c3201f882cc0c
|
4a5aaa6852108a8e5fd9e849209803c8f6fcd6cf |
18-Apr-2016 |
Chris Banes <chrisbanes@google.com> |
Fix invalidation workaround We were missing the tickle on the actual view, as well as the parent. BUG: 28239627 Change-Id: I8593e9a6ea8074e0a103ba4ed5c76f7220dc6e18
4/view/ViewCompatHC.java
|
4510b5c24adad2b94df9b84c6b73f5534ffe9b57 |
06-Apr-2016 |
Yigit Boyar <yboyar@google.com> |
Do not recycle visible views This CL adds a new API to the LayoutManager where the LayoutManager can get the bounds of a View while taking into account its transformation matrix. This API is mainly useful for recycle decision. I've also changed built in layout managers to respect this value in addition to layout position of the view. Bug: 26402811 Change-Id: If75072c73d3374bfac0439d7714714c82684096a
4/view/ViewCompatHC.java
|
a0af9ab1fbfa7f4e1c1d90278ec3ff3167a7ec60 |
26-Feb-2016 |
Chris Banes <chrisbanes@google.com> |
resolve merge conflicts of 6dc05991fa to nyc-dev Change-Id: Icdd6cf18ea09242e94fb396ddf4f3e00bdb6808e
|
4da36b0dfa8436b197314094337fa3102fcca1bc |
25-Feb-2016 |
Chris Banes <chrisbanes@google.com> |
Fix issue with DrawableCompat.wrap() + mutation The following is workaround for issues for certain DrawableContainers on some API levels. They expect getConstantState() to always return non-null, which will only happen after our wrapper has been mutated. Since most Drawables provided to wrap() will be from Resources, they will nearly always have been mutated. Therefore the wrapper should act as it has been too, and return a constant state. BUG: 27353857 Change-Id: Ib244f8f26f2e09979885d1fe2b84f0ec55cf2f02
4/graphics/drawable/DrawableWrapperHoneycomb.java
|
9a7451b2f23d00e8f4b68f16edb64f260b433fee |
03-Feb-2016 |
Chris Banes <chrisbanes@google.com> |
Merge "Fix AppCompat running on pre-v13"
|
ed1096ebffac8f3cac5e5b98f54b96ae2ce8579e |
02-Feb-2016 |
Chris Banes <chrisbanes@google.com> |
Fix AppCompat running on pre-v13 BUG: 26928253 Change-Id: I1d0f56df5072e35370b1943ebaf15531145f8c5b
4/view/KeyEventCompatHoneycomb.java
|
34656d7f78f35591ad1f629b936c939406d6270e |
01-Feb-2016 |
Yuichi Araki <yaraki@google.com> |
VC.offsetTopAndBottom/LeftAndRight on API 11-22 Bug: 26894655 Change-Id: I8579782f77f6b8a71c7c82bc94fbfe8a56e4eccb
4/view/ViewCompatHC.java
|
a89b7a8e4840e52dfda1442bcb885686680556f6 |
26-Jan-2016 |
Chris Banes <chrisbanes@google.com> |
Fix Snackbar swipe to dismiss not working pre-v11 Multiple issues: - offsetTopAndBottom doesn't invalidate pre-v11, so ViewDragHelper now uses the ViewCompat version. - ViewCompat's offset method needs to invalidate the parent instead, since the view has moved and thus the dirty rect is larger than the view's bounds. - Fixed issue in Snackbar which meant that the view would not be removed after a swipe settle. BUG: 26768803 Change-Id: Ia9abc4884f8ffd05408135d3fc4dd1b073392a7b
4/view/ViewCompatHC.java
|
9925d4a53e0dbaacf07901fb48907fe1aff9bbbd |
22-Jan-2016 |
Chris Banes <chrisbanes@google.com> |
Implement ConstantState in DrawableCompat.wrap()s wrappers Mostly copied from M's DrawableWrapper class BUG: 26698785 Change-Id: I2580e10883c4b2ec8d274ad66a3cd1c6ab1dfc95
4/graphics/drawable/DrawableWrapperHoneycomb.java
|
de8e2baf9504defe12972fbf60935a1148f1098f |
24-Jul-2015 |
Vladislav Kaznacheev <kaznacheev@google.com> |
Introduce ParallelExecutorCompat into support/v4 This class provides a backward compatible access to a shared instance of ThreadPoolExecutor. Also using this class in AsyncListUtil implementation to avoid creating a new single thread executor per instance. Fixed tests accordingly. Bug: 22640199 Change-Id: I89a59854f436c7dd9a8a9ab30fc86bd8f50e9df7 (cherry picked from commit c705c5d9a4f33aafeaabdf294b22bd587b0b7811)
4/content/ExecutorCompatHoneycomb.java
|
20680c49584c26f7818c2dec8fb00633af753e4a |
19-May-2015 |
Chris Banes <chrisbanes@google.com> |
Allow FragmentActivity to hook in to Factory2 method Since Activity will automatically install itself as a private factory on HC+, we need to ensure that FragmentActivity also hooks in as a Factory2. Currently, if FragmentActivity's Factory is *not* called, the framework FragmentManager will attempt to inflate a support Fragment and crash. Also removed some AppCompat code which is now uneeded. BUG: 21287184 Change-Id: Id163caa3ec46654e25706e58415d4aa7b0213dd1
4/app/BaseFragmentActivityHoneycomb.java
|
976b6a8c18550ace670e0410453741d11dafa474 |
15-May-2015 |
Ian Lake <ilake@google.com> |
Introduce NotificationCompat.MediaStyle DO NOT MERGE Make Notification.MediaStyle available from v7 with the support library. For versions prior ICS, the normal template is used, as buttons within notifications weren't supported. From ICS to Jellybean, a custom template is used which maches the platform one. On Lollipop and later, the platform implementation is used. Bug: 17425365 Change-Id: I6a44c8b325c0fb204e3043e1114c4a2c3276d78f (cherry picked from commit 10d7d250bc41b21059a90095e8b693c9e7bc3bc3)
4/app/NotificationBuilderWithBuilderAccessor.java
|
a12f22ddbd4382df3bc0d7311e7573b4c748c76c |
22-Apr-2015 |
Chris Banes <chrisbanes@google.com> |
Ensure LayoutInflaterCompat forces set the correct Factory This is a follow up to Ib9cd690725b365ad40d4a6cf12c1e6dc6c0089fd which makes sure that any subsequent merged factory is set to be the designated Factory2. This ensures that we use the merged factory over another Factory2. Also bumped up the version number in preparation. BUG: 20477817 Change-Id: Ie4ea8595afffe9905bb11174f330db4dedb2d2fb
4/view/LayoutInflaterCompatHC.java
|
10850534c9e2949857133437cf1cd9af82721ab1 |
19-Apr-2015 |
Adam Powell <adamp@google.com> |
Work around a framework bug setting LayoutInflater.Factory2 Prior to commit 630c077463fecaa8eb1015865770f2c05c514ade in frameworks/base there was a platform bug starting at API 11 (fixed in API 21) that would cause a Factory2 not to be set properly on a LayoutInflater obtained via the LayoutInflater#cloneInContext method. The intended behavior was to merge the old Factory/Factory2 with the new one set on the cloned LayoutInflater. Precedence is given to the new Factory/Factory2, but if the new factory returns null, the old one is used. The bug would cause the merge to be correct for Factory, but not Factory2. Now that AppCompat uses Factory2, this matters. Without this workaround, nested fragment inflation for android-support-v4 fragments is broken and nested fragments are inflated into the FragmentActivity's FragmentManager instead of the parent Fragment's child FragmentManager. Bug 20343535 Change-Id: Ib9cd690725b365ad40d4a6cf12c1e6dc6c0089fd
4/view/LayoutInflaterCompatHC.java
|
a966c6cda6a3aa562fcfdb842b6c6b35bdd6a3dc |
05-Feb-2015 |
Adam Powell <adamp@google.com> |
CoordinatorLayout CoordinatorLayout is meant to be like a super-powered FrameLayout with three major additional capabilities: * Aligning views relative to other views arbitrarily nested within other siblings (e.g. floating action buttons aligning to one edge of a content pane) * Aligning views relative to keylines defining horizontal positioning * Defining pluggable interaction behaviors from layout xml This patch implements the first two features and some of the initial plumbing for the third. Change-Id: I9c368d298cd35ff507ce5c8449a572fbfe9e5da7
4/view/ViewCompatHC.java
|
7e82b99953680915596eaf0eb35927388e574ca8 |
27-Jan-2015 |
Chris Banes <chrisbanes@google.com> |
Add tintable Drawables to support-v4 Works by using AppCompat's tinting Drawbale wrapper in support v4. I've also moved over AppCompat and design lib to use DrawableCompat. I've also added a workaround due to GradientDrawable not supporting tinting of Lollipop. Change-Id: Ifa178eae99207051bf72ba6b9f3148cdcbe1579f
4/graphics/drawable/DrawableCompatHoneycomb.java
4/graphics/drawable/DrawableWrapperHoneycomb.java
|
fd1eb27a3700de31507de34fd1bcc51830fe876c |
24-Oct-2014 |
Chris Banes <chrisbanes@google.com> |
Backport android:theme functionality for all Views Also make the tinted widgets public so that developers can extend from them. BUG: 18367946 BUG: 18112118 Change-Id: Id47e21e960f3539304f0c1c023eebdff6c429c8d
4/view/LayoutInflaterCompatHC.java
|
b645de790756e27bbe92d133216b7ac79cca7679 |
21-Oct-2014 |
Chris Banes <chrisbanes@google.com> |
Update ShareActionProvider to match Lollipop's BUG: 16370059 Change-Id: I1e0013bd9344ccda3751972109b389097d4f7a23
4/view/ViewCompatHC.java
|
5e63ab9505a3a4d11374cbbec418c1aba921409d |
07-Oct-2014 |
Chris Banes <chrisbanes@google.com> |
Remove the intermediary ViewGroup for support-v4 fragments On Honeycomb and above the extra ViewGroup isn't needed as we can use setSaveFromParentEnabled() like the framework FragmentManager impl. BUG: 17901056 Change-Id: I7b3cb130943f8f0e9ab7c910f86f5d711bd42f7a
4/view/ViewCompatHC.java
|
bc7c32772fbc966091181ce7fa933ca4083679ac |
22-Sep-2014 |
Adam Powell <adamp@google.com> |
Jump drawables to current state when rebinding ActionMenuView This prevents lingering ripples or other pressed state effects from remaining after an action button has been rebound. Also add ViewCompat#jumpDrawablesToCurrentState to support this. Bug 17592051 Change-Id: I8227af59d7b80a5a2d2f91aca7d0f17257fb6101
4/view/ViewCompatHC.java
|
b966b785a7e81697f88861b98d2ae2a9acb2cfbf |
11-Jul-2014 |
Alan Viverette <alanv@google.com> |
Fix HC support lib drawer toggle Change-Id: Iee870727f98693942b735701da3e821392a61ac9
4/app/ActionBarDrawerToggleHoneycomb.java
|
d95b307eb0b135c6c1da464fcbab96802506f929 |
11-Jul-2014 |
Alan Viverette <alanv@google.com> |
Obtain the theme up indicator using the action bar context BUG: 16208318 Change-Id: I2cbd24c83c2e87736ef0e00ae5fe8acf160dad09
4/app/ActionBarDrawerToggleHoneycomb.java
|
c6cdc41397bc3ad2c936069af6d448f242790513 |
01-Jul-2014 |
Chris Banes <chrisbanes@google.com> |
Update Palette + AsyncTaskCompat - Added AsyncTaskCompat to v4 - Moved PaletteItem into Swatch inner class of Palette - Removed unnecessary copying of pixel int[] data - Use THREAD_POOL_EXECUTOR for AsyncTask - Various other improvements Change-Id: I06f1efefcdfa3d22578653b5f5da3d61a064b5d5
4/os/AsyncTaskCompatHoneycomb.java
|
51ea7c98b34f39a2da711549a0a443c77f2c94b0 |
03-Jul-2014 |
Narayan Kamath <narayan@google.com> |
Revert "Update Palette + AsyncTaskCompat" This reverts commit b14fc7c928307b6758688ed38590bf674c62a01b. Change-Id: I57a2cee10f4084e921bc9204784c6fffce56b80b
4/os/AsyncTaskCompatHoneycomb.java
|
b14fc7c928307b6758688ed38590bf674c62a01b |
01-Jul-2014 |
Chris Banes <chrisbanes@google.com> |
Update Palette + AsyncTaskCompat - Added AsyncTaskCompat to v4 - Moved PaletteItem into Swatch inner class of Palette - Removed unnecessary copying of pixel int[] data - Use THREAD_POOL_EXECUTOR for AsyncTask - Various other improvements Change-Id: I66ada4bd2d4cec48b87acce50fb0fd6952473c25
4/os/AsyncTaskCompatHoneycomb.java
|
d7d27e9ebe5c7325e67e1a8af265378bd2056cad |
28-Feb-2014 |
Chet Haase <chet@google.com> |
Add animations to RecyclerView This CL adds the basic plumbing for animating item changes in RecyclerView. It also implements the bare essentials add/delete animations. When the app specifies that items have been added/removed (by calling the appropriate Adapter methods), the RecyclerView will determine the appropriate fading and moving animations to animate the items being added, removed, and moved into new locations. Change-Id: I4fa8686f54c8bfa2ba29c399eea112d33f71689c
4/view/ViewCompatHC.java
|
b1bfdf4c03d1b25959c5818805b997020f7ed085 |
15-May-2014 |
Chet Haase <chet@google.com> |
Revert "Add animations to RecyclerView" This reverts commit 33b18903168c177d65e3c2ef7398c1b2ca0c826f. Change-Id: I41664a375f9fc5fa878481b90cd2e61aad17f739
4/view/ViewCompatHC.java
|
33b18903168c177d65e3c2ef7398c1b2ca0c826f |
28-Feb-2014 |
Chet Haase <chet@google.com> |
Add animations to RecyclerView This CL adds the basic plumbing for animating item changes in RecyclerView. It also implements the bare essentials add/delete animations. When the app specifies that items have been added/removed (by calling the appropriate Adapter methods), the RecyclerView will determine the appropriate fading and moving animations to animate the items being added, removed, and moved into new locations. Change-Id: If70c09e7af168ce5963c785b5886a18c87a7dc98
4/view/ViewCompatHC.java
|
c096ad1894f1a4543e703ddc9d279fbd3b596c53 |
06-Mar-2014 |
Adam Powell <adamp@google.com> |
More RecyclerView API additions * findViewHolderForChildUnder() becomes findChildViewUnder() * Have findChildViewUnder() respect translationX/Y properties * getChildViewHolder() becomes public * LayoutManager gets onAddFocusables to override default ViewGroup#addFocusables behavior * LayoutManager gets onInterceptFocusSearch to override the default focus finder behavior before onFocusSearchFailed Change-Id: Id7e79167fbe68bdbeac6e0cd09c90202b493f4df
4/view/ViewCompatHC.java
|
6eac16328af1bc2cf0560e7a46fd90cb056ec203 |
15-Feb-2014 |
Alan Viverette <alanv@google.com> |
am 45fb1eea: am f4166011: Force content description update in ActionBarDrawerToggle * commit '45fb1eeaa6338def00148c04f07d6a7def501c00': Force content description update in ActionBarDrawerToggle
|
f41660112132e90d4a127051bf2772fa2347e42c |
14-Feb-2014 |
Alan Viverette <alanv@google.com> |
Force content description update in ActionBarDrawerToggle Change-Id: I524c0747675302fcfc7509891c7cca6ee5ae8c1b
4/app/ActionBarDrawerToggleHoneycomb.java
|
f6a9644327aca589c415a44b9cc1411d15ce6e70 |
14-Feb-2014 |
Griff Hazen <griff@google.com> |
Merge "Roll forward the support library changes for LOCAL_ONLY support." into klp-modular-dev
|
7b74aa144a22b74896be5f28af2c4f257f76d71f |
13-Feb-2014 |
Alan Viverette <alanv@google.com> |
Revert "Force action bar to update generated content description" This reverts commit 169b51c4749ece0e04575beb42f09d43aca610d2. Change-Id: I37d003b696901032d1bc0382e508888e7b77c665
4/app/ActionBarDrawerToggleHoneycomb.java
|
b56de0d1a113c71a2808303009ab4d9708ed6e84 |
13-Feb-2014 |
Griff Hazen <griff@google.com> |
Roll forward the support library changes for LOCAL_ONLY support. The build problem was because unbundled branches were depending on the master version of frameworks/support. Also renamed "Current" to "Api20" pre request. Change-Id: I309b89b133e22fb642f3dcd8d23af6697fe0b9c6
4/app/NotificationBuilderWithBuilderAccessor.java
|
169b51c4749ece0e04575beb42f09d43aca610d2 |
12-Feb-2014 |
Alan Viverette <alanv@google.com> |
Force action bar to update generated content description BUG: 12607574 Change-Id: I4a2086f8866cdcd5ec2f3997cf418134f84ff08a
4/app/ActionBarDrawerToggleHoneycomb.java
|
145d27f9dd22e953d05e01327c9c2dac68634ae8 |
19-Oct-2013 |
Jeff Sharkey <jsharkey@android.com> |
Support versions of new external storage APIs. Add support library versions of getObbDirs(), getExternalFilesDirs(), getExternalCacheDirs(), and Environment.getStorageState(). Bug: 11287667 Change-Id: I78db3800a3fbcd65b6ac7c3ee8c297d535a3b59c
4/content/ContextCompatHoneycomb.java
|
b12ba0547b2fad1c4dfc12dec36c5e7893974e67 |
28-Aug-2013 |
Adam Powell <adamp@google.com> |
Fix compatibility support for v7/gridlayout A previous implementation import from frameworks/base combined with an incorrectly restricted makefile led to GridLayout using new/hidden API from the framework instead of compat lib conventions and public API only. Add required shims to ViewCompat/ViewGroupCompat as needed and have GridLayout use them. Fix some general Android code style guide issues. Change-Id: I5dd965b9c4282c47964bfd1d481e3a62725cca38
4/view/ViewCompatHC.java
|
2a7181902b4d4596da15304b97e5cb3010126229 |
05-Jun-2013 |
Scott Main <smain@google.com> |
am b835468a: am 84bbe6fe: make various compat classes package only * commit 'b835468ac941e7b09b3c45bcff95f10f3ba4f752': make various compat classes package only
|
84bbe6fe39c63a7e67a3ca937981a463c11ac9ed |
03-Jun-2013 |
Scott Main <smain@google.com> |
make various compat classes package only Change-Id: Icc42b95455cc572cee9a583a22e55febb7663fba
4/app/TaskStackBuilderHoneycomb.java
|
6eb3cdf42d5382aef6b6a6afd7c305dbc27885b9 |
30-May-2013 |
Alan Viverette <alanv@google.com> |
Initial commit for ExploreByTouchHelper class. This helper class simplifies the implementation of accessibility in custom views that would otherwise need AccessibilityNodeProvider. It supports single-depth virtual view hierarchies and enforces guidelines about what properties must be set on accessibility nodes and events. Additional supporting code has been added to the ViewCompat and ViewParentCompat. Change-Id: If0d1f21bea5c187eecc54cac6c9e9bae96337d9b
4/view/ViewCompatHC.java
|
11417b1cfde8f1749905f2d735623af9214148af |
27-Apr-2013 |
Jeff Brown <jeffbrown@google.com> |
Add media router picker UI. Introduced the concept of a MediaRouteSelector which is the means by which an application states the route capabilities of routes that it would like to discover. Added selectors to the addCallback method along with several other methods to assist with discovery. Callbacks can specify flags to perform active scans of routes or to disable filtering of route events. Added a workaround to scan for wifi displays on JB MR1. Refactored the route descriptor objects to use the builder pattern instead of simply documenting that they should be immutable since several developers have already tripped over this. The UI is feature complete but not final. Bug: 8175766 Change-Id: I54ebb7488222746b0c07292e65b9ded1b9d720fa
4/graphics/drawable/DrawableCompatHoneycomb.java
|
4d43916b89d85315e1f344d992325e8ab106fb4e |
07-May-2013 |
Adam Powell <adamp@google.com> |
am 2c4ea24c: am cb154e52: am 1b8262b8: Disable MotionEvent splitting for DrawerLayout * commit '2c4ea24c49d222582c7e439e461935f18099886c': Disable MotionEvent splitting for DrawerLayout
|
1b8262b87426b2f766b40d6ab4eaeac296d5c2fe |
07-May-2013 |
Adam Powell <adamp@google.com> |
Disable MotionEvent splitting for DrawerLayout Make sure that secondary touches don't interact with content in views other than the drawer. Add ViewGroupCompat method for MotionEvent splitting changes Bug 8839961 Change-Id: Ia833333ef596363d0a3ce951f53f78342aca52aa
4/view/ViewGroupCompatHC.java
|
30837f1095c803f332f4a1c3f0917c8afdd50156 |
24-Apr-2013 |
Adam Powell <adamp@google.com> |
API changes for support action bar menus Refactor support action bar to use standard framework menu interfaces instead of additional interfaces. This simplifies the API and results in fewer disjoint callbacks which could make life difficult for library authors. SupportMenu/SupportMenuItem are now private implementation details of the support lib rather than interfaces used directly by app developers. Developers must use standard support shim *Compat classes to access new methods, and these shims are now aware of SupportMenu/SupportMenuItem and will do the right thing. Fix up a few other general issues and bugs. Change-Id: I833dce76485741b680bef84c1c0ed8d81ea57616
4/view/MenuItemCompatHoneycomb.java
|
79f95ce3e660d267831067e514ff455156c4381f |
18-Apr-2013 |
Adam Powell <adamp@google.com> |
Add ActionBarDrawerToggle This helper provides an easy way to tie together the functionality of DrawerLayout and the framework action bar and correctly implement the design guide behavior for navigation drawers. Fix a bug with minimum fling velocity in DrawerLayout/SlidingPaneLayout. Part of bug 8609454 - code samples for DrawerLayout/SlidingPaneLayout Change-Id: I293ac33e3898e5dbecdb8aed386318a40f72ca75
4/app/ActionBarDrawerToggleHoneycomb.java
|
44e3a52be44809a8018fb170e3130cc0ae164366 |
06-Dec-2012 |
Dianne Hackborn <hackbod@google.com> |
SDK only: improve SearchViewCompat There is an issue with SearchView where if you use back to dismiss it, the search text does not get cleared. This change fixes it in the support library by overriding the callback about the action view being collapsed to also clear the search text. (Note that this will only be fixed in API 14 or later since this callback doesn't exist on earlier versions.) Also add a bunch of additional methods for performing API calls on the SearchView. Change-Id: I97241f165eb6076329ff7108c4596da72d02cb6c
4/widget/SearchViewCompatHoneycomb.java
|
bea2fc73637a1d59eb5face20006a27df6893042 |
25-Sep-2012 |
Adam Powell <adamp@google.com> |
Supply the full set of make* methods in IntentCompat IntentCompat now supports all of makeMainActivity, makeMainSelectorActivity, and makeRestartActivityTask. Bug 7225175 Change-Id: I4ec30058b706575aace8bd2de3bcf6749d7617ad
4/content/IntentCompatHoneycomb.java
|
f19cb1f3facdb9f90ef1b26537ff303eaa3db77d |
17-Sep-2012 |
Adam Powell <adamp@google.com> |
Port TaskStackBuilder fixes and features from frameworks/base Bug 6457058 Change-Id: Ibc519e1b0ef10b2fb37992d68dfc92953f0355a5
4/content/IntentCompatHoneycomb.java
|
97341bdc5bea1d7bf777de65228039142d249f38 |
20-Jul-2012 |
Adam Powell <adamp@google.com> |
Add SlidingPaneLayout SlidingPaneLayout gives a two-pane layout suitable for use at the top level of an activity layout. layout_width on children is treated as a minimum width and layout_weight indicates how remaining space should be divided, similar to LinearLayout. When there isn't enough space to lay out the child views, remaining views become sliding panels that can move over previous panels. If a panel slides more than halfway out of view, it dims and will not respond to normal touch input. Instead taps will slide the panel closed making its content fully visible again. Still todo: * Keyboard support - navigating into a dimmed pane should bring the pane back. * requestChildRectangleOnScreen and friends * Helpers for manipulating Up/Back in Activities * Further testing Change-Id: I4dae69e06d1cee4e7b68091f6bea70a317eab517
4/view/ViewCompatHC.java
|
8a0c51a3d438802df28612e02fdf0cc8fab06ddb |
24-Jul-2012 |
Adam Powell <adamp@google.com> |
Add PageTransformers to ViewPager PageTransformer allows an app to supply a custom step during scrolling to transform each page view in addition to the default sliding behavior. Setting a PageTransformer also allows the app to reverse the drawing order for pages to accomodate certain kinds of transformations. Add setLayerType to ViewCompat. Make ViewPager use hardware layers for scrolling when available and a PageTransformer is in use. Change-Id: Icdcb7bf92ad4adb9d14e36c6048f7f5dd455437b
4/view/ViewCompatHC.java
|
575e098da5bc16ff8b95ca080284253fd206fe12 |
12-Jun-2012 |
Adam Powell <adamp@google.com> |
Allow TaskStackBuilder to be used from a Service Add ContextCompat and pull startActivities out of ActivityCompat. Bug 6650578 Change-Id: Ib7451d2821a60829525321c6f397bc34b1c0cf2f
4/app/ActivityCompatHoneycomb.java
4/content/ContextCompatHoneycomb.java
|
79a066778652bc29586d60381da0a75d741279bb |
19-Apr-2012 |
Chris Tate <ctate@android.com> |
am c1ca6fda: am 993d3e48: am 0d3a6843: Merge "Support setNumber(int) in NotificationCompat.Builder" * commit 'c1ca6fdaa0d74e2707fc70b342bf5ac9a613875e': Support setNumber(int) in NotificationCompat.Builder
|
9e164ff93fd027f51f0f950d9de222a1fbaec112 |
18-Apr-2012 |
Scott Kennedy <skennedy27@gmail.com> |
Support setNumber(int) in NotificationCompat.Builder The "number" parameter was ignored in NotificationCompatHoneycomb, so it does not get displayed in the notification. This simply calls through to the native Notification.Builder#setNumber(int) method. Change-Id: Ic867efa6f4b4b79fa64723443e0df2045f262d01 Signed-off-by: Scott Kennedy <skennedy27@gmail.com>
4/app/NotificationCompatHoneycomb.java
|
ec03704fbb4f0217d4c274d1c6cf56e6ea4dcfbd |
12-Apr-2012 |
Adam Powell <adamp@google.com> |
Add support for postOnAnimation View methods for JB. Fallback variants for older platform versions post runnables with a timeout value lower than that needed to achieve 60fps. Change-Id: I807a1cbe82111a29e9459de0892f253348717c7b
4/view/ViewCompatHC.java
|
c9cf2eb0a9b6694d0fda3dbc313844955db60820 |
13-Jan-2012 |
Adam Powell <adamp@google.com> |
Add app navigation helper code to the support library. Add TaskStackBuilder for synthesizing back stacks for cross-task navigation on Android 3.0 and newer. Add NavUtils for general navigation helper code. Add NotificationCompat.Builder as a partial backport of Android 3.0's Notification.Builder. (It does not currently support progress notifications.) Change-Id: I2d7d4dab3dd26e34f6b2210d0f0f3909f2162d6f
4/app/ActivityCompatHoneycomb.java
4/app/NotificationCompatHoneycomb.java
4/app/TaskStackBuilderHoneycomb.java
|
1935ed3af7c6545bc38adfdc6026d87a3249222f |
15-Nov-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Adding new APIs to the support-v4 lib needed by the v4 samples (support-v4 part). Some of the samples are using APIs that are introduced after v4 but not supported in the v4 library. Adding the minimal necessary stuff to the support-v4 lib to compile and run the samples. bug:5616340 Change-Id: I103e557f8d021773d51d8383f7b6752027ca334d
4/view/MenuCompatHoneycomb.java
4/view/MenuItemCompatHoneycomb.java
4/widget/SearchViewCompatHoneycomb.java
|
2a4d8518f36346ea25a22a736453ff28f2954165 |
30-Aug-2011 |
Dianne Hackborn <hackbod@google.com> |
Fix issues 5158104 and 4981556 (fragment problems) 5158104: com.android.contacts: java.lang.IllegalStateException: Can not perform this action after onSaveInstanceState at android.app.FragmentManagerImpl.checkStateLoss(FragmentManager.java:1201) The ViewPager can just commit without worrying about a state loss, since it can correctly reconstruct its state later. 4981556: Fragment.mImmediateActivity doesn't get restored on orientation change I am giving up on this thing; I just don't see how it can actually be correct. So now instead of getting an exception about a dup add/remove at point of the add/remove call, this will happen later when processing the transaction. Also add an API for controlling the visibility of menus, which ViewPager uses to have the correct menus shows. And add a method to get the name of a back stack entry. Finally fix a recent problem in ViewPager with dealing with focus, and make ViewPager smart about handling keyboard focus navigation inside itself. Change-Id: I280269ac64079d171e9c899ea1cff7e80246c924
4/view/KeyEventCompatHoneycomb.java
|
eedc67283a5a49dce86c625e54596dfdea9465a7 |
05-Apr-2011 |
Dianne Hackborn <hackbod@google.com> |
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. Change-Id: I997492cfc6f1969f1a5d775385afb830f5a47795
4/view/VelocityTrackerCompatHoneycomb.java
|
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
4/app/ActivityCompatHoneycomb.java
4/view/MenuCompatHoneycomb.java
|