Status Update
No update yet.
Comments
ap...@google.com
Branch: androidx-master-dev
commit 27ea2de83c9a53a3f7ebb7e0fbaaac7cc2adeb21
Author: Louis Pullen-Freilich <lpf@google.com>
Date: Mon Jul 06 17:55:59 2020
Moves androidx.ui:ui-animation-core to androidx.compose.animation:animation-core
This CL does not touch package names, or directory structure - only the maven group.
Bug:
Bug:
Test: ../development/validateComposeModuleMigration.sh androidx.ui:ui-animation-core androidx.compose.animation:animation-core --build
Change-Id: If7b4254191583317fcb03e71c45a35692419bf62
M ui/settings.gradle
M ui/ui-animation-core/build.gradle
M ui/ui-animation-core/samples/build.gradle
M ui/ui-animation/build.gradle
M ui/ui-core/build.gradle
M ui/ui-desktop/build.gradle
M ui/ui-material/build.gradle
na...@google.com
As a data point for this issue: going forward, core will likely have more dependencies on the animation primitives (from animation-core). :)
ap...@google.com
We were running into a similar circular dependency problem with animated vectors (cc Nader) - vectors live in UI but animated vectors need animation APIs.
Did we consider moving animation to be a lower group than ui? We could move the animation clock ambient to animation directly, avoiding the cyclic dependency, and also lets us use animation APIs in the ui library.
It also seems that animateContentSize makes more sense in the ui group than animation.
ju...@google.com
Re #4:
Could you elaborate on what moving animation to be a lower group would look like? Is this animation or both animation and animation-core?
I assume there's a policy against having animation-core and animation in separate groups? That would solve the cicular dependency between groups.
BTW, AnimationClock is going away by Beta, although that wouldn't solve the animated vectors issue.
Description
Right now compose will automatically leverage an offscreen compositinglayer if the graphicsLayer has an alpha < 1.0f. However, configuring usage of an offscreen layer is useful in other circumstances such as blend mode usage.
Alternatively if a consumer of graphicsLayer has more information regarding the scene (ex if the content is overlapping or not) they should be able to skip offscreen compositing layer for alpha usage.