This just reuses the views from BrigthnessDialog. Later, we will move
to a model where we only have one single slider.
Change-Id: Ib8116741802b7de930331648e50ff55fc869d7af
Also, the status icons are hidden when quick settings is expanded,
except for the battey indicator.
Change-Id: I6fb130c7eb73445b2ec2fdf9a9f3ec181d98033d
We only inset the notification themselves on tablets, and also the
header when not on the lockscreen (on the lockscreen, the header must
be full width so the icons are at the correct location).
Change-Id: I85c8a4559f59b016432dab4a73236352233d9159
Also introduces a different height for the header area on keyguard,
as it looks better with less padding when no background is here (and
is closer to the mocks).
Change-Id: Ie9b94dcf823c3e4af83a22f5fae15d9033e146fd
This change moves the status bar icons into the quick settings header
when the status bar is expanded. Also, the universal header is now
showing on the Keyguard.
Change-Id: Ib91f7e0b8de9f852676a11b500c4419183db1b90
This also includes a new (very WIP) interaction to get to quick
settings, with clumping the cards and a scrollable container with
the cards and the bottom QS part in it.
Change-Id: Ib073bb0174cddcf60347a5e3bb474fb3b6385bcf
Refactor the camera affordance into a reusable view. This change
also swaps the asset for the camera affordance.
Bug: 14488709
Change-Id: I0633614f6a1ea81faa37923f748af3c635e64a52
Adds button in the same location as the menu button and overrides
it when present. The setNavigationHintIconHints lets it know when
the button should be shown.
Bug: 14257632
Change-Id: Ia80de7fd2390cd8b083e37cbe58b7ee53555e619
This allows for animating the notifications between the different
states. So we can nicely switch between Keyguard and full shade,
and make the stack smaller when going to quick settings.
Change-Id: I768dc7cd8f4dc0197365a5befebad24086816a8d
Notifications now consist of ExpandableViews instead of SizeAdaptiveLayouts
to avoid layout passes during the resizing. The StackScrollAlgorithm and its
States are also refactored in order to support the new behaviour. In addition,
the generation of the outline is moved to the notification views instead of
the container which contains them.
Change-Id: I1ac1292a6520f5951610039bfa204c204be9d640
Currently, the padding and the glow was inside the individual
notification. This no longer works if we want to adjust the
padding dynamically whether we are on Keyguard or not. This change
moves the padding outside of the individual notifications, and as
a side effect, removes the glow. The glow wasn't really visible with
the new layout, so it's not a breaking change. We have to discuss
with UX first what the new "glow" solution is going to be.
Change-Id: Iac16892cb3b7bb1de3001954b1428796b07950c1
This also moves the camera affordance from navbar to the navigation
panel, so it is still visible on the Keyguard.
Bug: 14086354
Bug: 14085922
Bug: 14110532
Bug: 14059294
Change-Id: I93b51381915a67c688cdffd055fd149f2a220b00
I don't always have quick settings. But when I do,
they live in a flip view, not a separate panel.
Bug:14133785
Change-Id: I3df11d7de308a36a800eb7582a71e3febc897fec
Make existing QS panel available via pulldown from header
(or keyguard status view on keyguard), update the affordances
as a hint.
Don't allow QS to scroll, cap to max rows.
Add scrim over panel to indicate that this is purely temporary.
Bug:14081801
Bug:14059974
Change-Id: I166033975cbc44b91f45ee70ea5c7540390670dd
For the double tap interaction, this change introduces a new cue
that the notifications must be double-tapped: With the first tap,
the tapped notifications gets larger and the others fade out a bit.
Change-Id: Ib48ff0291aee1a5ec083b9e7ed1021bc420514cf
